feat(Monitors and Alerts): Monitors and Alerts GA#17659
Conversation
…eferencing /product/alerts to /product/monitors-and-alerts
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Unrelated external link https://imageoptim.com/ is 502ing right now. |
…they are now unde Monitors and Alerts.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 714c153. Configure here.
saponifi3d
left a comment
There was a problem hiding this comment.
Doc updates and routing changes generally look good once that bot comment is addressed.
Not sure if we should have a catch all redirect or not, might be nice just in case we missed anything.
| }, | ||
| // Notifications docs live at /product/notifications/ (no longer under alerts or monitors-and-alerts) | ||
| { | ||
| source: '/product/alerts/notifications/:path*', |
There was a problem hiding this comment.
Should we setup a redirect just incase any links were missed?
@saponifi3d - I think this does that? Also, I think the notifications part is covered here: I think a redirect like this is safest for now. It was a major change. |
|
Ah yep! That covers it, woohoo! |
| <Alert> | ||
|
|
||
| Please note that in Alerts only a limited number of properties are available for [filtering transaction events](/product/alerts/create-alerts/metric-alert-config/#tags--properties). | ||
| Please note that in Alerts only a limited number of properties are available for filtering transaction events. |
There was a problem hiding this comment.
I think that this statement is misleading because it's not filtering transaction events its transaction.* values on span events. That being said https://docs.sentry.io/product/alerts/create-alerts/metric-alert-config/#tags--properties is going away it looks like.
| ### Creating Alerts | ||
|
|
||
| To create a metric alert rule for this transaction, click [Create Alert](/product/alerts-notifications/metric-alerts/) at the top of the page. | ||
| To create a metric alert rule for this transaction, click [Create Alert](/product/monitors-and-alerts/monitors/) at the top of the page. |
There was a problem hiding this comment.
I think this page needs to go away?
There was a problem hiding this comment.
Oh, I just did these PRs separately. Should have done the insights one based on this, but started them in parallel. This is going away. You can ignore.
coolguyzone
left a comment
There was a problem hiding this comment.
Big lift! Updates and redirects look good.
## DESCRIBE YOUR PR Deleting Alerts section, redirects added, updated all links in repo referencing /product/alerts to /product/monitors-and-alerts ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. - [x] Urgent deadline (GA date, etc.): ASAP - [ ] Other deadline: <!-- ENTER DATE HERE --> - [ ] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) --------- Co-authored-by: Shannon Anahata <shannonanahata@gmail.com>

DESCRIBE YOUR PR
Deleting Alerts section, redirects added, updated all links in repo referencing /product/alerts to /product/monitors-and-alerts
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: