Invalid metric error when creating metric alert

[rodolfoBee]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Go to alerts
2. Create a new alert with Custom measurement
3. Under "Define your metric" select " Custom measurement - p95 - spans.ui - 4h internval"
4. Set any threshold, actions and alert name
5. Try to save the alert

Expected Result

The alert is created.

Actual Result

Internal error: Invalid Metric: We do not currently support this field.
Most likely from this line: https://github.com/getsentry/sentry/blob/master/src/sentry/incidents/serializers/alert_rule.py#L158-L175

Product Area

Alerts

Link

No response

DSN

No response

Version

No response

[getsantry]

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

[rachrwang]

@wedamija - do you know what might be the cause of this problem?

[dalnoki]

I have a customer who reported the same, but they used p95, spans.ui and 4 hour interval:

[ceorourke]

@iambriccardo do you have insight into this? It looks like you've done some work around this - it's checking the organizations:custom-metrics flag which is set to false by default and I don't see it in options automator or getsentry, so it might not work for any customers.

[minori-fh]

I have a customer who reported the same but they used spans (beta), sum, a custom measurement, and 30 minute interval

[krzysztofjablonski]

Hey @minori-fh, do you have any updates on the bug?

[rodolfoBee]

There is another report for this issue.

In this case, the user wants to use a custom measurement created with setMeasurement but it is not available in the list. The same measurement is used in Dashboards with no issues.

@mifu67 @ceorourke do you have any update on the issue?

[mifu67]

Hey @rodolfoBee,

Our team doesn't currently have the bandwidth to investigate this, but I've added it to our backlog.

[masinette]

Related to: https://sentry.zendesk.com/agent/tickets/152900