Know when your services go down.

Check websites, APIs, databases and background jobs on the interval you choose, and alert your on-call team when a check fails. Moneat keeps the request that failed, so the alert arrives with the evidence.

ChecksHTTP, TCP, ping, DNS, SSL, more
IntervalSet per monitor
On failureThe request is kept, not summarised
api.acme.io · every 30s99.98% · 30d
Uptime99.98%30 days
Avg response412 ms
Checks today2 889
Incidents117 min
Response timems · last 24h
Frankfurt214 ms
Virginia388 ms
Singapore512 ms
São Paulo461 ms
Sydney597 ms
Latest checkFrankfurt
status200 OK
dns12 ms
connect41 ms
ttfb288 ms
tlsvalid · 71 days
Assertions
  1. status is 200
  2. body contains "ok"
  3. response under 800 ms
  4. certificate valid 14+ days
Alerting
3 consecutive failures → notify payments-primary

Detect a failing endpoint and raise an alert

A check that fails is confirmed by retries before it raises anything, and the group it raises closes itself on recovery. Here is one outage, from the first slow probe to the all-clear.

INC-402 · Checkout latency above SLO
Resolved
14:02:11 → 14:19:44 · 17m 33s
14:01:58
Checkout probe slows
Response time crosses the monitor’s threshold, thirteen seconds before the first error alert.
Uptime checks
14:02:11
Third consecutive failure, alert raised
The monitor retries before it is marked down, so a single failed request raises nothing.
Alert routes
14:19:44
Recovered, alert group closed
Five clean minutes of checks before the route auto-resolved the group.
Alert routes

Set up checks for what you run

A check type for each kind of service, with the settings that keep a monitor useful rather than noisy.

Check types

HTTP, TCP, ping, DNS, WebSocket, SSL, database and Docker container checks.

types
Confirmation retries

Re-check a failing endpoint on a retry interval you set before the monitor is marked down.

retries
The failing request, kept

Status, response headers, a body excerpt and phase timings: DNS, connect, TLS and first byte.

evidence
TLS expiry warnings

Warn a set number of days before a certificate expires, so renewal happens ahead of an outage.

tls
Keyword and JSON assertions

Check the response body for a keyword or a JSON value, not only the status code.

assertions
Background job checks

Give a cron job or worker a URL to call when it finishes, and keep its run history on the monitor.

heartbeat
Maintenance windows

Suppress notifications during planned work, while the checks keep recording. The window expires on its own.

windows

See the request that failed.

Moneat keeps the failing attempt rather than a summary of it, so you can read what the endpoint returned instead of reproducing the failure.

  • Phase timings. DNS, connect, TLS handshake and first byte, so a slow check names its own stage.
  • Response captured. Status line, headers and a body excerpt from the attempt that failed.
  • Check history. Every result the monitor has recorded, so you can see when the behaviour changed.
  • Linked to the trace. When the endpoint is instrumented, the check links to the request it made.
POST /api/checkout14:02:11
Status
503 Service Unavailable
DNS
11 ms
Connect
24 ms
TLS
38 ms
First byte
9 841 ms
Body
{"error":"pool timeout"}
Trace
a41f…9c2 · 12 spans

Start checking your endpoints.

Add a monitor, set its interval and retries, and point it at an alert route. Start on the free plan with no card.