Sign In

Creating Monitors

Define and configure active checks for your systems, services, or endpoints.

Monitors are core to ensuring visibility across your infrastructure and services. In Upstat, monitors can be created directly through the Monitoring section and tailored to fit your observability needs.

Creating a New Monitor

To create a monitor:

  1. Navigate to Monitoring from the main sidebar.
  2. Click New Monitor.
  3. Select the Monitor Type:
    • HTTP/HTTPS
    • SSL Certificate
    • Heartbeat
  4. Fill in the required fields:
    • Name
    • Target (e.g., URL or service identifier)
    • Check Interval (default is 30 seconds)
    • Threshold Settings

![Placeholder: Monitor Creation Form]

Monitor Configuration Fields

Each monitor includes:

  • Name: A human-readable label for identification.
  • Type: Chosen at creation; determines check behavior.
  • Interval: How often to run checks.
  • Regions: If multi-region is enabled, checks will run from selected geographies.
  • Failure Thresholds: Number of failed checks before a monitor is considered “down.”
  • Response Expectations (for HTTP monitors):
    • Expected status codes (e.g., 200–299)
    • Optional keyword verification in response body
  • Headers: Custom headers such as API keys (if enabled for your plan)
  • Authentication: Basic auth or token headers

![Placeholder: Advanced Monitor Settings Screenshot]

Multi-Region Support

You can optionally select multiple regions for distributed monitoring. Each region will independently evaluate the health of the target.

Monitors track:

  • Which regions failed
  • Percentage of total failure
  • Whether the failure constitutes a partial or full outage

Post-Creation Behavior

After creation, your monitor will begin checking immediately based on the selected interval. You’ll see:

  • A live feed of recent check results
  • A status badge (Healthy, Partial, Down)
  • Event logs when status changes occur

Automations & Notifications

You can attach Automations to monitor status transitions to:

  • Trigger alerts
  • Create incidents
  • Update Status Pages

Monitor-triggered Automations are configured under the Monitor Automations section.

Best Practices

  • Use descriptive names (e.g., “API – Auth Service”)
  • Enable multi-region checks for critical services
  • Set realistic thresholds to avoid alert fatigue
  • Use Heartbeat monitors for background tasks and workers

Learn more