Skip to content
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

Add log encoding option for JSON logging. #2166

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

mcdee
Copy link

@mcdee mcdee commented Sep 20, 2024

This option allows selection of either CONSOLE (the default, and the current behaviour) or JSON for log output, allowing for easier parsing of output for structued log backends.

This option allows selection of either CONSOLE (the default, and the
current behaviour) or JSON for log output, allowing for easier parsing
of output for structued log backends.
@dan-catalano-vc
Copy link

this is a great addition. hope this is merged in soon.

curious why you chose to call it encoding, instead of format

@dan-catalano-vc
Copy link

#2256

@mcdee
Copy link
Author

mcdee commented Nov 6, 2024

curious why you chose to call it encoding, instead of format

Encoding is the term used internally in the logging. Also, format can be the format for individual fields (e.g. timestamp format) rather than the general encoding of the log entry.

@pnowosie pnowosie self-requested a review November 26, 2024 12:14
Copy link
Contributor

@pnowosie pnowosie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - however linter fixes required

@mcdee
Copy link
Author

mcdee commented Nov 26, 2024

@pnowosie should be fixed, but workflows need running to confirm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants