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
Slack integration report device tag values differently to the Sentry UI #37656
Comments
Routing to @getsentry/ecosystem for triage. ⏲️ |
Hi @liamjones, thanks for reporting the issue. We'll backlog this for now and will prioritize this in the future. |
Hi @liamjones Could this be because the slack notification shows you the event that triggered the alert, but when you navigate to the issue, we show you the latest events, which is why you're seeing different tags? |
Hi @Dhrumil-Sentry - apologies for the delayed reply - nope, it's showing a different representation. An |
Environment
SaaS (https://sentry.io/)
Version
No response
Steps to Reproduce
device
tag.device
tag value is.Expected Result
Consistent result between Sentry UI and Slack alert.
Looks like the Slack notification takes the underlying model number but the UI translates it to a more friendly "marketing" name.
Actual Result
Sentry UI:
Slack notification:
The text was updated successfully, but these errors were encountered: