Add structured markers to JavaScript logs - #10
Open
rogierslag wants to merge 1 commit into
Open
rogierslag wants to merge 1 commit into
rogierslag wants to merge 1 commit into
Conversation
rogierslag
marked this pull request as ready for review
September 18, 2026 15:03
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
JavaScript log arguments currently become message text, making custom fields difficult to query in Elasticsearch.
Adds
Markers.of({...}), mirroring Java’s structured-marker approach: readable message text stays separate from attached fields. The logger exposes markers throughLogMessage.fields, and the Kafka transport writes them at the event root.Ordinary log arguments retain their behaviour. Kafka’s standard fields take precedence over marker values. Package versions remain unchanged.