Documentation for Monitors and Alerts #15041
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Bundle ReportChanges will decrease total bundle size by 5.47kB (-0.02%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
docs/product/automations/index.mdx
Outdated
|
|
||
| <Alert> | ||
|
|
||
| Automations are an Organization-level feature. By default, only owners, managers, and team admins can create, update, and delete Automations. |
There was a problem hiding this comment.
We should remove "team admins" from this list, since automations are org-scoped so there are no teams that own the automations.
By default, the org setting "Let Members Create and Edit Alerts" is actually ON, so all members can create automations. Would it worth pointing out where you can change this behavior in settings?
There was a problem hiding this comment.
Good to know! I'll update to mention where to change those settings.
docs/product/monitors/index.mdx
Outdated
|
|
||
| <Alert> | ||
|
|
||
| Monitors are a Project-level feature. By default, only owners, managers, and team admins can create, update, and delete Monitors. |
There was a problem hiding this comment.
Similar comment to https://github.com/getsentry/sentry-docs/pull/15041/files#r2392346270 , by default the org setting is actually ON so members can also create monitors.
There was a problem hiding this comment.
Got it! Thank you for calling that out.
There was a problem hiding this comment.
@ameliahsu - I cannot for the life of me find where that setting is. Mind pointing me in the right direction?
There was a problem hiding this comment.
No problem! In organization settings under "General Settings" you should see it if you scroll down to the "Membership" section
There was a problem hiding this comment.
Oh, but that's just for alerts. Is the plan to keep just this one setting for both? If so, we need to update the text.
|
|
||
| ### General Settings | ||
|
|
||
| Monitors are made of attributes that define when to create an issue, and actions that define what to do when an issue is created. |
There was a problem hiding this comment.
actions that define what to do when an issue is created
Is this referring to assigning the issue, setting a priority, etc? Just to refresh my memory, are we differentiating these actions from alerts/automation Actions through capitalization?
There was a problem hiding this comment.
Yes, that's what it's referring to. Do we officially want to call these capital A actions? Happy to update.
sfanahata
changed the title
…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/*)
DESCRIBE YOUR PR
We're rearranging documentation to show the new world of Monitors and Alerts.
This PR purposefully leaves
Alertsalone, as we'll be moving through beta before GA, and still getting clarity on timing of Alerts officially going away.Moved Crons and Uptime monitoring to 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: