We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm not sure if this is a bug or expected behaviour, but when log_level is set to logging.INFO, I still get debug messages in the log, like so:
July 24 22:09:39 graphios.py DEBUG graphios sleeping. July 24 22:09:54 graphios.py DEBUG Processing spool directory /var/spool/graphios July 24 22:09:54 graphios_backends.py DEBUG Connecting to carbon at 172.12.0.10:2004 July 24 22:09:54 graphios_backends.py DEBUG connected July 24 22:09:54 graphios.py DEBUG deleted /var/spool/graphios/service-perfdata.1500934190 July 24 22:09:54 graphios.py DEBUG deleted /var/spool/graphios/host-perfdata.1500934190 July 24 22:11:24 graphios.py INFO Processed 0 files (0 metrics) in /var/spool/graphios
Should I be seeing those debug messages?
Thanks, Guy
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm not sure if this is a bug or expected behaviour, but when log_level is set to logging.INFO, I still get debug messages in the log, like so:
July 24 22:09:39 graphios.py DEBUG graphios sleeping.
July 24 22:09:54 graphios.py DEBUG Processing spool directory /var/spool/graphios
July 24 22:09:54 graphios_backends.py DEBUG Connecting to carbon at 172.12.0.10:2004
July 24 22:09:54 graphios_backends.py DEBUG connected
July 24 22:09:54 graphios.py DEBUG deleted /var/spool/graphios/service-perfdata.1500934190
July 24 22:09:54 graphios.py DEBUG deleted /var/spool/graphios/host-perfdata.1500934190
July 24 22:11:24 graphios.py INFO Processed 0 files (0 metrics) in /var/spool/graphios
Should I be seeing those debug messages?
Thanks,
Guy
The text was updated successfully, but these errors were encountered: