325 Front St W
Toronto, ON M5V 2Y1, Canada
Notify developers and security analysts when Feroot Inspector uncovers a malicious event and triggers alerts
Below is the step-by-step instructions on how to connect PagerDuty to Feroot and manage this integration
The PagerDuty integration requires an admin role in order to authorize the account. If you are not an admin, please reach out to an admin or account owner within your organization to configure the integration for you.
If you need any help getting the PagerDuty integration up and running, please do not hesitate to reach out to us via email at firstname.lastname@example.org
There are two ways to integrate Feroot with PagerDuty. The first is via PagerDuty global event routing or via 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 enables you to route events to specific services based on the payload of the event from Feroot.
There are two ways to add an integration to a PagerDuty service:
Automatically – Which is completed using a simplified integration workflow. Please see the “In Feroot” section for more information.
To stop the Feroot project from creating triggers in PagerDuty, you will need to disable the PagerDuty integration in Feroot.
See Client-Side Security in Action!