A check-in from the job
Call the monitor’s private ping address from your script. GET, POST and HEAD are supported, making the signal easy to add to an existing task.
The job should run.
Know when it doesn’t.
Watch backups, scheduled scripts and background jobs without giving them a public URL. Let each successful run check in, and get a signal when the expected heartbeat is missing.
Part of your Uptiva workspace · One workspace. Every signal.
SUCCESSFUL CHECK-INS
Last run received. Next window is being watched.
- Job
- nightly-backup
- Expected every
- 24 hours
- Last heartbeat
- 12 minutes ago
- Grace period
- 15 minutes
A scheduled task can fail quietly. There may be no page to request and no user to report an error. Heartbeat monitoring reverses the usual check: your job calls Uptiva, and the monitor watches for the next expected signal.
Choose an expected period and a grace period that covers normal run time and scheduling variation. Send the heartbeat after successful completion so a started but unfinished job does not look like a completed one.
Keep this signal alongside the rest of your stack: organize related services, choose who receives alerts and follow recovery in the same workspace. The goal is a check that explains what changed and gives the right person a useful place to start.
SMALL DETAILS. USEFUL CONTEXT.More than
More than
an up or down.
Purpose-built checks.
Information you can act on.
An expected schedule
Set how often a successful run should arrive. The monitor watches the allowed time between pings rather than sending requests to your infrastructure.
Room for normal variation
Add a grace period for slow but acceptable runs. Your expected period plus grace determines when a missing heartbeat becomes overdue.
Explicit failure reporting
Use the failure address when a task knows it failed. You do not have to wait for the missing-ping window to finish before reporting an error.
Last and next signal
The monitor page shows the last ping and when the next one is due. Overdue information makes a missing run easier to understand than a generic status alone.
Recovery when pings resume
When successful heartbeats return, the monitor can recover and notify the team. Keep the alert destinations alongside your other monitoring signals.
WHERE IT FITSMade for the work
Made for the work
you already do.
One reliable signal.
Plenty of practical uses.
Scheduled backups
Send a heartbeat after the backup command succeeds. This verifies the completion signal, while separate restore testing remains important for validating the backup itself.
Import and export jobs
Watch routine data transfers or reports that run on a schedule. A missing check-in can reveal a stalled process that has no public endpoint to monitor.
Background maintenance
Add a completion ping to cleanup jobs, scheduled scripts and other repeatable work. Choose a grace period based on their realistic run time.
FROM SETUP TO A USEFUL SIGNALStart with what
Start with what
matters most.
Use a meaningful name, choose the behavior you expect and make sure the alert reaches someone who can act. Start with one service, then add the related checks as your monitoring grows.
Open the setup guide- 01
Choose your starting point.
Create a Heartbeat monitor and set the expected period plus a grace period appropriate to the job.
- 02
Configure the check.
Copy its private ping address from the monitor page. Add the request after the task completes successfully.
- 03
Follow the signal.
Choose alerts, verify a successful ping and check the next due time. Optionally report failures through the dedicated failure address.
A LITTLE MORE CONTEXTGood questions.
Good questions.
Clear answers.
The details that help you choose the right check and get a useful result.
Read the full documentationDo I need to expose a public endpoint?+
No. The job sends an outbound request to Uptiva. There is no inbound URL for the monitor to request on your machine.
When should the job send its heartbeat?+
Usually after successful completion. Pinging at startup can make a job that later hangs appear healthy until the next expected window.
Can I report an immediate failure?+
Yes. The ping address has a /fail endpoint for explicit failure reports. Keep both addresses private because anyone with the secret address can send a signal.
How quickly is a missed run detected?+
The allowed window is the expected period plus grace. Detection takes up to about thirty seconds after that window ends; heartbeat checks do not use the regular consecutive failure setting.
Why is there no response-time chart?+
A heartbeat measures whether signals arrive on time rather than the response latency of a remote endpoint. The useful details are the last ping, next due time and failure state.
LESS CHECKING. MORE KNOWING.One more thing
Get started One more thing
off your mind.
Bring heartbeat monitoring into your workspace.