§ concepts — pulse
what's a pulse?
A pulse is a heartbeat monitor. Instead of us reaching out to your service, your service reaches out to niceuptime — a quick check-in every time a job runs. Miss the check-in, and the missing run is recorded in the monitor evidence.
pulse — you check in
For things that run on a schedule: cron jobs, backups, queue workers, ETL. Silence is the signal.
probe — we check you
For things that should always answer over HTTP or HTTPS: websites, APIs, and health endpoints.
how it works
Create a pulse and copy its unique check-in URL.
Call that URL at the end of your job — one line of curl.
No check-in arrives in time? The missed run is recorded.
# at the end of your nightly backup cron
0 2 * * * /usr/local/bin/backup.sh && \
curl -fsS https://heartbeat.niceuptime.com/a1f9-c3d2-7bready to add one?
Set it up from one small form. No agent to install.
§ concepts — probe
what's a probe?
A probe is an outbound HTTP/HTTPS monitor. We call your website, API, or health URL on a schedule, then check that the response status is the one you expected. Bad status, timeout, or latency drift? The run is recorded for review.
probe — we check you
For things that should always answer over HTTP or HTTPS: websites, APIs, and health endpoints.
pulse — you check in
For things that run only sometimes: cron jobs, backups, queue workers, and ETL.
how it works
Create a probe and add the URL or endpoint we should check.
Choose the expected HTTP status and timeout for the runner.
The response drifts or disappears? The failed run is recorded for review.
# what niceuptime probes on your behalf
GET https://api.acme.co/health
expect status 200 within 10sready to add one?
Point it at a URL, choose what good looks like, and let it watch.