We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
👋
What version are you running?
"10.2.0"
When using Logger.error, deeply nested :sentry metadata gets silently dropped.
Logger.error
:sentry
For example, this event is stored without any additional information:
Logger.error("error from logs x1", sentry: %{extra: %{response: Bamboo.ApiError.build_api_error("response info")}})
But these two get stored with the expected additional information:
Logger.error("error from logs x2", sentry: %{extra: %{response: "response info"}}) Sentry.capture_message("error from logs x3", extra: %{response: Bamboo.ApiError.build_api_error("response info")})
The text was updated successfully, but these errors were encountered:
I tried it out on Sentry 10.8.1 and it seems to be already fixed.
Sorry for a false alarm!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
👋
Environment
What version are you running?
Steps to Reproduce
When using
Logger.error
, deeply nested:sentry
metadata gets silently dropped.For example, this event is stored without any additional information:
But these two get stored with the expected additional information:
The text was updated successfully, but these errors were encountered: