Verbosity/Logging

15 views
Skip to first unread message

Thomas Müller

unread,
Feb 28, 2017, 4:17:12 PM2/28/17
to grid-control
Dear experts,

I need to find some debug output while running go.py, which I previously
did with -v 3, for example. Now I see these options

> -v, --verbose Give detailed information during run
> (use multiple times to increase verbosity)
> -l, --logging <opt> Specify logger and log level using
> "<logger>:<level>"
> (<level>: ERROR, CRITICAL, WARNING,
> INFO..INFO3, DEBUG...DEBUG3)

but it is not clear what to specify for <logger>. Could somebody please
let me know the possible options there or point me to the relevant
documentation? Thanks.

Regards,
Thomas

Fred Stober

unread,
Mar 1, 2017, 12:56:17 AM3/1/17
to grid-control, t.mu...@cern.ch
Hi,

-v increases the global verbosity
--logging can increase the global verbosity, but also allows to filter, which logging messages should be shown

--logging can increase the global verbosity (the same way as -vvvvvvvv) by using
--logging DEBUG3

After increasing the verbosity with "-vvvv" you get this for example
xxxx-xx-xx xx:xx:xx - classloader.report:DEBUG - Successfully loaded class

If you are only interested in "classloader.report" DEBUG messages, one should use
--logging classloader.report:DEBUG

There is no full list of available loggers yet (since the logger is usually found as described above), but a quick grep+sed through the source code for getLogger calls gives these loggers:

backend
classloader
config
console - this logger is used for user output and can be used to silence grid-control on the command line
jobs
logging
matcher
parameters
process - this can give information about all external commands
report
requests
task
thread_pool
webservice
workflow

Cheers,
Fred
Reply all
Reply to author
Forward
0 new messages