Skip to content
Glowo
Esc
↑↓navigate↵open⌘Jpreview
On this page

Uptime reports and history

Heartbeats, hourly statistics, and downloadable SLA reports in JSON or CSV.

Every check Glowo runs is kept as a heartbeat: its result, latency, region, and — on failure — the error code and message.

Heartbeats

Glowo monitor detail page showing 100% availability, P50 and P95 response times, a check-results bar chart and a response-time chart

A monitor’s detail page: availability, percentiles, the check-result timeline and per-region run results.

The monitor page shows the recent heartbeat timeline. Opening a single heartbeat gives the full detail, including the timing breakdown and the response metadata captured at the time.

GET /monitors/<monitor-id>/heartbeats
GET /monitors/<monitor-id>/heartbeats/<heartbeat-id>

For multi-region monitors each region records its own heartbeat, which is how you tell “the service is down” from “one region cannot reach it”.

Hourly statistics

GET /monitors/<monitor-id>/hourly-stats

Heartbeats rolled up per hour. This is what the dashboard’s longer-range charts draw from — use it when you want a trend rather than individual checks.

SLA reports

GET /monitors/<monitor-id>/report
GET /monitors/<monitor-id>/report?format=csv

Returns uptime percentage, incident count, average latency, paused time, maintenance time left out of uptime and per-day statistics. format=csv returns the same data as a download, for attaching to a customer SLA review or pasting into a spreadsheet.

The incident count counts outages, not failed checks. An outage starts when a region’s checks turn DOWN and lasts until that region’s next check that is not DOWN. Outages that overlap, or follow one another with no gap — in one region or across several — count as a single incident, so one region failing for an hour is one incident, not sixty. An outage still open at the end of the range ends at its last failing check in the range.

Paused time is reported separately and excluded from uptime, so pausing a monitor for planned work does not quietly inflate your numbers — the gap stays visible and honest.

Maintenance excluded from uptime is reported separately too. totalExcludedMs is how long maintenance windows excluded from uptime covered the period, and each day’s excludedChecks counts the checks made during them: left out of that day’s check counts and of uptime, still counted in its latency.

Retention

How long heartbeats are kept depends on your plan:

PlanRetention
Free30 days
Pro90 days
Business365 days

Hourly statistics let you see trends across a longer window than raw heartbeats would practically allow. If you need history beyond your plan’s retention, export the report periodically.

Clearing history

DELETE /monitors/<monitor-id>/heartbeats

Deletes every heartbeat for a monitor and resets its statistics.

Was this page helpful?