feat: Monitors alerts LA version #15550
Open
Conversation
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
added 12 commits
September 24, 2025 16:30
…h directory changes.
Resolved conflicts: - docs/product/alerts/index.mdx: Kept new alert description and sidebar_order, added og_image from master - docs/security-legal-pii/security/data-retention-periods.mdx: Merged retention period updates from master with documentation links - Removed 6 old alert documentation files that were restructured (alert-types.mdx, create-alerts/*)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
sfanahata
changed the title
| }, | ||
| "status": "in_progress" | ||
| } | ||
| ``` |
There was a problem hiding this comment.
Bug: JSON Syntax Errors Break Monitor Example
Invalid JSON syntax in the monitor upsert example. Line 118 is missing a comma after "timezone": "America/Los_Angeles", and line 120 has a trailing comma after "recovery_threshold": 1, which is invalid JSON. These errors will prevent the example from working when copied and used.
|
|
||
| <Expandable title="Why aren't recurring job errors showing up on my monitor details page?"> | ||
|
|
||
| You may not have [linked errors to your monitor](/product/new-monitors-and-alerts/monitors/crons/getting-started/http/#connecting-errors-to-cron-monitors). |
There was a problem hiding this comment.
Bug: Troubleshooting Link Leads Nowhere
Broken link reference. The troubleshooting page links to #connecting-errors-to-cron-monitors anchor in the HTTP getting started guide, but this section doesn't exist in that file. This will result in a broken anchor link that users won't be able to navigate to.
Bundle ReportChanges will increase total bundle size by 75.41kB (0.32%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-client-array-pushAssets Changed:
view changes for bundle: sentry-docs-server-cjsAssets Changed:
|
ameliahsu
added a commit
to getsentry/sentry
that referenced
this pull request
Nov 19, 2025
updated links according to getsentry/sentry-docs#15550 we'll be keeping monitors/alerts docs in a separate folder during LA so that they're still published/accessible but don't interfere with the structure of existing docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Created an LA directory for "new monitors and alerts"
Preview:
https://sentry-docs-git-monitors-alerts-la-version.sentry.dev/product/new-monitors-and-alerts/
https://sentry-docs-git-monitors-alerts-la-version.sentry.dev/product/new-monitors-and-alerts/alerts/
https://sentry-docs-git-monitors-alerts-la-version.sentry.dev/product/new-monitors-and-alerts/monitors/
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: