PagerDuty is for when a dark screen is something somebody is on call for.
Connecting
Under Settings, then Notifications, choose Connect to PagerDuty and authorise.
You then either pick an existing service or create one. Creating from Screenly asks for a service name and gives you an integration key using PagerDuty’s Events API V2.
Give it a service of its own rather than attaching to one that already exists for something else. Screens have a different urgency profile from an application outage, and separating them means the escalation policy can differ too.
Deciding what belongs here
The temptation is to route every screen. Resist it.
PagerDuty wakes people. A screen in a corridor going offline at 2am does not justify that; a screen in a plant control room might. Route the ones that matter and leave the rest on email or Slack.
If everything pages, nothing does, and the first thing an on-call engineer learns is to ignore Screenly.
Recovery
The Screens come back online event resolves the picture, and it is worth enabling alongside the offline one. Most screens recover on their own within minutes, and without the recovery event somebody is investigating a problem that has already fixed itself.
Disconnecting
From the Integrations tab, or by revoking Screenly in PagerDuty. Incidents stop being raised; anything already open stays open.