Turn any signal into insight and action. See how PagerDuty Digital Operations Management Platform integrates machine data and human intelligence to improve visibility and agility across organizations.
Cut through the noise. Unleash innovation and productivity.
Check out the latest features we’ve been working on—including event intelligence, machine learning, response automation, on-call, analytics, operations health management, integrations, and more.
Digital Operations Management arms organizations with the insights needed to turn data into opportunity across every operational use case, from DevOps, ITOps, Security, Support, and beyond.
Over 200 Integrations
Discover DevOps best practices with our library of webinars, whitepapers, reports, and much more.
Learn best practices and get support help with resources from our award-winning support team.
See how PagerDuty works with our live product demo — twice a week, every week.
Join live and on-demand webinars for product deep dives, industry trends, configuration training, and use case-specific best practices.
Interactive, simple-to-use API and technical documentation enables users to easily try updates and extend PagerDuty.
Engage with users and PagerDuty experts from our global community of 200k+ users. Become a member, connect, and share insights for success.
Get all your PagerDuty-related questions answered by exploring our in-depth support documentation and community forums.
It’s pretty well known that we live in a connected, always-on world where seconds matter when it comes to customer happiness. There are smaller incident...
PagerDuty helps organizations transform their digital operations. Learn more about PagerDuty's mission and what we do.
Meet our experienced and passionate executive team.
We are risk-taking innovators dedicated to delivering amazing products and delighting customers. Join us and do the best work of your career.
With the PagerDuty Foundation, we are committed to doing our part in giving back to the community.
This integration requires use of our v1 REST API which is currently in a decommissioning period, please contact support to gain access to a v1 REST API key to configure this integration.
For more information about the v1 REST API deprecation, take a look at our FAQ here: https://v2.developer.pagerduty.com/v2/docs/v1-rest-api-decommissioning-faq
We are working with partners to upgrade integrations to use our v2 REST API.
Zenoss is a very popular open source network, server and application monitoring system used by thousands of IT organizations. It provides one of the best event management systems available in any open source monitoring system. The plug-in architecture of Zenoss allows it to be extensible by anyone.PagerDuty extends Zenoss’s functionality by providing on-call scheduling, alerts and incidents tracking through the PagerDuty API. You are notified of the most critical Zenoss events by PagerDuty so you are able to take immediate action.
This guide describes how to integrate your Zenoss 4 installation with the PagerDuty ZenPack. You might need to slightly alter these instructions depending on your exact Linux distribution and your Zenoss configuration. If you are having trouble completing the installation, please contact us.
From the Configuration menu, select Services.
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.
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.
Click the Add Service or Add Integration button to save your new integration. You will be redirected to the Integrations page for your service.
Copy the Integration Key for your new integration:
Note: You may create multiple Generic API integrations for use with different PagerDuty policies. Zenoss 4 can be aligned to any number of different PagerDuty accounts and Generic API integrations.
Login to your Zenoss server’s shell as root. Open the /opt/zenoss/etc/zenactiond.conf file within your text editor. Update the zopeurl parameter to the URL that you use to access your Zenoss web interface. This parameter will be used to directly link from your PagerDuty console to your Zenoss web interface. Note: This can be an intranet URL. Make sure to remove the # symbol from this parameter so that the field is activated.
From your web browser, download the PagerDuty ZenPack to your local workstation. Note: Do not change the name of this file.
From the Zenoss web interface, go to ADVANCED > Settings > ZenPacks > Click on the Gear Icon > Install ZenPack:
Select the PagerDuty ZenPack that you downloaded and click OK.
Restart Zenoss. From a shell:
sudo -u zenoss /opt/zenoss/bin/zenoss restart
You will now see PagerDuty under ADVANCED > Settings:
Select this new PagerDuty option. You can then enter your PagerDuty subdomain and API key then press enter. For more information on API Access Keys, read this knowledge base article. Note: You will not use the service API key here. Please read the aforementioned article for more information.
Note: Once you hit the Apply button, the list of all PagerDuty Generic API services will populate. If your service does not show up, confirm your settings and verify that your services is of type Generic API within PagerDuty.
Go to EVENTS > Triggers and click on the + button to add a trigger.
Enter an Id for your trigger. We’re using PagerDuty, but you may want to use something more descriptive, such as “Critical Alert.” Click the SUBMIT button once you’ve entered an Id.
Select your trigger and click on the gear icon to configure it.
Configure the trigger to the rule(s) that you would like to trigger alerts within PagerDuty. Once you have completed configuring your rule(s), click on the SUBMIT button.
Click on Notifications from the left-hand menu, then click on the + icon to add a new notification.
Enter an Id for the notification, and select PagerDuty for the Action. In this example we use PagerDuty for the id, although you may want to use something more descriptive. Click on the SUBMIT button once the form is complete.
Select your new notification and click on the gear icon to configure it.
Check the Enabled box, then select the trigger that you made earlier, then click the Add button. The trigger should show up in the lower box under Triggers.
Click on the Content tab. Now select the PagerDuty service from the drop-down menu. Note: You can also type the service name. This is the service that will get notified when an alert is triggered within Zenoss. If you are connecting to multiple PagerDuty services from Zenoss, this is where you would select the different services. The PagerDuty ZenPack will automatically populate the remaining fields. Many of these fields are customizable. For a full list of available variables, check the FAQ. Click the SUBMIT button once you’re finished.
To verify that everything is working, you’ll want to trigger a new alert within Zenoss, which will in-turn trigger an incident within PagerDuty. When viewing the details for an incident, you can use the View in Zenoss link to take you to the event within your Zenoss web interface.
This is an issue with the version of Python that you have installed. You can either install the ZenPack from source or change the filename from “ZenPacks.PagerDuty.APINotification-1.0.0-py2.71.egg” to “ZenPacks.PagerDuty.APINotification-1.0.0.egg” and then reinstall the ZenPack.
This is easy to do with the current integration, as each Zenoss notification can be associated with a PagerDuty service. You would just need to add multiple notifications within Zenoss to tie to each of your PagerDuty services.
If a PagerDuty server can’t be reached for any reason, Zenoss will re-send the notification to PagerDuty every 60 seconds. This is configurable under the notification configuration.
You should configure an external ping check service to monitor your site’s external connectivity. Of course, you can use PagerDuty to forward alerts from these services.
PagerDuty does not support unacknowledged incidents. The event will remain as acknowledged within PagerDuty until it is resolved.
Other event properties can be found in Section 7.1.2 (Page 89) of the ZenOSS Core Administration Guide. Note: The Incident Key needs to be unique per incident.
You can do this by editing the ~zenoss/.bashrc file to include the http_proxy and https_proxy environment variables. The lines added would look like:
For the changes to take effect, you must either fully stop and start the Zenoss service or reboot the server.
Please contact us if you’re unable to sort out the difficulty.
600 Townsend St., #200
San Francisco, CA 94103
260 Queen St W #300,
Toronto, ON M5V 1Z8, Canada
1416 NW 46th St., St. 301
Seattle, WA 98107
5 Martin Place
1 Fore St,
London EC2Y 9DT
© 2009 - 2018