Promptwatch Logo

Sentry Uptime Monitoring Bot

Sentry's Uptime Monitoring Bot performs health checks on configured URLs to monitor the availability and reliability of web services.
Sentry
Monitoring

What is Sentry Uptime Monitoring Bot?

Sentry Uptime Monitoring sends an HTTP request to each URL configured in an uptime monitor. The request repeats at the monitor's interval, and Sentry evaluates the result to decide whether the service is available. A failed run can create a downtime issue for the alert rules attached to that monitor.

The traffic stays focused on the configured endpoint rather than following links through the site. Monitor owners can add request headers when a check needs a particular credential or routing value. This makes a dedicated health route a better target than a page with unrelated browser behavior.

Sentry publishes the full identity as SentryUptimeBot/1.0 (+https://docs.sentry.io/product/monitors-and-alerts/monitors/uptime-monitoring/). It also sends a Sentry-Trace header so the check can be connected to downstream spans and errors. Current monitoring addresses are available from Sentry, although the operator warns that they may change.

This bot belongs to Sentry's reliability product. It has no documented job in search indexing, AI answer retrieval, or model training. The recurring requests should be removed from visitor counts without being reclassified as AI crawler activity.

Not relevant for AI search

Is Sentry Uptime Monitoring Bot relevant for AI search?

No. Sentry Uptime Monitoring Bot is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

Sentry Uptime Monitoring Bot runs synthetic monitoring or uptime checks on a schedule. It is not collecting content for any index or model, so it has no bearing on search rankings or AI answers. You usually see it because your own team or a service you use set up a check.

How to handle Sentry Uptime Monitoring Bot

Keep the monitored route reachable when your team uses Sentry Uptime Monitoring. A firewall rejection creates a failed check even if the application remains healthy for ordinary users. When an exception is needed, scope it to the health endpoint and use both current source information and the published identity. Do not authorize access to sensitive data from the header alone.

The stable product name can be addressed as a crawler preference:

User-agent: SentryUptimeBot
Disallow: /

Sentry does not document robots.txt handling for uptime requests, so this rule is not an enforceable block. Edit or remove the monitor in Sentry when you control it. If the checks only need to be excluded from Sentry errors or performance sampling, use the documented SDK filter for SentryUptimeBot and leave the uptime request working.

Examples

  • A request to `/health` carries `SentryUptimeBot/1.0` and `Sentry-Trace`. The trace connects the slow check to work performed inside the application.
  • A WAF starts rejecting Sentry's monitoring traffic. The team limits an exception to the health route instead of allowing the bot across the whole site.

Frequently asked questions about Sentry Uptime Monitoring Bot

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

The published user agent begins with `SentryUptimeBot/1.0` and includes a link to Sentry's uptime documentation.

Be the brand AI recommends

Monitor your brand's visibility across ChatGPT, Claude, Perplexity, and Gemini. Get actionable insights and create content that gets cited by AI search engines.

Promptwatch Dashboard