> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/checkmk/native.md).

# 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 <a href="#create-alarm-source" id="create-alarm-source"></a>

1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Checkmk**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.

   <figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-8a281bf3931f5a1a531951ce97984d50989dd875%2Falert-source-escalation-step.png?alt=media" alt="The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below."><figcaption><p>Pick an existing escalation policy, or generate a basic one without leaving the wizard.</p></figcaption></figure>
5. Select **Default grouping** and click **Next**. The wizard then asks **Enable two-way alert status sync?** Decide whether status changes should also flow back to Checkmk, and click **Continue setup**.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now, or **Continue setup** if you turned two-way sync on.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.

## In checkmk: configure the ilert notification <a href="#configure-ilert-plugin" id="configure-ilert-plugin"></a>

1. Navigate to the **Setup** --> **Events** --> **Notifications**

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MYyXoaE8PU_puks-jbV%2F-MYyY7zyyYKUHINXnlkq%2FPicture%201.png?alt=media\&token=f69b952e-47ae-4bf4-8bfd-9cedafc87f55)

2. In the **Notification configuration**, click on **Add rule**

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MYyXoaE8PU_puks-jbV%2F-MYyYVArNDT6_Fxnf_gJ%2FPicture%202.png?alt=media\&token=6161a334-b08e-46f2-bb78-3edd7675181b)

3. In the **Notification Method** section choose ilert method. Enter enter the **API key** and click on **Save**.

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MYyXoaE8PU_puks-jbV%2F-MYy_wHqojIs37GD8Rf7%2FPicture%204.png?alt=media\&token=2ff351e1-c2f2-46da-a36a-0e82632e83fe)

## Optional: Bidirectional sync (acknowledges alerts in Checkmk)

{% hint style="info" %}
**Please note:** Bi-directional sync requires an [ilert Scale plan](https://www.ilert.com/pricing) or higher.
{% endhint %}

As the Checkmk API allows for host and service problems to be acknowledged, ilert offers a setting to configure your Checkmk alert source in bidirectional mode. This will automatically create a connector and alert action for your alert source that will pipe accept events and comments from ilert to Checkmk and acknowledge the problem related to the ilert alert.\
\
1\. Enable the **Bi-directional** checkbox during your alert sources creation.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FDA1Buy8asjnYYqXhie6Z%2Fbidirectional-option.png?alt=media&amp;token=8a48cffa-6015-4369-ada4-a41f851b4bdf" alt="" width="563"><figcaption></figcaption></figure>

\
\
2\. Enter your Checkmk Url into the **Url** field, and fill in an API user's information in the **Username** and **Password** fields.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fxso2ScKegQBXS1gc0A9m%2Fmetadata.png?alt=media&amp;token=f9952ffc-852c-4e30-9088-a2228f7a23a4" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
You cannot add bidirectional mode after an alert source has already been created. You will have to create a new alert source. Bidirectional mode cannot be enabled through the API.
{% endhint %}

## FAQ <a href="#faq" id="faq"></a>

**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:

<table><thead><tr><th>Types</th><th width="371.5">Description</th></tr></thead><tbody><tr><td>PROBLEM</td><td>Normal host or service problem</td></tr><tr><td>RECOVERY</td><td>Host / service goes UP / OK again</td></tr><tr><td>ACKNOWLEDGMENT</td><td>Acknowledgment of a problem</td></tr><tr><td>FLAPPINGSTART</td><td>A host / service begins to be discontinuous</td></tr><tr><td>FLAPPINGSTOP</td><td>End of discontinuity</td></tr><tr><td>DOWNTIMESTART</td><td>Start of scheduled maintenance.</td></tr><tr><td>DOWNTIMEEND</td><td>Normal end of maintenance</td></tr><tr><td>DOWNTIMECANCELLED</td><td>Premature termination of maintenance</td></tr><tr><td>CUSTOM</td><td>Alarm triggered manually by command</td></tr><tr><td>ALERT HANDLER</td><td>Alerthandler execution (CEE from 1.4.0i2)</td></tr></tbody></table>

\
**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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ilert.com/integrations/inbound-integrations/checkmk/native.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.