Could you describe in more detail what you have been trying to debug, and
what information you couldn't get to?
To see what classes are invoked it is enough to configure logging subsystem
such that it produces that info. See:
https://docs.jboss.org/author/display/WFLY10/Logging+Configuration
(especially the comment by James Perkins at the bottom of the page) and
sub-chapters. There's more in-depth info at this page:
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...
You can see full http requests, and responses by properly configuring
undertow loggers, or even adding logging interceptors to undertow (see:
https://mirocupak.com/logging-requests-with-undertow/)
I think we should have enough logging in place to support common issues. So
it's important to let us know what you were trying to debug and what info
was missing for you. But we will almost certainly not apply logging that
displays method arguments across our codebase, because that's just too much
logging. Such verbose logging is better solved with class instrumentation
(e.g. by using project Byteman -
byteman.jboss.org).
On Fri, Oct 20, 2017 at 8:11 AM, Narendra Kadali <narendra(a)naidmincloud.com>
wrote:
Hi,
I feel that logging information in Keycloak is not sufficient to debug
issues. Sometimes I struggle to debug issues in our environment due to lack
of enough logs. When I look at the Keycloak source code, I noticed that
most of the classes doesn't have any loggers in it code.
I believe that with logs we should be able to identify what classes are
being called for executing an request and what data is passed to various
methods. This will make our life simple while debugging issues.
Do we have any plans for enhancing existing logging in Keycloak?
Thanks!
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev