fix(logger): logflare formatter consistency with logflare backend #675
Conversation
This file contains hidden or 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
- Pids are formatted with `erlang:pid_to_list` - Modules aren't inspected - Module and function are in metadata (despite this being redundant with mfa inside metadata.context)
v0idpwn
changed the title
v0idpwn
force-pushed
the
fix/logflare-backend-conformance
branch
from
e6dc28a to
12858b6
Compare
filipecabaco
approved these changes
Jun 22, 2025
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.
Hopefully the last one on this vein.
After comparing logs emitted through Vector and through the Logflare backend, I noticed a few differences:
erlang:pid_to_listI took a brief look in the Logflare backend and I don't think there are any more differences.