PLEASE NOTE THIS IS AN ARCHIVED POST - Netuitive has since become Metricly, and the tool has matured greatly since the time this was written!

Metricly is excited to announce a new integration with PagerDuty.

This blog demonstrates how easy it is to send Metricly monitoring alarms to PagerDuty. Metricly 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:

Use Case

Metrics collected from Metricly’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 Metricly will send event data to PagerDuty as an incident which will alert the team to take action.

Real Life Example

While Metricly 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 Metricly simultaneously opens an incident in PagerDuty.

Real Example (PagerDuty)


You can leverage PagerDuty’s REST API to create the incident using Metricly data. It only takes 4 steps:

  1. Access your API key in PagerDuty
  2. Create your notification type in Metricly
  3. Add this notification to a Metricly policy
  4. 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 Metricly. This key will be used in the body of the JSON message. So you just simply need to copy this 32 bit string.

ServicesKey (PagerDuty)

2. In Metricly, now create the notification. The details for the custom JSON payload are in the product documentation.

Step 2 (Pager Duty)

3. Now add the notification to any policy in Metricly.

Step 3 (PagerDuty)

4. When the policy is triggered, an incident is opened in PagerDuty and your team is alerted appropriately.

Step 4 (PagerDuty)

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.

Try it for yourself – start monitoring with Metricly and take advantage of our 21-day free trial.

Learn more
About Metricly

Metricly coaches users throughout their cloud journey to organize, plan, analyze, and optimize their public cloud resources.

Try Metricly Free

About the Author