-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(alerts): Add info about custom metric alerts limitation #12797
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
feat(alerts): Add info about custom metric alerts limitation #12797
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
Bundle ReportChanges will decrease total bundle size by 15 bytes (-0.0%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
docs/product/alerts/alert-types.mdx
Outdated
| Metric alerts monitor macro-level metrics for both error and transaction events. A metric takes a set of events and computes an aggregate value using a function, such as `count()` or `avg()`, applied to the event properties over a period of time. When you create a metric alert, you can filter events by attributes and <PlatformLink to="/enriching-events/tags/">tags</PlatformLink>, which is particularly useful for aggregating across events that aren't grouped into single issues. Sentry has the following limits on metric alerts: | ||
|
|
||
| - **Organization**: A maximum of **1000 metric alerts** is allowed per organization. | ||
| - **Custom Metric**: A maximum of **50 custom metric alerts** is allowed per project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@priscilawebdev I don't think it's correct to say that the custom metric alerts limit is 50. I think these on-demand alerts can be created by picking any alert type under Performance or Custom (because they're based on the Transactions dataset). So for example it doesn't apply to metric alerts on Errors or Sessions data.
And within those types of alerts, they become on-demand when you use advanced filters, so I would suggest to maybe add the into about the limit here instead: https://docs.sentry.io/product/alerts/create-alerts/metric-alert-config/#advanced-filters-for-transactions
Also, this only applies to AM2 plans 🙈 I realise that on the latest version (AM3 plans) customers don't run into this. So maybe we can update the copy to "A maximum of 50 alerts with advanced filters is allowed per project on certain legacy plans."
@obostjancic, can you maybe confirm that what I said above is all true? 🙏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that makes total sense @ale-cota thank you! 🙏 Because I could not find anything mentioning 'on-demand' alerts, I assumed that it was 'custom metrics'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ale-cota yep, exactly!
85998cd to
b6f32de
Compare
Uh oh!
There was an error while loading. Please reload this page.