Monitors · Uptime monitoring
Connect uptime signals to the people responsible for response
MonoDuty Monitors give availability checks a direct place in the same incident alerting and on-call model.
No credit card required
01 / Overview
Uptime data becomes useful when ownership is clear
An availability signal answers whether a target appears reachable. An incident workflow answers who should investigate and how that person should be alerted. Treating these as connected but distinct concerns keeps the operating model understandable.
MonoDuty identifies Monitors as a product capability and publishes on-call scheduling on every plan. Pro and Business add escalation policies and a wider delivery-channel set.
02 / Operating value
Design monitoring around response decisions
The check is only one part of the system; ownership and delivery complete the path.
Give each monitored target context
Record the service, environment, and responsible owner so an availability incident is actionable.
Route according to coverage
Connect the incident path to on-call scheduling, which is included on Free, Pro, and Business.
Scale the response layer
Use Pro or Business when the workflow requires escalation policies, phone alerts, or supported team-chat channels.
03 / Workflow
Test availability and response as one path
A monitor should be validated against the operational result your team expects.
- 01
Choose a meaningful target
Start with a service whose availability has a clear owner and response expectation.
- 02
Configure from current docs
Use MonoDuty documentation for supported Monitor settings and current setup steps.
- 03
Verify incident delivery
Run a safe test and confirm the intended on-call coverage and plan channels receive the incident path.
04 / Plans
Select the response tier separately from Monitor configuration
The canonical plan data does not publish a Monitor allowance, so use current documentation for product-specific limits.
Free response layer
One user, email and push, 50 incidents/month, and 7-day retention.
Pro response layer
Up to 25 users, escalation policies, seven channels, and 30-day retention.
Business response layer
Unlimited users and incidents, escalation policies, status pages, advanced analytics, and 90-day retention.
05 / Questions
Common questions
01Does every plan include on-call scheduling for incident response?
Yes. On-call scheduling is included in the published definition of all three plans.
02Are Monitor limits shown in the public plan matrix?
The canonical plan data does not specify a Monitor allowance. Check current documentation and pricing before rollout.
03Which tiers include escalation policies?
Pro and Business include escalation policies; Free does not list them.
MonoDuty / Start
Close the gap between detection and ownership
Start with one important target and validate the complete path from availability signal to responsible person.