Scout Integration Guide

The Scout application delivers a streamlined server monitoring system developed for enterprise-level needs. It uses realtime graphs to add visibility to your infrastructure, one-click plug-ins for extensibility and an API for custom solutions.

If you are having trouble with this integration, please contact us.

In PagerDuty

  1. From the Configuration menu, select Services.

  2. On your Services page:If you are creating a new service for your integration, click +Add New Service.

    If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +New Integration button.

  3. RS-Add-New-Service

  4. Select your app from the Integration Type menu and enter an Integration Name.If you are creating a new service for your integration, in General Settings, enter a Name for your new service. Then, in Incident Settings, specify the Escalation Policy, Notification Urgency, and Incident Behavior for your new service.

  5. Click the Add Service or Add Integration button to save your new integration. You will be redirected to the Integrations page for your service.

In Scout

  1. Click on Notifications in the top Navigation bar.

  2. Under Notification Channels, click on Add PagerDuty.

  3. Enter the email and password you use to login to PagerDuty to enable Scout to integrate with your account.

  4. Select the service you created earlier, then click Finish Integration.

  5. Congratulations! You have completed the integration. It should now appear as a Notification Channel.

Verify that Scout and PagerDuty are Communicating

Once an alert has been created within Scout, you can verify that PagerDuty triggered a new incident by doing the following:

  1. Create a trigger that can used to create an incident in Scout. On an Amazon EC2 instance, after installing Ruby and the scout gem, one working example would be set the “CPU Steal” metric to send an alert when CPU usage passes 50%. To do this, go to the Servers tab and select your server; then select the Triggers tab and select Add Trigger. You should then see the screen shown below.scouttrigger

  2. Click on Create Trigger and verify that the trigger has been created in your account.
    Screen Shot 2014-03-27 at 5.03.29 PM

  3. Trigger an incident. On an EC2 Amazon instance, this can be done by issuing this command from the command line: perl -e “while(1) {}”
    Screen Shot 2014-03-27 at 5.19.13 PM

  4. Confirm that the alert appears in Scout.
    Screen Shot 2014-03-27 at 5.26.50 PM

  5. Confirm that a matching incident also appears in PagerDuty.


Can you configure Scout to change how it reports to PagerDuty?

You can customize the integration through the use of difference integration policies, as shown in the explanatory text on Scout’s site below.
Screen Shot 2014-03-27 at 5.39.13 PM

If an alert resolves in Scout, does the incident also resolve in PagerDuty?

Yes, it does. The ‘resolve’ is propagated automatically through the API, and should be visible in your dashboard.
Screen Shot 2014-03-28 at 9.44.46 AM