Thursday, May 1, 2014

Creating Multiple Opsview Pager Duty Services

Pager Duty, the popular alerting system for sysadmins, provides easy integration with a wide variety of tools. Recently, I have been using Opsview, a fork of Nagios, for system monitoring. Integrating Opsview with Pager Duty is fairly simple when creating a "catch all" user that sends every alert to Pager Duty. However, creating fine-tuned alerts associated with different Pager Duty services is a bit more complex.

The following steps should be completed for every service that requires a Pager Duty integration:

  1. Within Pager Duty, click the "Services" tab and then click "Add New Service."

  2. Provide a name for the service, select an escalation policy, and then choose "Opsview" in the "Integration" menu.

  3. On the next page, copy your Service API Key
  4. At this point, you need to prepare Opsview for Pager Duty integration if you haven't done so already. I am not going to repeat these steps because Pager Duty has an excellent guide here. Follow the steps under "On Your Server" and "In Opsview" up to step 13.
  5. When you create a new user in Opsview, give it a unique name for the service. In this case, I am using "Pager Duty - Flickr".
  6. The role should be Administrator and the password should be something long, complex, and not easily guessable. You will never need it again, so feel free to make it 100 characters.
  7. Click Next
  8. In the "Pagerduty Service Key" box, enter the key you copied in step 3
  9. Submit the changes and you should now see your user listed
  10. Now, click on "No Notifications Configured" next to your user to be taken to the notifications page
  11. On this page, enter a name, check the box to notify by Pagerduty, and select all of the host groups and services related to that service only
  12. Edit the other defaults as needed, then submit the changes
  13. Be sure to reload Opsview so your changes take effect
  14. Now, you can repeat this process of creating a new user for each service you want to monitor separately

No comments:

Post a Comment