We use cookies to ensure that we give you the best experience on our website.  Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it.

Your choices regarding cookies on this site.
Your preferences have been updated.
In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page.

Notifications via PagerDuty

Checkmk Manual
Last updated: August 14 2020

Related articles

Search in the manual

1. Function

The PagerDuty incident management platform can receive messages from a wide variety of sources and process them further – for example by filtering, sending notifications or initiating escalations. Notifications from Checkmk can be easily forwarded to the platform via a so-called integration key.

2. Configuring PagerDuty

PagerDuty provides integrations for many popular tools, including Checkmk. All you need is an Integration Key, which you create under PagerDuty as follows:

  1. Create a new service or open an existing one.
  2. In the corresponding service create a new integration via the Integrations tab.
  3. Assign any name and for the Integration Type choose Check_MK.
  4. Copy the created Integration Key.

3. Configuration in Checkmk

In Checkmk the integration requires only the specification of the integration key:

  1. For the Notification Method choose the item PagerDuty.
  2. Enter the copied key under Integration Key.

The filtering of the generated notifications can be implemented either in Checkmk, or in PagerDuty via the Event Rules. You can also optionally switch the PagerDuty connection to your own Checkmk user account. Simply create a standard user with a disabled login, and then create a personal notification rule.

You can test the connection using the commands. Use the Fake check results command and set a host covered by the rule to DOWN.