SQL check (default)
Runs a SQL query against a connection and evaluates the result against a condition. Single-value or grid. This is the default when no type is given.Website / API check (http)
Requests a URL on your interval and alerts if it stops behaving. No database
connection needed. Configure:
API metric check (api_metric)
Fetches a JSON API on your interval, extracts a number from the response,
and evaluates it against a condition — exactly like a SQL
single-value check, including the value graph on the check’s overview. Use it
to track SaaS usage, spend, queue depths, or any metric a provider exposes over
HTTP. See API metric checks for the full guide.
Heartbeat check (heartbeat)
A dead-man’s-switch for a cron job, ETL pipeline, or any scheduled task.
Instead of Alertee reaching out, your job calls a private ping URL when it
finishes successfully. If a ping doesn’t arrive in time, the check alerts.
Configure:
When you create the check, Alertee returns a ping URL like
https://api.alertee.app/heartbeat/<token>. Call it on success — for example at
the end of a cron job:
GET or POST both count as a ping. POST a JSON body
({"status":"failure","message":"…"}) to report a failed run explicitly.
Push check (push)
The one type where you send us the number. Your own cron, script, or CI step
POSTs a value to a private ingest URL; the value is evaluated against a
condition — single-value or grid — the instant it arrives.
No database credentials, and it works from inside a private network. A staleness
window doubles as a dead-man switch, so silence alerts too.
{"rows": [{"name": "eu-west", "value": 12}]} instead to push a grid — one
row per dimension. See Push checks for the full guide.
Creating each type
All five are available from the app, the CLI, and the MCP server (create_check with check_type = sql, http,
api_metric, heartbeat, or push).