Uptime Monitoring Docs Updates #12501
Merged
+107
−51
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Bundle ReportChanges will increase total bundle size by 354 bytes (0.0%) ⬆️. 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:
|
coolguyzone
reviewed
Feb 3, 2025
|
|
||
|
|
||
| | Team PAYG | Business PAYG | | ||
| | ---------- | -------------- | | ||
| | $0.7800000 | $0.7800000 | | ||
|
|
||
| #### Uptime Monitors Pricing | ||
|
|
||
| All Sentry plans include **one uptime monitor**. To activate additional uptime monitors, set up a **Pay-As-You-Go (PAYG) budget**. Additional uptime monitors can't be purchased in advance; they are only available through your PAYG budget, which can be shared across all event types. |
There was a problem hiding this comment.
I noticed 'PAYG' is defined above under 'Terminology', is it worth re-defining here?
There was a problem hiding this comment.
I left it here to be consistent with whats in Crons. Lets leave it for now since its close in context here.
coolguyzone
reviewed
Feb 3, 2025
jarrettscott
approved these changes
Feb 3, 2025
Co-authored-by: Alex Krawiec <[email protected]>
* Remove uptime monitoring section from early adopter features documentation * Move disable uptime error tracing to an expandable * add more info on uptime alert details page * fix typo in Alert Details description for uptime checks * Enhance uptime monitoring documentation with detailed failure criteria and notification setup * add reference to multi-region uptime monitoring support * Refine uptime alert configuration documentation for clarity and detail * Add Uptime Monitoring section to product documentation
codyde
changed the title
coolguyzone
reviewed
Feb 5, 2025
|
|
||
| Here’s a list of the types of data that will be stored in both data storage location (US and EU). | ||
|
|
||
| - Uptime checks |
There was a problem hiding this comment.
Are there plans to add to this list soon? Having a list of one feels a little weird.
There was a problem hiding this comment.
I think it emphasizes it well, so lets keep it
coolguyzone
reviewed
Feb 5, 2025
coolguyzone
reviewed
Feb 5, 2025
| - Include a `Content-Type` header if required by the target URL. For example, a JSON payload should have `Content-Type: application/json`. | ||
| - The selected interval affects downtime detection speed. Sentry triggers an uptime issue after three consecutive failures. For instance, with a 5-minute interval, downtime is detected at least 15 minutes after the first failure. Learn more about the [uptime check criteria](/product/alerts/uptime-monitoring/#uptime-check-criteria). | ||
| - In case the specified URL is behind a firewall, make sure Sentry's Uptime Bot can execute requests to it. [Learn more](/product/alerts/uptime-monitoring/troubleshooting/#verify-firewall-configuration). | ||
| - Sentry Uptime Tracing automatically appends a sentry-trace header to outgoing requests for distributed tracing. [Learn more](/product/alerts/uptime-monitoring/uptime-tracing/). |
There was a problem hiding this comment.
Suggested change
| - Sentry Uptime Tracing automatically appends a sentry-trace header to outgoing requests for distributed tracing. [Learn more](/product/alerts/uptime-monitoring/uptime-tracing/). | |
| - Sentry Uptime Tracing automatically appends a sentry-trace header to outgoing requests for distributed tracing. Learn more about [distributed tracing with uptime](/product/alerts/uptime-monitoring/uptime-tracing/). |
coolguyzone
reviewed
Feb 5, 2025
| ## 4. Alert Name | ||
|
|
||
| Give your alert a descriptive name, for example, "Landing Page" or "Contact Page". | ||
|
|
||
| ## 5. Ownership | ||
|
|
||
| Lastly, choose a team to associate with your alert so that members of that team are able to edit the alert if they want to. Note, that you can only add teams that you're a member of. If no team is assigned, anyone will be able to edit the alert. | ||
| Assign a team or team member to manage the alert. If no team is assigned, any user can modify the alert. [Uptime issues](/product/issues/issue-details/uptime-issues/) created from this alert rule will be set to the specified team or team member. |
There was a problem hiding this comment.
Should 'set to the specified team . . .' be 'sent'?
coolguyzone
reviewed
Feb 5, 2025
Co-authored-by: Alex Krawiec <[email protected]>
Co-authored-by: Alex Krawiec <[email protected]>
gaprl
approved these changes
Feb 6, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Updating docs with relevant uptime monitoring changes for exiting beta, including pricing informaitons, and clarifying crons vs uptime monitors
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.