Skip to content

Conversation

@priscilawebdev
Copy link
Member

@priscilawebdev priscilawebdev commented Feb 21, 2025

@vercel
Copy link

vercel bot commented Feb 21, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sentry-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 21, 2025 11:46am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
changelog ⬜️ Ignored (Inspect) Visit Preview Feb 21, 2025 11:46am
develop-docs ⬜️ Ignored (Inspect) Visit Preview Feb 21, 2025 11:46am

@priscilawebdev priscilawebdev requested review from a team and ale-cota February 21, 2025 08:01
@priscilawebdev priscilawebdev marked this pull request as ready for review February 21, 2025 08:01
@codecov
Copy link

codecov bot commented Feb 21, 2025

Bundle Report

Changes will decrease total bundle size by 15 bytes (-0.0%) ⬇️. This is within the configured threshold ✅

Detailed changes
Bundle name Size Change
sentry-docs-server-cjs 10.94MB -9 bytes (-0.0%) ⬇️
sentry-docs-client-array-push 9.39MB -6 bytes (-0.0%) ⬇️

Affected Assets, Files, and Routes:

view changes for bundle: sentry-docs-server-cjs

Assets Changed:

Asset Name Size Change Total Size Change (%)
1729.js -3 bytes 1.71MB -0.0%
../instrumentation.js -3 bytes 1.04MB -0.0%
9523.js -3 bytes 1.02MB -0.0%
view changes for bundle: sentry-docs-client-array-push

Assets Changed:

Asset Name Size Change Total Size Change (%)
static/chunks/pages/_app-*.js -3 bytes 865.35kB -0.0%
static/chunks/1298-*.js -3 bytes 401.61kB -0.0%
server/middleware-*.js 5.55kB 6.55kB 555.3% ⚠️
server/middleware-*.js -5.55kB 1.0kB -84.74%
static/iURVvqwHWkrfWSjyrDm41/_buildManifest.js (New) 578 bytes 578 bytes 100.0% 🚀
static/iURVvqwHWkrfWSjyrDm41/_ssgManifest.js (New) 77 bytes 77 bytes 100.0% 🚀
static/C8XBVuK1GF4DGbn0s40wU/_buildManifest.js (Deleted) -578 bytes 0 bytes -100.0% 🗑️
static/C8XBVuK1GF4DGbn0s40wU/_ssgManifest.js (Deleted) -77 bytes 0 bytes -100.0% 🗑️

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.
Copy link
Contributor

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."

Screenshot 2025-02-21 at 11 58 35

@obostjancic, can you maybe confirm that what I said above is all true? 🙏

Copy link
Member Author

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'.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ale-cota yep, exactly!

@priscilawebdev priscilawebdev force-pushed the priscila/ref/alerts/add-info-about-custom-metric-limit branch from 85998cd to b6f32de Compare February 21, 2025 11:18
@priscilawebdev priscilawebdev merged commit 9e7f884 into master Feb 21, 2025
11 checks passed
@priscilawebdev priscilawebdev deleted the priscila/ref/alerts/add-info-about-custom-metric-limit branch February 21, 2025 14:35
@github-actions github-actions bot locked and limited conversation to collaborators Mar 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants