Log level override for services #37

New issue

Closed

opened 2019-02-07 01:23:21 +00:00 by jamie · 4 comments

jamie commented

2019-02-07 01:23:21 +00:00

(Migrated from git.hazaar.io)

Services should be able to have their own log level. That mean, you might have the Warlock server itself on W_INFO to limit the logs, but the service may want W_DEBUG so you can diagnose issues.

At the moment, the service sends all of it's log messages and it's up to the server to filter out based on the set log level. This should make it fairly easy to instead use the service log level (which defaults to the global log level if not set) to filter out messages. Alternatively, we could get it to not send log messages so the service class itself filters out. The difference here is that we would need to negotiate the log level on startup.

Services should be able to have their own log level. That mean, you might have the Warlock server itself on W_INFO to limit the logs, but the service may want W_DEBUG so you can diagnose issues. At the moment, the service sends all of it's log messages and it's up to the server to filter out based on the set log level. This should make it fairly easy to instead use the service log level (which defaults to the global log level if not set) to filter out messages. Alternatively, we could get it to not send log messages so the service class itself filters out. The difference here is that we would need to negotiate the log level on startup.

jamie commented

2019-02-07 01:23:27 +00:00

(Migrated from git.hazaar.io)

created merge request !16 to address this issue