CLI option to specify logging level #1246

New Issue

2018-05-13T06:00:49+02:00

f97ada87 commented

2018-05-13 06:00:49 +02:00

(Migrated from github.com)

It would be nice to have a command line option to specify or override log_level (debug/info/warning/error) at runtime. Useful when diagnosing transient issues like connectivity problems, object propagation etc.

PeterSurda commented

2018-05-13 10:08:14 +02:00

(Migrated from github.com)

You can configure logging in the file logging.dat which follows the python logger standard, here is the documentation: https://docs.python.org/2/library/logging.config.html#logging-config-fileformat

You can configure logging in the file `logging.dat` which follows the python logger standard, here is the documentation: https://docs.python.org/2/library/logging.config.html#logging-config-fileformat

f97ada87 commented

2018-05-13 12:16:19 +02:00

(Migrated from github.com)

Thanks Peter, I was aware of that capability, however editing syntax-heavy files is not the type of immediate flexibility that I had in mind, Anyway, I'm happy to not waste developer bandwidth with this at the moment if you think it's unimportant. If/when I have time, I'll write the PR myself.

Thanks Peter, I was aware of that capability, however _editing syntax-heavy files_ is not the type of _immediate_ flexibility that I had in mind, Anyway, I'm happy to not waste developer bandwidth with this at the moment if you think it's unimportant. If/when I have time, I'll write the PR myself.

PeterSurda commented

2018-05-13 12:56:19 +02:00

(Migrated from github.com)

Maybe a PR that would put a couple of examples into the ~logging~ contrib directory would help. Changing logging settings is more of a developer activity rather than an end-user activity so I don't think a command line switch is the best approach.

dimyme commented

2018-09-20 12:05:11 +02:00

(Migrated from github.com)

the github wiki has info on logging

This repo is archived. You cannot comment on issues.