Uptime Monitoring
Learn how to help maintain uptime for your web services by monitoring relevant URLs with Sentry's Uptime Monitoring.
Sentry Uptime Monitoring is currently in open beta, so be gentle - features are still in-progress and may have bugs. We recognize the irony. For any questions or feedback, you can reach us on Github Discussions.
Sentry's Uptime Monitoring lets you monitor the availability and reliability of your web services effortlessly. Once enabled, it continuously tracks configured URLs, delivering instant alerts and insights to quickly identify downtime and troubleshoot issues.
By leveraging distributed tracing, Sentry enables you to pinpoint any errors that occur during an uptime check, simplifying triage and accelerating root cause analysis. This helps you enhance both the reliability and uptime of your web services.
Uptime is automatically configured as a new alert for the most frequently encountered hostname in all URLs of your error data, ensuring continuous monitoring of your most critical hostname right out of the box.
You can also create uptime monitoring alerts for specific URLs. They're fully customizable with request details such as the HTTP method, headers, and body.
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:
- Successful Response (2xx Status Codes): The URL must return an HTTP status code in the 200–299 range, indicating a successful request.
- 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.
- Timeout Setting: Each request has a timeout threshold of 10 seconds. If the server doesn't respond within this period, the check will be marked as a failure, indicating a potential downtime or performance issues.
- DNS Issue Detection: Our monitoring also includes the detection of DNS resolution issues. If a DNS issue is detected, the check will be marked as a failure, allowing you to address the underlying connectivity problems.
An uptime alert continuously monitors the configured URL with the criteria defined above. If a failure is detected, a new uptime issue with the failed check and related error details will be created. To avoid triggering false alerts due to transient issues like network glitches, new issues will only be created after a minimum of three consecutive failures have been detected, following the initial downtime detection.
To start getting notifications for a new downtime issue, configure an issue alert and choose the issue category "uptime". Then choose how you'd like to be notified (via email, Slack, and so on).
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").