Skip to content

Commit 3aefcc5

Browse files
committed
removing beta text and clarifying automatic instrumentation
1 parent 68fa560 commit 3aefcc5

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

docs/product/alerts/uptime-monitoring/automatic-detection.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,9 @@ sidebar_order: 51
44
description: "Learn how automatic detection of uptime monitoring works."
55
---
66

7-
<Include name="feature-stage-beta-uptime.mdx" />
8-
97
In order to be able to automatically detect uptime alerts, we analyze all the URLs detected in your project's captured error data to find the hostname that appears most frequently. This helps ensure that your most critical hostname is continuously monitored, enhancing the reliability and availability of your web services. We then create an uptime alert if it passes our [uptime check criteria](/product/alerts/uptime-monitoring/#uptime-check-criteria). Automatic uptime checks are configured to run once a minute as GET requests.
108

11-
9+
The automatic creation of Uptime Monitors only happens if there are no other existing uptime monitors configured.
1210

1311
To avoid creating flaky alerts, the hostname undergoes an "onboarding period" of three days. During this period, we send HTTP requests to the hostname every hour. If the request fails three times or more, the hostname will be dropped and re-evaluated after seven days.
1412

0 commit comments

Comments
 (0)