Skip to content

Checkmk

Send Checkmk host and service alerts to Notifiq using a notification plug-in.

Features

  • Automatic state mapping (OK/UP → success, WARNING → warning, CRITICAL/DOWN → critical)
  • Support for all notification types (PROBLEM, RECOVERY, ACKNOWLEDGEMENT, FLAPPING, DOWNTIME)
  • Configurable TTL (default: 15 seconds)
  • HTTPS support with system CA bundle

Installation

1. SSH to your Checkmk server:

bash
omd su <SiteName>
cd local/share/check_mk/notifications/

2. Copy the script from this repository:

bash
cp /path/to/notifiq/examples/integrations/checkmk/webhook_notifiq .
chmod +x webhook_notifiq

Configuration in Checkmk

  1. Setup → Notifications → Add notification rule
  2. Choose triggering events (PROBLEM, RECOVERY, etc.)
  3. Notification method — select "Notifiq Webhook"
  4. Parameters:
    • First parameter: Your Notifiq server URL (e.g. https://notify.yourdomain.com)
    • Second parameter: Your API bearer token
  5. Save and activate changes

Notification format

Service alert:

Title: PROBLEM: Checkmk Service CPU Load on server-01
Message:
Type: PROBLEM
Host: server-01
Service: CPU Load
State: CRITICAL
Summary: CRIT - Load average: 8.50 (warn/crit at 4.00/8.00)

State mapping

Checkmk stateNotifiq level
OK, UPsuccess
WARNINGwarning
CRITICAL, DOWN, UNKNOWNcritical
Otherinfo

Notification type mapping

TypeLevel override
RECOVERYsuccess
ACKNOWLEDGEMENTinfo
FLAPPINGSTARTwarning
DOWNTIMESTARTinfo
PROBLEM(uses state mapping)

Troubleshooting

bash
# Check notification logs
tail -f var/log/notify.log

Common issues:

  • "Missing Notifiq URL" — Parameter 1 is empty
  • "Missing API token" — Parameter 2 is empty
  • Connection timeout — check firewall rules
  • SSL errors — check CA bundle paths in the script

Rate limiting

Add your Checkmk server's IP to Settings → Security → Rate Limit Whitelist to avoid hitting the /api/notify rate limit when many alerts fire simultaneously.