-
Notifications
You must be signed in to change notification settings - Fork 3k
Add GCP complient tracing data to JSON logging #50368
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
base: main
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
6ae0003
to
27fe121
Compare
27fe121
to
9fdd9be
Compare
This comment has been minimized.
This comment has been minimized.
9fdd9be
to
220e271
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
🎊 PR Preview c3944a9 has been successfully built and deployed to https://quarkus-pr-main-50368-preview.surge.sh/version/main/guides/
|
...nsions/logging-json/runtime/src/main/java/io/quarkus/logging/json/runtime/JsonFormatter.java
Outdated
Show resolved
Hide resolved
220e271
to
2edf8e8
Compare
Status for workflow
|
A new JSON format option was created:
When this is used, tracing data is flatten and copied to the top level according to these semantics: https://cloud.google.com/logging/docs/structured-logging#structured_logging_special_fields
The logging level s also changed to
severity
.This is an output example:
Documentation for JSON logging was also improved.
I chose not to exclude the MDC field because it might contain other relevant data.