Integration

PagerDuty

The findings that deserve an on-call page go to PagerDuty; the others stay in the application.

Request a demonstration Try the online demo

What PagerDuty receives

Every new finding can go to this channel according to your alert rules: minimum severity, finding types, specific rules, projects. Only new findings are notified; a known, reopened or resolved finding generates nothing. Messages are written in English. The channel can be tested from the application with a fictitious event.

With PagerDuty, the alert rule earns its keep: limit it to critical and high severities, or to a few specific rules, so nobody is woken up for a test bucket.

How to connect it

In “Settings”, “Integrations” tab, “Notifications” sub-tab, add the channel with its incoming connector address. Then, in the “Notifications” tab, create an alert rule targeting it. System events (service, scan failure), end-of-scan and assistant summary events only go out if you tick them explicitly.

For PagerDuty, you provide the routing key of an Events API v2 integration.

See it on your accounts

The online demonstration is open to all, on fictitious data. For an instance on your own accounts, request a demonstration.

Request a demonstration Try the online demo