Standard way to determine Logger Name for which you need to change logging level setting
Every time I need to debug some standard rule or integration component I am searching PDN and trying to guess for which logger I need to enable DEBUG level. Even if I know the name but I make a misprint (they are case-sensitive) I will never know about it. Logging level setting tool allows you to enter whatever logger name.
2 years ago I enabled debug mode for email correspondence after raising an SR Support sent me the Logger Name. I would like to enable Debug again, but now I do not remeber the Logger Name. Do you?
What is the standard way to determine the Logger Name?
Where may we find the list of "Popular loggers" with searchable descriptions?
The root logging entry assigns default log level to ALL rules, can be overridden using specific categories mentioned previously. The priority value attribute specifies the log level. The appender-ref ref attribute indicates the Appender
The following example sets ALERT as the default log level and references two appenders ASYNC and ALERT-ASYC
Below example is based on the rule type category name.
Dunnd, thank you for the reply. Could you, please, be a little more specific: how may I determine the logger for Service SOAP or sending emails, so that I could override the standard logging level for them?
alibj, thank you for the reply. There are many loggers, I would like to at least be able to search for a string their names contain.
JonnyGar, it is rather difficult to use these loggers as the UI is currently implemented.
JonnyGar, thank you for the link. I obtained access to this new portal, it is nice there, though I think it is a huge problem to have 2 wiki-like websites with restricted access. Will have to sinchronize information between them all the time.
Back to the topic - I have found the logger enabling which puts request and response XML to the log file.
I had to manually try about 50 loggers which look like it.
It is not yet in that file you gave me a link to, we should add it there.
Now I would like to find an activity which gets called right after the service is called, so to incorporate my own logger which puts request-response XML for all SOAP services to DB-table. Tracer did not help me with the search as it traces the thread already after the inbound XML is parsed.