Notify the on-call developers or operations people when Feroot triggers an alert
Below is the step-by-step instructions on how to connect PagerDuty to Feroot and manage this integration
Feroot creates alert events if condition in alert rule is satisfied. Alert events from Feroot trigger a new incident on the corresponding PagerDuty Service or Global Event Routing.
PagerDuty integrations require an Admin base role for account authorization. If you do not have this role, please reach out to an Admin or Account Owner within your organization to configure the integration.
If you need any help about this integration, you can connect us via firstname.lastname@example.org
There are two ways to integrate Feroot with PagerDuty: via Global Event Routing or on a PagerDuty Service. If you are adding this integration to an existing PagerDuty service, please skip to the Integrating with a PagerDuty Service section of this guide.
Integrating with Global Event Routing
Integrating with Global Event Routing enables you to route events to specific services based on the payload of the event from Feroot.
Integrating with a PagerDuty Service
There are two major ways to add an integration to a service:
Automatically – Is achieved using simplified integration workflow. Please see “In Feroot” section how to do that.
To stop Feroot project from creating triggers in PagerDuty, you need disable PagerDuty integration in Feroot.