Skip to main content

​
Overview

Availability monitoring continuously checks that your connected platforms — n8n instances, Make.com accounts and OpenClaw gateways — are reachable and responding. Each check produces an availability sample; from those, Opsmatic computes uptime, response-time trends and opens incidents when a platform goes down.

​
How Checks Work

1

Scheduled checks

Opsmatic probes each connection on an interval. The frequency is tier-based and configurable per connection — higher plans check more often.
2

Sample recorded

Every check stores whether the platform was available and how long it took to respond.
3

Incident on failure

A run of failed checks opens an availability incident; two consecutive successful checks auto-resolve it.
4

Rolled up

Samples are aggregated into daily/weekly/monthly uptime for fast historical views.

​
Querying Availability

​
Raw samples

Set include_synthetic=false to exclude synthetic gap-fill samples.

​
Uptime summary

window accepts day, week or month. See the Analytics API for the full parameter list.

​
Uptime aggregations

For charts, use the pre-computed metrics daily_availability, weekly_availability, monthly_availability:

​
Incidents

Availability is one of several incident kinds (alongside missed heartbeats, anomalies and budget breaches). Incidents follow an open → acknowledged → resolved lifecycle with an append-only event timeline, and drive failure/recovery emails.

​
Data Retention

Raw availability samples are kept for a tier-based window, after which the pre-computed uptime aggregations preserve the long-term picture: Daily and monthly rollups are retained well beyond the raw window, so historical uptime charts survive the purge.

Health Monitoring

The live status view on your dashboard

Connection Problems

Diagnose a connection that’s showing as down