Checkmk alerts, routed to the right on-call engineer
Receive Checkmk host and service problems through a ready-made notification script. EvoHub turns each Checkmk alert into an on-call alert, runs it through your escalation policy, and pages people by voice call, mobile push and email.
How the Checkmk integration works
- Create a Checkmk integration in EvoHub On-Call and pick the escalation policy it should notify.
- EvoHub gives the integration its own URL (or inbound address) with a unique key — paste it into Checkmk using the steps below.
- Each Checkmk alert opens an EvoHub alert, and your escalation policy pages the on-call person — then the next step if nobody acknowledges.
- Resolves automatically on the RECOVERY notification (include the changes back to OK / UP in the rule).
Set up Checkmk
Create the integration in EvoHub first — it shows your personal integration URL to paste below.
# As the site user (omd su <site>):
# 1. Save this script as
# ~/local/share/check_mk/notifications/evohub — paste as-is
# (Python 3 standard library only), then: chmod +x it
#!/usr/bin/env python3
# EvoHub On-Call
# Checkmk notification script. Install as the site user:
# ~/local/share/check_mk/notifications/evohub (chmod +x)
# Rule parameter 1 = your EvoHub integration URL.
# Test by hand (as the site user): ./evohub --test '<URL>'
import json
import os
import sys
import urllib.error
import urllib.request
# Only these variables are sent: never the rule parameters (they hold the
# URL and its key) nor contact details.
FIELDS = (
"WHAT", "NOTIFICATIONTYPE", "HOSTNAME", "HOSTALIAS", "HOSTADDRESS",
"HOSTSTATE", "HOSTSTATEID", "HOSTOUTPUT", "LONGHOSTOUTPUT",
"SERVICEDESC", "SERVICESTATE", "SERVICESTATEID", "SERVICEOUTPUT",
"LONGSERVICEOUTPUT", "HOSTTAGS", "OMD_SITE", "SHORTDATETIME",
"HOSTURL", "SERVICEURL", "NOTIFICATIONAUTHOR", "NOTIFICATIONCOMMENT",
)
def post(url, payload):
req = urllib.request.Request(
url,
data=json.dumps(payload).encode("utf-8"),
method="POST",
headers={"Content-Type": "application/json", "User-Agent": "evohub-checkmk/1"},
)
try:
with urllib.request.urlopen(req, timeout=10) as resp:
resp.read()
print("EvoHub: delivered")
return 0
except urllib.error.HTTPError as e:
print("EvoHub answered HTTP %d" % e.code)
# 429 and 5xx are worth a retry (exit 1); other refusals are final.
return 1 if e.code == 429 or e.code >= 500 else 2
except (urllib.error.URLError, OSError) as e:
print("Could not reach EvoHub: %s" % getattr(e, "reason", e))
return 1
def main(argv):
if len(argv) == 3 and argv[1] == "--test":
return post(argv[2], {"evohub_test": True})
url = os.environ.get("NOTIFY_PARAMETER_1", "").strip()
if not url:
print("Set the EvoHub integration URL as the rule's first parameter")
return 2
payload = {}
for name in FIELDS:
value = os.environ.get("NOTIFY_" + name)
if value:
payload["NOTIFY_" + name] = value
return post(url, payload)
if __name__ == "__main__":
sys.exit(main(sys.argv))
# 2. Check the connection — EvoHub answers OK, opens no alert:
~/local/share/check_mk/notifications/evohub --test '<your EvoHub integration URL>'
# 3. Setup → Events → Notifications → Add notification rule
# (Checkmk 2.3 and 2.4; on 2.2 and earlier: Setup →
# Notifications)
Notification method: EvoHub On-Call
Parameters (first one): <your EvoHub integration URL>
Contact selection: one user (e.g. a dedicated "evohub" user)
# — the script runs once per selected contact; repeats only
# retrigger the same alert, but one call is cleaner.
Triggering events: problems AND the changes back to OK / UP
# — the recovery is what resolves the alert.
# 4. Activate changes.
# One EvoHub alert per host or host + service. CRIT / DOWN →
# critical, UNREACH → high, WARN → medium, UNKNOWN → low.
# RECOVERY resolves; acknowledgements, downtimes and flapping
# notifications are accepted and change nothing.Checkmk + EvoHub — FAQ
How do I connect Checkmk to EvoHub?
In EvoHub, go to On-Call → Integrations, add Checkmk, and choose an escalation policy. Then configure Checkmk with the integration URL EvoHub shows you — the exact steps are on this page.
Do Checkmk alerts resolve automatically in EvoHub?
Resolves automatically on the RECOVERY notification (include the changes back to OK / UP in the rule).
How is the Checkmk integration priced?
Integrations are included. EvoHub bills on usage, not per seat: an ingested alert costs 1 EvoHub token (about $0.015), push and webhook notifications are free, and every account gets 200 free tokens each month.
Start free — 200 EvoHub tokens every month. See pricing.
Last updated: · EvoHub is built and operated by EvoSync Teknoloji A.Ş.