Failure signal
A data processing script raises an exception.
PYTHON INTEGRATION
Monitor Python jobs and scheduled scripts
A Python script can stop because of an exception, a missing dependency or a scheduler problem. Use a heartbeat after successful execution to turn that silent failure into an actionable alert.
Job runs↓
Heartbeat sent↓
Upnora receives it✓
GET /h/YOUR_KEY/YOUR_TOKENWHAT CAN FAIL
Why this job can stop silently.
Failure signal
A scheduled Python script is no longer launched.
Failure signal
An export or synchronization task stops before producing its result.
BASIC INTEGRATION
Send the heartbeat after successful work.
Use the unique GET URL provided by your Upnora dashboard. The examples are generic: replace them with your monitor URL and keep it in an environment variable or secret.
import os, requests; requests.get(os.environ["UPNORA_HEARTBEAT_URL"], timeout=10)IMPLEMENTATION NOTES
Keep the signal meaningful.
Use the environment to provide UPNORA_HEARTBEAT_URL and send the request after run_job() returns successfully. If it raises an exception, the heartbeat is skipped.
See scheduled task monitoring →Common mistake
Do not catch every exception and send the heartbeat anyway. A successful heartbeat should mean the useful work completed.
Wrong: heartbeat → run the job
Better: run the job → heartbeat
MORE HEARTBEAT INTEGRATIONS
Use Upnora with your stack.
FAQ
Python heartbeat monitoring, simply explained.
How do I monitor a Python scheduled task?
Call the Upnora heartbeat URL after the Python task completes successfully.
Do I need a special Upnora package?
No. A normal HTTP client such as requests is enough.
What if run_job() raises an exception?
The heartbeat is not sent and the monitor can become overdue.
ADD A SUCCESS SIGNAL