You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/cli/configuration.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ You can manually create an [Organization Token](https://sentry.io/orgredirect/or
27
27
You can also sign in to your Sentry account (if you're not already) and create an Auth Token directly from this page.
28
28
29
29
<Alert>
30
-
Some CLI functionality, such as [Crons Monitoring](/product/monitors-and-alerts/monitors/crons/getting-started/cli/), is dependent on [Data Source Name (DSN)](/concepts/key-terms/dsn-explainer/) authentication.
30
+
Some CLI functionality, such as [Crons Monitoring](/cli/crons/), is dependent on [Data Source Name (DSN)](/concepts/key-terms/dsn-explainer/) authentication.
31
31
</Alert>
32
32
33
33
You can create an Auth Token from this page in one of the following three ways:
Copy file name to clipboardExpand all lines: docs/product/monitors-and-alerts/monitors/uptime-monitoring/index.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ You can also create an **Uptime Monitor** from the [Monitors](https://sentry.io/
22
22
Our uptime monitoring system verifies the availability of your URLs by performing HTTP requests at regular, pre-configured intervals. For a URL to be considered up and running, the response must meet the following criteria:
23
23
24
24
1.**Successful Response (2xx Status Codes):**
25
-
By default, the URL must return an HTTP status code in the 200–299 range, indicating a successful request. You can customize this behavior with [custom verification](/product/monitors-and-alerts/alerts/#uptime-monitoring-and-alerts) (early access).
25
+
By default, the URL must return an HTTP status code in the 200–299 range, indicating a successful request. You can customize this behavior with [custom verification](/product/alerts/create-alerts/uptime-alert-config/#5-verification) (early access).
26
26
2.**Automatic Handling of Redirects (3xx Status Codes):** Sentry will follow redirects for URLs returning an HTTP status code in the 300–399 range and verify that the final destination URL returns a successful response. This ensures that redirects won't falsely trigger downtime alerts.
27
27
3.**Timeout Setting:** Each request has a timeout threshold of 10 seconds.
28
28
If the server doesn't respond within this period, the check will be marked as a failure,
@@ -36,7 +36,7 @@ Our uptime monitoring system verifies the availability of your URLs by performin
36
36
An uptime alert continuously monitors the configured URL with the criteria defined above. If a failure occurs,
37
37
a new [uptime issue](/product/issues/issue-details/uptime-issues/) is created, including details about the failed check and related errors.
38
38
39
-
To prevent false alerts caused by temporary network issues, **an issue is only generated after three consecutive failures** (configurable via [thresholds](/product/monitors-and-alerts/alerts/#uptime-monitoring-and-alerts)) following the initial detection of downtime. Additionally, uptime checks are performed from a variety of geographical locations in a round-robin fashion. This ensures that each failed check comes from a different region, reducing the likelihood of false positives due to localized network failures.
39
+
To prevent false alerts caused by temporary network issues, **an issue is only generated after three consecutive failures** (configurable via [thresholds](/product/alerts/create-alerts/uptime-alert-config/#4-thresholds)) following the initial detection of downtime. Additionally, uptime checks are performed from a variety of geographical locations in a round-robin fashion. This ensures that each failed check comes from a different region, reducing the likelihood of false positives due to localized network failures.
40
40
41
41
_In rare cases where Sentry is unable to perform a scheduled uptime check—such as during outages—the check status will be marked as "Unknown"._
42
42
@@ -58,7 +58,7 @@ Uptime request spans are free and will not count against your [span quota](/pric
58
58
59
59
## Notifications
60
60
61
-
To start getting notifications for a new downtime issue, [configure an Alert](/product/monitors-and-alerts/alerts/#uptime-monitoring-and-alerts) that matches outage / downtime issues and add actions for email, Slack, on-call tools, or other integrations.
61
+
To start getting notifications for a new downtime issue, [configure an Alert](/product/monitors-and-alerts/alerts/#creating-an-alert) that matches outage / downtime issues and add actions for email, Slack, on-call tools, or other integrations.
Copy file name to clipboardExpand all lines: docs/product/monitors-and-alerts/monitors/uptime-monitoring/troubleshooting.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,4 +24,4 @@ See [IP Ranges](/security-legal-pii/security/ip-ranges/#uptime-monitoring) for a
24
24
25
25
## Verify That Issue Alerts Match Downtime Issues
26
26
27
-
Uptime monitors create downtime issues. If you're not receiving notifications when downtimes are detected, make sure you've [configured an Alert](/product/monitors-and-alerts/alerts/#uptime-monitoring-and-alerts) whose sources and filters match those issues, with actions for the channels you expect.
27
+
Uptime monitors create downtime issues. If you're not receiving notifications when downtimes are detected, make sure you've [configured an Alert](/product/monitors-and-alerts/alerts/#creating-an-alert) whose sources and filters match those issues, with actions for the channels you expect.
0 commit comments