Skip to content

Commit 08c493c

Browse files
gaprllucas-zimerman
authored andcommitted
docs: Update uptime monitoring automatic detection disable instructions (#14455)
This PR updates the uptime monitoring documentation to: - Remove the unsupported robots.txt option for disabling automatic detection - Emphasize that deleted uptime alerts won't be re-created automatically - Simplify the disabling section for better clarity The robots.txt feature is not currently supported, so the best way to disable automatic detection is to simply delete the uptime alert.
1 parent 344c363 commit 08c493c

File tree

1 file changed

+2
-14
lines changed

1 file changed

+2
-14
lines changed

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

Lines changed: 2 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -21,18 +21,6 @@ Once an automatically detected uptime alert has been created, you'll be able to
2121

2222
## Disabling Automatic Detection
2323

24-
If you prefer not to use automatically detected uptime alerts, you have two options for disabling them:
24+
If you prefer not to use automatically detected uptime alerts, you can delete them directly from your [Alerts page](https://sentry.io/orgredirect/organizations/:orgslug/alerts/rules).
2525

26-
1. **Deleting Uptime Alerts:** You can directly delete existing automatically detected uptime alerts from your [Alerts page](https://sentry.io/orgredirect/organizations/:orgslug/alerts/rules). Once deleted, these alerts will not be re-created automatically in the future.
27-
2. **Blocking Sentry via `robots.txt`:** Another method to prevent automatic detection is by updating your hostname's robots.txt file to block Sentry’s uptime monitoring bot. To do this, add the following lines to your robots.txt file:
28-
29-
```txt{tabTitle: Example}{filename: robots.txt}
30-
User-agent: SentryUptimeBot
31-
Disallow: *
32-
```
33-
34-
<Alert level="warning">
35-
**Note:** The `robots.txt` file only prevents Sentry from detecting URLs that
36-
it encounters after its been implemented. Existing URLs that have already been
37-
detected will continue to have uptime alerts unless they're manually deleted.
38-
</Alert>
26+
**Once deleted, these automatically detected uptime alerts will not be re-created in the future.**

0 commit comments

Comments
 (0)