PagerDuty

Incidents that close themselves.

Trigger a PagerDuty incident when a monitor goes down, and it resolves automatically when the service recovers. Of every destination Hesklo supports, this is the one that manages its own lifecycle rather than just sending a message.

Opens on the way down. A monitor going down triggers an incident on the PagerDuty Events API.
Resolves on the way back up. Recovery resolves the incident automatically, so nothing is left open for someone to close by hand.
Uses your existing rota. If your organisation already runs on-call through PagerDuty, this plugs Hesklo into that rather than replacing it.

Start free All features

01 · Why it is different

A record, not a message.

Most destinations send an alert and forget about it. PagerDuty incidents have a lifecycle that Hesklo participates in on both ends.

Automatic resolution

The incident closes when the monitor recovers. This is the only destination where that happens without you drawing anything from the up port.

No stale incidents

Because resolution is automatic, your PagerDuty view does not slowly fill with incidents for services that came back hours ago.

Their rota, not ours

If PagerDuty already holds your on-call schedule, escalation policies and overrides, this uses all of it.

Hesklo does the detection

You get Hesklo checks and flow logic on the detection side, and PagerDuty on the response side.

02 · Using it well

What to send, and what not to.

Behind a Wait

Give brief outages a chance to resolve before raising a formal incident. A PagerDuty incident is a heavier artifact than a chat message.

Critical services only

Because flows belong to individual monitors, you can raise incidents for the services that warrant one and use a channel for everything else.

Do the filtering first

Use the monitor confirm down after setting and a Wait so PagerDuty only ever sees genuine outages.

Alongside a channel post

A flow can post to Slack and raise a PagerDuty incident from the same down port, so the team sees it and the on-call process starts.

Questions

Common questions

Do PagerDuty incidents resolve automatically?

Yes. An incident triggered by a Hesklo flow is resolved automatically when the monitor recovers, so you do not have to close it by hand or draw anything from the monitor up port.

How do I connect PagerDuty to Hesklo?

Get the Events API routing key for the PagerDuty service you want incidents raised against, then add a PagerDuty connection in the monitor editor sidebar and paste it in. Send test confirms an incident appears.

Should I use PagerDuty or the Hesklo on-call schedule?

If your organisation already runs on-call through PagerDuty with its escalation policies and overrides, keep using it and let Hesklo raise the incidents. The built-in Hesklo rota exists for teams who do not have a separate paging tool and would rather not add one.

Can one monitor both raise an incident and post to a channel?

Yes. A flow can branch to as many notify steps as you like from the same down port, so the team sees the alert in chat while the PagerDuty incident starts the formal response.