-
Notifications
You must be signed in to change notification settings - Fork 98
JSON log format #611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
jelovirt
wants to merge
7
commits into
develop
Choose a base branch
from
feature/json-log
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
JSON log format #611
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
Signed-off-by: Jarno Elovirta <[email protected]>
Signed-off-by: Jarno Elovirta <[email protected]>
infotexture
reviewed
May 4, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a good start, with a few minor suggestions.
Not sure we need the list of fields in the command overview, but probably makes sense to add those to the logging topic and Xref there from the args topic.
Co-authored-by: Roger Sheen <[email protected]> Signed-off-by: Jarno Elovirta <[email protected]>
Co-authored-by: Roger Sheen <[email protected]> Signed-off-by: Jarno Elovirta <[email protected]>
Co-authored-by: Roger Sheen <[email protected]> Signed-off-by: Jarno Elovirta <[email protected]>
Co-authored-by: Roger Sheen <[email protected]> Signed-off-by: Jarno Elovirta <[email protected]>
Co-authored-by: Roger Sheen <[email protected]> Signed-off-by: Jarno Elovirta <[email protected]>
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.
Description
Document strucutured log (JSON).
Fields in every log message
level— log levelFATAL,ERROR,WARN,INFO,DEBUG, orTRACEtimestamp— message timestamp in ISO datatime formatOptional fields that are in some messages depending on message type
code— message IDduration— duration of build/target/task in millisecondsline— line number in the source documentlocation— source document that caused the log messagemsg— message textrow— row number in the source documentstacktrace— error Java stack tracetarget— Ant target nametask— Ant task nameMotivation and Context
Documents dita-ot/dita-ot#4581
How Has This Been Tested?
Type of Changes