JSON logging format
#10209
Replies: 2 comments 2 replies
-
|
Hey. On point 1 i am totally aligned and will provide a PR shortly. Can you elaborate a bit more on point 2? What option would you set and what would be your expected outcome/log output? Thanks! |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Initial json console logging support is now in latest main, see #10576 - expect some more options when we get to #10618 - we need quarkus 2.8.0 to be released though. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Wildfly based Keycloak provides option to change logging format to JSON, e.g.:
Quarkus based Keycloak doesn't have this option (v 17.0.0). generated logs are in the text format only. Logging options:
Naive solution with current config option:
doesn't work very well - it may generate empty fields, (e.g. empty exception, when there is no exception).
It will help if Keycloak admin will have easy option switch from the text log format to json format (which can be then parsed easily with standard logging tools). This probably can be easily implemented via quarkus extension
quarkus-logging-json.It will help if also full message (
%m)/short message (%s) is generated in the JSON format. Use case: Keycloak event messages don't need additional parsing - default Keycloak JSON logs will be enough to generate/calculate/aggregate all possible metrics/reports, e.g. succesfull/failed logins of (unique) users/clients per selected time period, ...Example of Keycloak event in the text format:
Which should be logged in the JSON format as:
@dasniko mentioned that in the community:
Beta Was this translation helpful? Give feedback.
All reactions