Monitors · Uptime monitoring
Connect uptime signals to the people responsible for response
MonoDuty Monitors run HTTP or HTTPS availability checks from the current Helsinki worker and connect failures to the incident workflow.
No credit card required for the trial · EUR subscriptions through Stripe
01 / Overview
Uptime data becomes useful when ownership is clear
An availability result answers whether a target appeared reachable from Helsinki for that execution. It is not a global observation or a contractual uptime guarantee. The incident workflow separately determines who should investigate and which configured channel is queued.
HTTPS checks validate the peer certificate and hostname during the connection. MonoDuty does not currently inventory certificate details, track expiry dates, or send certificate-expiry warnings.
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 or the release-gated phone 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
Monitor capacity and interval by plan
Every Monitor currently uses the Helsinki execution location; tiers differ in capacity and minimum interval.
Free
5 Monitors with a minimum 300-second interval.
Pro
50 Monitors with a minimum 60-second interval.
Business
250 Monitors with a minimum 30-second interval.
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.
02Where do Monitor checks run?
The current production worker runs in Helsinki. The region name is a real execution location, not a simulated global probe.
03Does MonoDuty warn before a TLS certificate expires?
No. HTTPS checks validate the certificate and hostname during connection, but certificate metadata and expiry warnings are not currently provided.
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.