-
Notifications
You must be signed in to change notification settings - Fork 312
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
fix: add log severity #10835
fix: add log severity #10835
Conversation
case 'debug': | ||
case 'verbose': | ||
severity = 'DEBUG'; | ||
break; | ||
case 'info': | ||
severity = 'INFO'; | ||
break; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WDYT about mapping debug
to DEBUG
, verbose
to INFO
, and info
to NOTICE
, so we keep that extra granularity? It may be confusing that our infos get propagated as notice instead of info though...
formatters: { | ||
level: levelToSeverityFormatter, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to apply this formatter to the stdio transport only? We don't need to make this change in the OTEL transport.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the pino docs, no. But I'm not sure if that means we can't customize the log level at all or if we can't customize it per transport.
https://github.com/pinojs/pino/blob/main/docs/api.md#level
Changes to circuit sizes
🧾 Summary (100% most significant diffs)
Full diff report 👇
|
An attempt to get log levels recognized by Google's Log Explorer service