> ## Documentation Index
> Fetch the complete documentation index at: https://docs.opsmatic.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Availability Monitoring

> Track platform uptime, response time and connection health

## 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

<Steps>
  <Step title="Scheduled checks">
    Opsmatic probes each connection on an interval. The frequency is **tier-based and configurable per connection** — higher plans check more often.
  </Step>

  <Step title="Sample recorded">
    Every check stores whether the platform was available and how long it took to respond.
  </Step>

  <Step title="Incident on failure">
    A run of failed checks opens an **availability incident**; two consecutive successful checks auto-resolve it.
  </Step>

  <Step title="Rolled up">
    Samples are aggregated into daily/weekly/monthly uptime for fast historical views.
  </Step>
</Steps>

## Querying Availability

### Raw samples

```
GET /v1/availability
```

```bash theme={null}
# Only the failed checks for one connection
curl -H "Authorization: Bearer ops_your_api_key" \
  "https://api.opsmatic.com/v1/availability?connection_id=conn_abc123&is_available=false"
```

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

### Uptime summary

```
GET /v1/availability/summary
```

```bash theme={null}
curl -H "Authorization: Bearer ops_your_api_key" \
  "https://api.opsmatic.com/v1/availability/summary?window=week&connection_id=conn_abc123"
```

`window` accepts `day`, `week` or `month`. See the [Analytics API](/api-reference/analytics#availability) for the full parameter list.

### Uptime aggregations

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

```bash theme={null}
curl -H "Authorization: Bearer ops_your_api_key" \
  "https://api.opsmatic.com/v1/analytics?metric_type=daily_availability&connection_id=conn_abc123"
```

## 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.

```bash theme={null}
curl -H "Authorization: Bearer ops_your_api_key" \
  "https://api.opsmatic.com/v1/incidents?connection_id=conn_abc123"
```

## Data Retention

Raw availability samples are kept for a **tier-based** window, after which the pre-computed uptime aggregations preserve the long-term picture:

| Plan  | Raw data retention |
| ----- | ------------------ |
| Free  | 7 days             |
| Pro   | 30 days            |
| Scale | 90 days            |

Daily and monthly rollups are retained well beyond the raw window, so historical uptime charts survive the purge.

## Related

<CardGroup cols={2}>
  <Card title="Health Monitoring" icon="heart-pulse" href="/dashboard/health-monitoring">
    The live status view on your dashboard
  </Card>

  <Card title="Connection Problems" icon="triangle-exclamation" href="/troubleshooting/connection-problems">
    Diagnose a connection that's showing as down
  </Card>
</CardGroup>