Skip to main content

​
What ships together

Squasher status monitoring ties four workflows into one product surface:
  • Monitors for HTTP uptime checks and query-backed health checks
  • Incidents that open automatically when monitor thresholds are breached
  • Status pages that roll up component health for customers
  • AI guidance that helps responders investigate faster

​
Create monitors

Go to Dashboard > Monitors to register a monitor.

​
HTTP monitors

Use HTTP monitors for health endpoints and synthetic uptime checks. Common settings:
  • Request URL
  • Expected status codes
  • Response body assertions
  • Check interval
  • Failure and recovery thresholds
  • Optional runbook URL

​
Query monitors

Use query monitors when health is better represented by metrics or event volume than a single endpoint. You can monitor:
  • Event counts
  • Log counts
  • Ingestion latency
  • Web vital measurements
Each query monitor lets you define:
  • Data source
  • Query or filter
  • Aggregate to evaluate
  • Comparison operator
  • Threshold
  • Evaluation window

​
Test a monitor immediately

Use Run now from the monitor list when you want to validate a new monitor without waiting for the next scheduled check. This records a real monitor check, updates the current monitor state, and can open or resolve incidents using the same automation rules as scheduled runs. Go to Dashboard > Status Pages to create a page and add components such as Checkout API or Background Jobs. When a monitor uses the same component name, Squasher rolls monitor state into that public component automatically.

​
Incident automation

When a monitor breaches its configured failure threshold, Squasher opens or reuses an active incident for that affected scope. When checks recover and meet the recovery threshold, the incident can resolve automatically. This keeps monitor history, incident response, and customer-facing communication aligned.

​
Publish a status page

Each status page gets a public route you can share with customers. Public pages show:
  • Current component health
  • Active incidents
  • Recent incident history
  • Optional support link and page headline

​
Suggested setup order

  1. Create a status page and its public components.
  2. Register monitors and link them to matching component names.
  3. Verify incident creation by running monitors manually.
  4. Share the public page after the component rollups look correct.