Skip to content
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

Creating an alert using release.stage: adopted in the Sentry web UI throws a 500 error #70666

Open
arifken opened this issue May 10, 2024 · 3 comments

Comments

@arifken
Copy link

arifken commented May 10, 2024

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

  1. Navigate to Alerts > Create Alert > Crash free user rate
  2. Select a project and environment
  3. for filters, enter release.stage:adopted
  4. Set some thresholds below (I used 99.5 as critical, 99.7 as warning and 99.75 as recovery)
  5. Name the alert
  6. Click "Add alert"

Expected Result

The alert should be created and visible in the Alert list.

Actual Result

An error appears in lower right of the screen:
Screenshot 2024-05-10 at 9 38 57 AM

And in the console the message

Failed to load resource: the server responded with a status of 400 ()
us.sentry.io/api/0/organizations/REDACTED/alert-rules/?duplicateRule=false&referrer=alert_stream&sessionId=REDACTED&wizardV3=true:1 

Failed to load resource: the server responded with a status of 500 ()

Product Area

Alerts

Link

No response

DSN

No response

Version

No response

@getsantry
Copy link
Contributor

getsantry bot commented May 10, 2024

Assigning to @getsentry/support for routing ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented May 13, 2024

Routing to @getsentry/product-owners-alerts for triage ⏲️

@ceorourke
Copy link
Member

@iambriccardo I reproduced this and tracked the error id to this Sentry issue that's assigned to your team, can you take a look? I don't see a telemetry team on GitHub to assign this to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants