Skip to content
New issue

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

Log messages sent to stdout absent from GCP Log Explorer #595

Open
leplatrem opened this issue Apr 16, 2024 · 3 comments
Open

Log messages sent to stdout absent from GCP Log Explorer #595

leplatrem opened this issue Apr 16, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@leplatrem
Copy link
Contributor

eg. heartbeat messages, autograph response status, etc.

@leplatrem leplatrem added the bug Something isn't working label Apr 16, 2024
@alexcottner
Copy link
Contributor

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

@alexcottner
Copy link
Contributor

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:

  • kinto
  • kinto.core
  • kinto.core.authorization

@leplatrem
Copy link
Contributor Author

leplatrem commented May 2, 2024

update: that's already a big improvement :) thank you @alexcottner and GG for spotting the culprit

We instantiate logger in kinto_remote_settings too.

Does this mean we also have to explicit add it the conf too?
I still don't get why root doesn't mean "all"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants