feat(Monitors and Alerts): Monitors and Alerts GA#17659
Open
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
|
Contributor
Author
|
Unrelated external link https://imageoptim.com/ is 502ing right now. |
…they are now unde Monitors and Alerts.
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
|  | ||
|
|
||
| If you'd rather be alerted when a specific metric crosses a threshold, you can set a [metric alert](/product/alerts/alert-types/#metric-alerts) by following the same steps as above. Once you've chosen the metric you want to be alerted about, click "Add Action", then select Opsgenie from the notification types dropdown. You can also select a custom priority for the alert, or leave it blank to use the default severity level that Sentry provides for incident statuses ("P1" for critical status and "P2" for warning status) | ||
| If you'd rather be alerted when a specific metric crosses a threshold, you can set a [Monitor](/product/monitors-and-alerts/monitors/) by following the same steps as above. Once you've chosen the metric you want to be alerted about, click "Add Action", then select Opsgenie from the notification types dropdown. You can also select a custom priority for the alert, or leave it blank to use the default severity level that Sentry provides for incident statuses ("P1" for critical status and "P2" for warning status) |
There was a problem hiding this comment.
Bug: The documentation for Opsgenie, PagerDuty, and MS Teams incorrectly directs users to the 'Monitors' page to configure notification actions, which is actually done in the 'Alerts' flow.
Severity: MEDIUM
Suggested Fix
Update the documentation for Opsgenie, PagerDuty, and MS Teams to reflect that notification actions are configured within the Alerts creation flow. Change the links and instructions to guide the user to the correct 'Alerts' page and workflow instead of the 'Monitors' page.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: docs/integrations/notification-incidents/opsgenie/index.mdx#L56
Potential issue: The integration documentation for Opsgenie, PagerDuty, and MS Teams
incorrectly states that notification actions are configured under 'Monitors'. The
documentation directs users to the Monitors page to 'Add Action', but this UI and
workflow actually exist within the 'Alerts' creation flow. Users following the
documentation will navigate to the wrong page and be unable to configure notifications
for these services, causing confusion and preventing them from completing the setup.
Also affects:
docs/integrations/notification-incidents/pagerduty/index.mdx:54docs/integrations/notification-incidents/msteams/index.mdx:60
Did we get this right? 👍 / 👎 to inform future reviews.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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: