BACKGROUND JOB MONITORING
Detect background jobs that stop running
Background work often has no public URL to check. Upnora uses a heartbeat sent by your application after successful work to detect when a job, worker or task becomes silent.
WHAT CAN GO QUIET
Detect the work that has no customer-facing page.
HOW IT WORKS
Your application sends the proof of completion.
Upnora does not inspect your queues directly and does not execute background jobs. Your application sends a small HTTP request when the expected work has completed. If that heartbeat does not arrive within the configured interval and grace period, the monitor becomes overdue.
This pattern works whether a job runs every hour, every night or whenever a worker receives a task. It helps detect a queue that stops consuming messages, an import that exits early, or a worker that crashes before reporting.
Send the heartbeat after the successful part of the job. A process that fails before reporting should remain silent so Upnora can detect the missing signal and alert your team.
CONTINUE WITH YOUR STACK
Add a heartbeat where the job runs.
Use the integration that matches your application or scheduler.
Explore heartbeat integrations →FAQ
Background job monitoring, simply explained.
What can background job monitoring detect?
It can detect a missing heartbeat from jobs such as imports, exports, workers, reports, backups and billing tasks.
Does Upnora inspect my queue directly?
No. Your application sends a heartbeat after successful work; Upnora monitors that external signal.
When should a background job send its heartbeat?
After the useful work completes successfully, not before it starts.
MONITOR SILENT WORK