How to Connect Monitorion to PagerDuty, Webhooks, and Your Incident Workflow

Getting an alert is only useful if it reaches the right person at the right time through the right channel. Monitorion supports 9 alert channels out of the box, but the real power comes from integrating them into your existing incident workflow.

PagerDuty Integration

PagerDuty handles on-call scheduling, escalation policies, and incident tracking. Connecting Monitorion to PagerDuty means your monitoring alerts automatically create PagerDuty incidents that follow your team's escalation rules.

1. In PagerDuty, go to Services > Service Directory > + New Service
2. Name it "Monitorion" and select your escalation policy
3. Under Integrations, choose Events API v2 and copy the Integration Key
4. In Monitorion, go to Settings > Notifications and paste the key under PagerDuty
5. Click Test to verify the connection

When a monitor goes down, Monitorion sends an event to PagerDuty's Events API v2. PagerDuty creates an incident, pages the on-call engineer, and escalates if nobody responds. When the monitor recovers, Monitorion sends a resolve event that automatically closes the PagerDuty incident.

Custom Webhooks

Webhooks let you connect Monitorion to any system that accepts HTTP POST requests. Use cases:

• Custom dashboards — send incident data to your internal monitoring dashboard
• Ticketing systems — auto-create Jira or Linear tickets on incidents
• ChatOps — post to a custom Slack bot or Microsoft Teams workflow
• Automation — trigger auto-scaling, failover, or restart scripts

The webhook payload includes the monitor name, type, target URL, status, error message, response time, region, and incident ID — everything you need to take action programmatically.

Per-Monitor Alert Channels

Not every monitor needs every alert channel. Monitorion lets you choose which channels each monitor uses:

• Production API — Email + Slack + PagerDuty + SMS (all hands on deck)
• Staging environment — Slack only (informational, no paging)
• SSL certificate — Email only (non-urgent, 30-day warning)
• Internal service — Webhook to auto-restart script (no human needed)

Configure this in the monitor's Advanced Settings under "Alert Channels" — choose "Custom selection" and pick the channels that make sense for that specific service.

Start monitoring free — connect your first alert channel in under a minute.