Heartbeats
Make silent scheduled work visible to your on-call process
MonoDuty Heartbeats provide a dedicated product concept for recurring processes that need operational attention.
No credit card required for the trial · EUR subscriptions through Stripe
01 / Overview
A recurring process needs a recurring proof of life
Scheduled work can fail without producing the same event pattern as an interactive service. A heartbeat gives that recurring work a named place in the monitoring and incident model.
MonoDuty lists Heartbeats alongside Webhooks and Monitors. Use each product for the signal shape it represents, then connect the resulting incident path to on-call coverage.
02 / Operating value
Build a heartbeat around operational meaning
The important design work is deciding what a missing signal means and who should respond.
Name the process and owner
Tie each recurring signal to a job, environment, and responsible team or person.
Define the expected rhythm
Base the operating rule on the schedule the process is actually expected to keep.
Connect failure to response
Align the heartbeat with on-call scheduling and the channels available on your chosen plan.
03 / Workflow
Design the signal before relying on the alert
A heartbeat should be simple to send and unambiguous to interpret.
- 01
Choose a recurring process
Start with work that has a clear expected schedule and a meaningful consequence when it does not complete.
- 02
Follow current setup guidance
Use MonoDuty documentation for the current Heartbeat configuration and request details.
- 03
Test the missing-signal path
Run a safe validation of the complete incident path, including the responsible schedule and plan channels.
04 / Plans
Heartbeat capacity by plan
The public plan matrix publishes a finite Heartbeat allowance for every tier.
Free
5 Heartbeats, one user, email delivery, and 7-day incident retention.
Pro
100 Heartbeats, up to 25 users, and email/SMS/voice allowances.
Business
500 Heartbeats, unlimited users, and email/SMS/voice allowances.
05 / Questions
Common questions
01What kind of work is a Heartbeat for?
It is a useful monitoring model for recurring work with an expected rhythm, such as a scheduled process.
02What are the published Heartbeat limits?
Free includes 5, Pro 100, and Business 500 Heartbeats.
03Can Heartbeats sit alongside Webhooks and Monitors?
Yes. MonoDuty names Heartbeats, Webhooks, and Monitors as separate product capabilities.
MonoDuty / Start
Bring recurring work into view
Start with one meaningful scheduled process, document its owner, and test the full missing-signal response path.