In this article, the screenshots and the GUI navigation described are not yet updated to Checkmk version 2.0.0. However, nothing fundamental has changed in the described functions themselves and most of the functions can be found quickly with the Monitor or Setup menu search of the Checkmk 2.0.0 user interface. We will update this article as soon as possible.
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:
Create a new service or open an existing one.
In the corresponding service create a new integration via the Integrations tab.
Assign any name and for the Integration Type choose Check_MK.
Copy the created Integration Key.
3. Configuration in Checkmk
In Checkmk the integration requires only the specification of the integration key:
For the Notification Method choose the item PagerDuty.
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.