You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to configure structured logging for the gtoken tool. I.e. we'd expect log messages to be optionally JSON formatted with a message, a severity, and a timestamp. This could be achieved by replacing log with slog.
Why
In production deployments all messages are currently classified as error given that there is no auxiliary information. Hence, our log alerting consistently triggers on messages from gtoken.
The text was updated successfully, but these errors were encountered:
What
We would like to configure structured logging for the
gtoken
tool. I.e. we'd expect log messages to be optionally JSON formatted with a message, a severity, and a timestamp. This could be achieved by replacinglog
with slog.Why
In production deployments all messages are currently classified as error given that there is no auxiliary information. Hence, our log alerting consistently triggers on messages from
gtoken
.The text was updated successfully, but these errors were encountered: