Automatic Detection
Learn how automatic detection of uptime monitoring works.
In order to be able to automatically detect Uptime Monitors, 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 Monitor if it passes our uptime check criteria. Automatic uptime checks are configured to run once a minute as GET requests.
The automatic creation of Uptime Monitors only happens if there are no other existing uptime monitors configured.
To avoid creating flaky monitors, 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.
Sentry will execute uptime checks against the hostname root path of the most frequently-seen URLs. For example, if the most frequently-seen URL in your events is GET https://www.example.com/docs/introduction, the check will be GET https://www.example.com/.
Once an automatically detected Uptime Monitor has been created, you can customize its configuration—including the HTTP request method, headers, and request body—from the Monitors page.
If you prefer not to use automatically detected Uptime Monitors, you can delete them from the Monitors page.
Once deleted, these automatically detected Uptime Monitors will not be re-created in the future.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").