Add Uptime Monitoring Documentation #10810
Merged
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 decrease total bundle size by 3 bytes ⬇️
|
lizokm
approved these changes
Jul 25, 2024
Co-authored-by: Liza Mock <[email protected]>
…stead of full string
| 1. **Successful Response (2xx Status Codes):** | ||
| The URL must return an HTTP status code in the 200–299 range, indicating a successful request. | ||
| 2. **Automatic Handling of Redirects (3xx Status Codes):** URLs returning an HTTP status code in the 300–399, indicating a redirect, will trigger Sentry to automatically follow the redirect and verify that the final destination URL returns a successful response. This ensures that redirects won't falsely trigger downtime alerts. | ||
| 3. **Timeout Setting:** Each request has a timeout threshold of 10 seconds. |
There was a problem hiding this comment.
It's actually 5 seconds right now isn't it @wedamija ?
Co-authored-by: Evan Purkhiser <[email protected]>
gaprl
added a commit
to getsentry/sentry
that referenced
this pull request
Aug 6, 2024
Updates the uptime checker `User-Agent` to match what we have described in our [documentation PR.](getsentry/sentry-docs#10810)
wedamija
approved these changes
Aug 6, 2024
Comment on lines
+26
to
+31
| Alternatively, the hostname's `robots.txt` can be updated to disallow Sentry: | ||
|
|
||
| ```txt{tabTitle: Example}{filename: robots.txt} | ||
| User-agent: SentryUptimeBot | ||
| Disallow: * | ||
| ``` |
There was a problem hiding this comment.
Note that this will just disable detection at the moment, it won't disable an ongoing checker (even in onboarding mode)
| 1. **Successful Response (2xx Status Codes):** | ||
| The URL must return an HTTP status code in the 200–299 range, indicating a successful request. | ||
| 2. **Automatic Handling of Redirects (3xx Status Codes):** URLs returning an HTTP status code in the 300–399, indicating a redirect, will trigger Sentry to automatically follow the redirect and verify that the final destination URL returns a successful response. This ensures that redirects won't falsely trigger downtime alerts. | ||
| 3. **Timeout Setting:** Each request has a timeout threshold of 10 seconds. |
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.
DESCRIBE YOUR PR
Adds new pages describing our new uptime monitoring feature, and updates various other relevant pages to reference uptime alerts.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: