Add the stringify replacer option to the HTTP transport #2155
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Support custom stringify replacer when sending logs via HTTP transport. Usage of the `format.json` with the custom replacer does not work with HTTP transport since the message symlink (which is mutated) is not sent in the request.
|
Thanks for your contribution! |
|
Out in 3.8.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support custom stringify replacer when sending logs via HTTP transport.
Usage of the
format.jsonwith the custom replacer does not work withHTTP transport since the message symlink (which is mutated) is not sent
in the request.
Work done:
HttpTransportOptionsjsonStringifyof HTTP transport