PagerDuty integration
Open a PagerDuty incident when a FlatLyne check goes down, and resolve it when the check recovers.
FlatLyne watches your scheduled jobs and tells you when one stops running. The PagerDuty integration opens an incident on a PagerDuty service when a check goes down, and resolves the incident when the check recovers.
Benefits
- Missed cron jobs, failed backups and stalled workers page your on-call team through the escalation policy you already have.
- Incidents close on their own when the job runs again, so nobody resolves them by hand.
- You can send a project's alerts to more than one PagerDuty service.
Requirements
- A FlatLyne account. Sign in at flatlyne.com with Google.
- A PagerDuty account where you can add an integration to the service that should receive the incidents.
- A FlatLyne role that can edit the project: owner or member. Read-only members can't connect PagerDuty.
- The Free plan allows 2 integrations across the projects you own. Pro has no limit.
How it works
| FlatLyne event | What FlatLyne sends to PagerDuty |
|---|---|
A check goes down: a ping is later than its schedule plus grace time, or the job sends a /fail ping | A trigger event that opens an incident |
| A down check recovers: it receives a success ping | A resolve event that closes the incident |
The incident key is the check's ID. Each check has at most one open incident at a time: if a check that is already down sends another /fail ping, the open incident updates and no second incident opens.
Every trigger event has:
| Field | Value |
|---|---|
| Description | <check name> is down |
| Client | FlatLyne, linking to the check in your dashboard |
| Custom details | Check, Status, Schedule, Time Zone, Total Pings, Last Ping Type, Last Ping, Status changed to down at |
The resolve event adds a Downtime detail, such as "2 hours, 14 minutes". Urgency and escalation come from the settings of your PagerDuty service.
Set up the integration
Sign in to FlatLyne and open your project. Choose Integrations in the sidebar.
Find PagerDuty under Available integrations and click Configure ›.
Click Connect PagerDuty. A popup opens on PagerDuty. Sign in if you need to.
Choose the service or services that should receive FlatLyne incidents, then approve the connection.
The popup closes. The panel shows your PagerDuty account and the services it routes to, for example "Connected to Acme Corp — routing to Database backups." Alerts start right away.
To test the connection, create a check, let it miss its schedule or send it a /fail ping, and watch the incident open in PagerDuty. Then send it a success ping and watch the incident resolve. The quickstart shows how to create and ping a check.
Change services
Open Integrations, then PagerDuty, and click Reconnect PagerDuty. Choose the services you want.
Pause or remove the integration
- To stop alerts for a while, open the Actions menu on the PagerDuty row of the Integrations table and choose Pause. Choose Resume to turn it back on.
- To remove the integration, open the PagerDuty panel and click Disconnect. FlatLyne stops sending events to PagerDuty. You can also delete the FlatLyne integration from your service in PagerDuty.
Incidents that are already open in PagerDuty stay open after you disconnect. Resolve them in PagerDuty.
Delivery and retries
FlatLyne tries each PagerDuty service up to 3 times. An attempt fails if PagerDuty doesn't answer within 30 seconds or doesn't return 200. Each service is tried on its own, so one failing service doesn't block the others.
Support
Questions or problems with the integration? Email [email protected]. Include your account email, the name of the check, and what you expected to happen.
For other alert channels, see Alert channels.