Checkmk Integration (v 2.0+ )
The ilert checkmk native integration ships with checkmk version >= 2.0.0.
With the native ilert notification integration in Checkmk, you can automatically create alerts in ilert from Checkmk alerts. That way, you will never miss a critical alert and always alert the right person using ilert's on-call schedules, automatic escalation, and multiple alerting channels. When checkmk creates an alert, ilert will alert the on-call person through their preferred channel, including SMS, phone calls, push notifications and Slack. ilert will automatically escalate to the next person, if the alert is not acknowledged. ilert also lets you define alerting rules based on support hours and delay alerts until your support hours start.
In ilert: Create a Checkmk alert source
Go to Alert sources --> Alert sources and click on Create new alert source
Search for Checkmk in the search field, click on the Checkmk tile and click on Next.
Give your alert source a name, optionally assign teams and click Next.
Select an escalation policy by creating a new one or assigning an existing one.
Select you Alert grouping preference and click Continue setup. You may click Do not group alerts for now and change it later.
The next page show additional settings such as customer alert templates or notification prioritiy. Click on Finish setup for now.
On the final page, an API key and / or webhook URL will be generated that you will need later in this guide.
In checkmk: configure the ilert notification
Navigate to the Setup --> Events --> Notifications
In the Notification configuration, click on Add rule
In the Notification Method section choose ilert method. Enter enter the API key and click on Save.
FAQ
Which notification types are processed?
The plugin processes the notification types PROBLEM , ACKNOWLEDGEMENT and RECOVERY. The remaining Notification Types (including FLAPPING* and DOWNTIME*) are ignored.
checkmk has the following alarm types:
| Types | Description |
|---|---|
PROBLEM | Normal host or service problem |
RECOVERY | Host / service goes UP / OK again |
ACKNOWLEDGMENT | Acknowledgment of a problem |
FLAPPINGSTART | A host / service begins to be discontinuous |
FLAPPINGSTOP | End of discontinuity |
DOWNTIMESTART | Start of scheduled maintenance. |
DOWNTIMEEND | Normal end of maintenance |
DOWNTIMECANCELLED | Premature termination of maintenance |
CUSTOM | Alarm triggered manually by command |
ALERT HANDLER | Alerthandler execution (CEE from 1.4.0i2) |
Will alerts in ilert be resolved automatically?
Yes, as soon as the state of a host / service is UP or OK again in checkmk, the associated alert is resolved in ilert. If a problem is acknowledged in checkmk, the associated alert in ilert is set to the status Accepted.
Can I link checkmk to multiple alert sources in ilert?
Yes, create a checkmk user for each alert source in checkmk. Proceed as described above in the instructions.
Last updated
