Are our log messages logged at the right severity? #152
josephdecock
started this conversation in
General
Replies: 1 comment 4 replies
-
|
I would say "mostly yes" but sometimes things are logged as errors that may not be actual errors. From another issue I logged, ""Client secret validation failed for client" doesn't need to be an error in my understanding - it can just mean someone has configured a client wrong. This message is logged as an error, but it's not an error in the software, it's a kind of expected condition for client's that aren't setup right, or whatever. A bit like a wrong password, it's not a software error. We think it should be downgraded to a warning or even just an info... |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We sometimes hear from users who would prefer some of our log messages to be logged at a different level. We'd like to make our logs as useful as possible, but we also know that many users have metrics and alerts that are sensitive to log levels. We don't want to make useful alerts stop working, but we also don't want false positives for on-call support types. That's why we treat a log message's severity as an API contract and keep them stable.
We're considering a few options for how to approach this problem in the future:
We'd love to hear from you!
Beta Was this translation helpful? Give feedback.
All reactions