Skip to content

feat(Monitors and Alerts): Monitors and Alerts GA#17659

Merged
sfanahata merged 5 commits into
masterfrom
feat/monitors-and-alerts-ga
May 7, 2026
Merged

feat(Monitors and Alerts): Monitors and Alerts GA#17659
sfanahata merged 5 commits into
masterfrom
feat/monitors-and-alerts-ga

Conversation

@sfanahata

Copy link
Copy Markdown
Contributor

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.

  • Urgent deadline (GA date, etc.): ASAP
  • Other deadline:
  • 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

…eferencing /product/alerts to /product/monitors-and-alerts
@vercel

vercel Bot commented May 6, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sentry-docs Ready Ready Preview, Comment May 7, 2026 6:54pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
develop-docs Ignored Ignored Preview May 7, 2026 6:54pm

Request Review

@sfanahata

Copy link
Copy Markdown
Contributor Author

Unrelated external link https://imageoptim.com/ is 502ing right now.

Comment thread docs/integrations/notification-incidents/opsgenie/index.mdx Outdated

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

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

Comment thread redirects.js

@saponifi3d saponifi3d left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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.

Comment thread redirects.js
},
// Notifications docs live at /product/notifications/ (no longer under alerts or monitors-and-alerts)
{
source: '/product/alerts/notifications/:path*',

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Should we setup a redirect just incase any links were missed?

@sfanahata

sfanahata commented May 7, 2026

Copy link
Copy Markdown
Contributor Author

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.

@saponifi3d - I think this does that?

{
    source: '/product/alerts/:path*',
    destination: '/product/monitors-and-alerts/alerts/',
  },

Also, I think the notifications part is covered here:

{
    source: '/product/alerts/notifications/notification-settings/',
    destination: '/product/notifications/notification-settings/',
  },

I think a redirect like this is safest for now. It was a major change.

@saponifi3d

Copy link
Copy Markdown

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Ah, I can update.

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think this page needs to go away?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

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 coolguyzone left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Big lift! Updates and redirects look good.

@sfanahata sfanahata merged commit b278b60 into master May 7, 2026
20 checks passed
@sfanahata sfanahata deleted the feat/monitors-and-alerts-ga branch May 7, 2026 20:44
sentrivana pushed a commit that referenced this pull request May 18, 2026
## 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>
@github-actions github-actions Bot locked and limited conversation to collaborators May 23, 2026
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