Transaction Duration Metric Alerts not being triggered when an environment is selected

[InterstellarStella]

Environment

SaaS (https://sentry.io/)

Version

No response

Link

No response

DSN

No response

Steps to Reproduce

1. Create a "Transaction Duration" metric alert and choose an environment within the rules as follows:

2. Manually trigger the alert

Expected Result

The alert gets triggered and changes state from "Resolved" to "Warning".

Actual Result

The alert does not get triggered and the state remains on "Resolved", even though the graph indicates that it should have been triggered.

If in the alert rules we choose "All Environments" instead

the alert works as expected

• Example alert working
• Example alert not working
  

[getsantry]

Assigning to @getsentry/support for routing, due by Friday, March 31st at 5:00 pm (sfo). ⏲️

[getsantry]

Routing to @getsentry/workflow for triage, due by Monday, April 3rd at 5:00 pm (sfo). ⏲️

[brianthi]

From Dan:

did a few tests:
transaction durations with env: never fires
transaction durations without env: fires
error counts with env: fires

[illing2005]

Do you have any update on this?

[wedamija]

@illing2005 Sorry for the lack of follow up here. The bug was specific to performance alerts that had an environment specified. We've fixed this, so alerts like this should be working as expected now. Please let me know if this is not the case and I'll re-open this issue.

[illing2005]

Thanks for the update!
I will try it out