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 forwarded to the platform via a key.

1. 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.

2. Configuring Checkmk

You have already learned how to set up Checkmk notifications in general in the article on notifications.

In Checkmk it is now sufficient to specify the key copied above:

  1. Create a new notification rule with Setup > Events > Notifications > Add rule.

  2. For the Notification Method choose PagerDuty.

  3. Enter the copied key under Integration Key:

    The notification method settings for PagerDuty.

    Instead of entering the key directly here, you can also read it from the password store - provided it was previously stored there.

When using the following Contact selection box, note the following two points:

  1. When selecting contacts, make sure that the notifications are only sent to one contact, e.g. by selecting a single user. With the notification methods for ticket systems etc., the contact selection only serves to specify that notifications are sent. However, the notifications are not sent to the selected user, but to the ticket system. Note that a contact selection via contact groups, all contacts of an object or similar usually generates several identical notifications for an event, which then end up in the ticket system twice, three times or even more often.

  2. If the first point is fulfilled, but the user is used in several notification rules for the same method, then only the last rule applies in each case. It is therefore advisable to create a separate functional user for each of these notification rules.

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 find out how to test the new notification method in the article on notifications.

On this page