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
{{ message }}
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.
I would like to add tags for each message and then create an alert rule for some tags and send email notification. It would be nice if these options can be sent with message for example logger.error({ data, error }, "Message", { tags: {test: "testTag"} })
The text was updated successfully, but these errors were encountered:
Then this would not be a part of logger options, but of each logged entry non? This would require either changing the API that is inherited from pino, or adding some reserved fields to message. Which of the two options is more desirable @stefan-prokop-cz @vlasy?
Well i think its not necessary to have sentry options as a part of each logged entry. Its ok for me to have sentry options as part of logger options.
My use case: add sentry tag to one concrete log entry - it would be nice to add this tag to the specific log entry instead of create a new logger instance .. but i dont care
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Can we add sentry capture context to the logger options?
I would like to add tags for each message and then create an alert rule for some tags and send email notification. It would be nice if these options can be sent with message for example
logger.error({ data, error }, "Message", { tags: {test: "testTag"} })
The text was updated successfully, but these errors were encountered: