Repository navigation
Request Logging, v1
#10473
Replies: 2 comments 1 reply
|
We have a number of request "categories" such as:
I would imagine that commonly people will want to enable one of these, and not all. Not sure if we would want something like |
1 reply
|
With regard to the log category if we use |
|
until this is developed, whats the best way to have acess logs enabled? |
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.
A very common scenario is to troubleshoot the requests from and to Keycloak, a.k.a. a HTTP Access log. Quarkus gives us some things out of the box, see https://quarkus.io/guides/http-reference#configuring-http-access-logs
Proposal for V1:
Have a new configuration property
log-request-enabled=true/falsethat internaly maps toquarkus.http.access-log.enabledand a dedicated log category set calledorg.keycloak.request(by usingquarkus.http.access-log.category=org.keycloak.requestinternally.There are other options to consider, but this is a basic V1, enabling ppl to just use
kc.sh start --log-requests-enabled=true. wdyt?All reactions