Integration guide · updated

PagerDuty + Vigil integration guide

Overview

Vigil by PuzariCloud checks websites, APIs, SSL certificates, domains, cron jobs (heartbeats) and servers. With this integration, a failed check triggers a PagerDuty incident with the monitor name, the error and a link to the check, and the recovery resolves the incident. You do not need to resolve anything by hand.

Requirements

  • A PagerDuty account with permission to add integrations to a service (Manager, Admin or Account Owner role).
  • A Vigil account on any plan, including Free, with permission to add alert channels (owner, admin or editor).

Support

If you need help with this integration, write to hello@puzaricloud.in or use puzaricloud.in/contact. We reply personally.

How it works

  • Trigger. When a monitor goes down or an alert escalates, Vigil sends a trigger event to PagerDuty's Events API v2 with severity critical. Other problems (failed health check, third-party status page, SSL, domain, DNS, security or error alerts) trigger with severity warning.
  • What the incident contains. Summary (for example "Checkout API is down"), source (the monitored URL), component (the monitor name), a link back to the check in Vigil, and details such as the event type, error message, HTTP status code and response time.
  • One incident per monitor. Every event uses the dedup key vigil-monitor-<monitor id>, so repeated failures of one monitor join the open incident instead of opening new ones.
  • Resolve. When the monitor recovers, Vigil sends a resolve event with the same dedup key and PagerDuty resolves the incident.
  • Information only. Slow responses, content or keyword changes and reports are sent as change events. They appear on the service timeline and never page anyone.
  • Test. The Send test button triggers an incident with severity info and the dedup key vigil-test, then resolves it straight away.
  • The integration is one way: acknowledging or resolving in PagerDuty does not change anything in Vigil.

Integration walkthrough

In PagerDuty

  1. Go to Services → Service Directory and open the service that should receive Vigil alerts (or create one).
  2. Open the Integrations tab and click Add an integration.
  3. Search for Vigil. If it is not listed in your account yet, choose Events API V2; it works the same way.
  4. Click Add, then open the new integration and copy the Integration Key (32 characters).

In Vigil

  1. Go to Alerts → Channels and add a channel of type PagerDuty.
  2. Paste the integration key into Integration key (Events API v2), give the channel a name and save.
  3. Press Send test on the channel. In PagerDuty you should see a test incident that resolves on its own.
  4. Attach the channel to the monitors that should page someone (on each monitor, or in a notification policy).

To try it end to end, add an uptime monitor for a URL that answers with an error, attach the channel, and wait for the first failed check: an incident is triggered. Point the monitor at a working URL and the incident resolves.

How to uninstall

  1. In Vigil, go to Alerts → Channels and delete the PagerDuty channel (or detach it from your monitors).
  2. In PagerDuty, open the service, go to Integrations, open the Vigil (or Events API V2) integration and delete it. Its integration key stops working at once.

FAQ

Which Vigil plan do I need?

Any plan, including Free. The PagerDuty channel is available on every plan.

Will one outage page people more than once?

No. Every event for a monitor uses the same dedup key, vigil-monitor-<monitor id>. While that incident is open, PagerDuty adds new triggers to it instead of opening a second incident.

What severity do incidents get?

critical when a monitor is down or an alert escalates, warning for other problems (failed health check, third-party status, SSL, domain, DNS, security or error alerts). You can map severities to urgency in PagerDuty's service settings.

Do warnings like slow responses or content changes page anyone?

No. Those are sent as change events. They show on the service timeline in PagerDuty and never page.

Can I send different monitors to different PagerDuty services?

Yes. Create one Vigil PagerDuty channel per service (each with its own integration key) and attach each monitor to the right channel.

If I acknowledge or resolve the incident in PagerDuty, does Vigil know?

No. The integration is one way, from Vigil to PagerDuty. If you resolve an incident by hand while the monitor is still failing, the next failure alert opens it again.

My account is in PagerDuty's EU service region. Does it work?

Vigil sends events to events.pagerduty.com. If the test fails for an EU account, write to hello@puzaricloud.in and we will set the channel to the EU endpoint.

PagerDuty is a trademark of PagerDuty, Inc. Vigil by PuzariCloud is not affiliated with PagerDuty. See also: incident.io guide, Spike.sh recipe.