Netuitive is excited to announce a new integration with PagerDuty.
This blog demonstrates how easy it is to send Netuitive monitoring alarms to PagerDuty. Netuitive provides an intuitive web UI that sends event details to any external system for alerting. By using this to send information through PagerDuty’s API, users can easily enable a seamless connection of the two services.
Below is an example use-case walking through setup and the alerting procedure:
Metrics collected from Netuitive’s browser agent can use a dynamic policy set to determine if the total response time on your homepage is above the expected threshold (automatically determined through behavior learning.) Once the policy observes this condition, it will generate an event and Netuitive will send event data to PagerDuty as an incident which will alert the team to take action.
Real Life Example
While Netuitive is monitoring a website, it experienced some performance issues including a 9.2 second page load time at 469% above normal. Because this data spiked well above expected behavior, an event is triggered and Netuitive simultaneously opens an incident in PagerDuty.
You can leverage PagerDuty’s REST API to create the incident using Netuitive data. It only takes 4 steps:
- Access your API key in PagerDuty
- Create your notification type in Netuitive
- Add this notification to a Netuitive policy
- Alerts now automatically generated in PagerDuty
Here’s a more detailed walk through:
1. In PagerDuty users can create an API service which generates the key required in Netuitive. This key will be used in the body of the JSON message. So you just simply need to copy this 32 bit string.
2. In Netuitive, now create the notification. The details for the custom JSON payload are in the product documentation.
3. Now add the notification to any policy in Netuitive.
4. When the policy is triggered, an incident is opened in PagerDuty and your team is alerted appropriately.
While surprisingly quick to set up, the process offers much needed flexibility without creating longer implementation times. The entire process takes about 15 minutes to set up in a production environment.