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
eg. heartbeat messages, autograph response status, etc.
The text was updated successfully, but these errors were encountered:
Based on my local testing, I think we at least need to add an explicit log config section for kinto. Example:
[loggers] keys = root, kinto, summary .... [logger_kinto] level = INFO handlers = console qualname = kinto
Sorry, something went wrong.
Changes have been deployed. We're now seeing at least some logs that we were missing, unsure if this is everything. New log types we're seeing:
update: that's already a big improvement :) thank you @alexcottner and GG for spotting the culprit
We instantiate logger in kinto_remote_settings too.
kinto_remote_settings
remote-settings/kinto-remote-settings/src/kinto_remote_settings/signer/utils.py
Line 17 in 96b025c
Does this mean we also have to explicit add it the conf too? I still don't get why root doesn't mean "all"
root
No branches or pull requests
eg. heartbeat messages, autograph response status, etc.
The text was updated successfully, but these errors were encountered: