PagerDuty alerts for
SSL, DNS & uptime monitoring
Trigger and auto-resolve PagerDuty incidents from monitoring.
How it works
How Merlonix delivers to PagerDuty
Merlonix sends alerts to PagerDuty through the Events API v2 using an integration routing key. Each alert triggers a PagerDuty incident carrying a dedup key, so when Merlonix sees the underlying issue recover it resolves the same incident automatically — the alert routes straight into your existing PagerDuty services and escalation policies.
Alerts route through the Events API v2 into your existing PagerDuty service — no change to how your team is paged.
A dedup key ties the trigger and the recovery together, so a resolved check auto-resolves the PagerDuty incident instead of leaving it open.
If you already run on-call in PagerDuty, monitoring becomes one more source feeding the same escalation.
Setup
Set up PagerDuty in three steps
Step 1
In PagerDuty, add an Events API v2 integration to the service you want and copy its routing key.
Step 2
In Merlonix (Team plan or above), add a PagerDuty notification channel with the routing key.
Step 3
Send the one-click test to confirm an incident triggers, then attach the channel to your assets.
What fires an alert
The delivery channel changes; the monitoring doesn’t
Every alert carries the same context regardless of destination: which client asset changed, which check fired (SSL-certificate expiry or change, DNS-record drift, domain registration/expiry, uptime, DNSSEC, security headers, blocklist status, and more), and what specifically changed. Alerts fire on real state changes between definitive checks — not on a transient blip.
- SSL / TLS monitoring
- DNS & DNSSEC monitoring
- Domain-hijack & registrar-lock monitoring
- Security-header monitoring
PagerDuty is one of ten delivery destinations, and Merlonix also runs on-call rotations and escalation policies so the right person is paged. See alerting & on-call →
Other destinations
Prefer a different channel?
Merlonix delivers the same alerts to every destination your team already uses.
Common questions
Frequently asked questions
Which Merlonix plan includes PagerDuty alerts?
PagerDuty alert delivery is available on Team and above (the on-call band). You can start on the free plan and add PagerDuty when you are on the qualifying tier.
What do PagerDuty alerts actually contain?
Every alert carries the same context regardless of destination: which client asset changed, which check fired (SSL-certificate expiry or change, DNS-record drift, domain registration/expiry, uptime, DNSSEC, security headers, blocklist status, and more), and what specifically changed. Alerts fire on real state changes between definitive checks — not on a transient blip. The PagerDuty message carries that same context, so a responder can triage from the alert itself.
Can I use PagerDuty alongside other channels?
Yes. A single asset can send to PagerDuty and other destinations at once — for example email plus a chat channel plus an on-call channel — so no alert rides on one delivery path. Merlonix supports email, Slack, Microsoft Teams, Discord, Telegram, Google Chat, a generic webhook, SMS, PagerDuty, and Opsgenie.
Do I need access to my clients’ servers to monitor them?
No. Merlonix probes each domain from the outside in — its public SSL certificate, DNS records, registration data, and HTTP responses — the same way a browser or resolver would. You add an asset by hostname; the PagerDuty channel just decides where the resulting alert is delivered.
Wire monitoring into PagerDuty today
SSL, DNS, uptime, and vendor-aware alerts across every client asset — delivered where your team already works. Start free, no credit card.