​
Overview

The Checkmk provider enables seamless integration between Keep and Checkmk. It allows you to get alerts from Checkmk to Keep via webhooks making it easier to manage your infrastructure and applications in one place.

​
Connecting Checkmk to Keep

To connect Checkmk to Keep, you need to configure it as a webhook from Checkmk. Follow the steps below to set up the integration:
  1. Keep webhook script need to installed on the Checkmk server.
  2. You can download the Keep webhook script using the following command: 
wget -O webhook-keep.py https://github.com/keephq/keep/blob/main/keep/providers/checkmk_provider/webhook-keep.py?raw=true
  1. Copy the downloaded script to the following path on the Checkmk server:
If you are using Checkmk Docker container, then copy it to the following path according to your docker volume mapping: 
cp webhook-keep.py /omd/sites/<site_name>/local/share/check_mk/notifications/webhook-keep.py
cd /omd/sites/<site_name>/local/share/check_mk/notifications
If you are using Checkmk installed on the server, then copy it to the following path: 
cp webhook-keep.py ~/local/share/check_mk/notifications/webhook-keep.py
cd ~/local/share/check_mk/notifications
  1. Make the script executable:
chmod +x webhook-keep.py
  1. Now go to the Checkmk web interface and navigate to Setup
  1. Click on Notifications under Events
  1. Click on Add rule
  1. In the Notifications method method, select “webhook-keep” as the notification method.
  1. Configure the Rule properties, Contact selections, and Conditions according to your requirements.
  2. The first parameter is the Webhook URL of Keep which is https://api.keephq.dev/alerts/event/checkmk.
  3. The second parameter is the API Key of Keep which you can generate in the Keep settings.
  4. Click on Save to save the configuration.
  5. Now you will start receiving alerts from Checkmk to Keep via webhooks when the configured conditions are met.

​
In workflows

This provider can’t be used as a “step” or “action” in workflows. If you want to use it, please let us know by creating an issue in the GitHub repository.