LibreNMS alerts, routed to the right on-call engineer
Receive LibreNMS alerts via an API alert transport with a body template. EvoHub turns each LibreNMS alert into an on-call alert, runs it through your escalation policy, and pages people by voice call, mobile push and email.
How the LibreNMS integration works
- Create a LibreNMS 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 LibreNMS using the steps below.
- Each LibreNMS 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 alert (keep "Recovery alerts" on in the rule).
Set up LibreNMS
Create the integration in EvoHub first — it shows your personal integration URL to paste below.
# 1. Alerts → Alert Transports → Create alert transport
Transport type: API
API Method: POST
API URL: <your EvoHub integration URL, without ?key=…>
# — no ?key=… here: LibreNMS drops the URL's query.
Options: key=<your integration key>
# — LibreNMS sends Options as the query string; this is
# what authenticates. A key left in the URL gives 401.
Headers: Content-Type=application/json
Body — paste as-is, on one line (LibreNMS 25.7 or later;
# json_encode quotes and escapes each value itself):
{"title":{{ $title|json_encode }},"rule":{{ $name|json_encode }},"rule_id":{{ $rule_id|json_encode }},"alert_id":{{ $alert_id|json_encode }},"device_id":{{ $device_id|json_encode }},"hostname":{{ $hostname|json_encode }},"sysName":{{ $sysName|json_encode }},"ip":{{ $ip|json_encode }},"os":{{ $os|json_encode }},"location":{{ $location|json_encode }},"severity":{{ $severity|json_encode }},"state":{{ $state|json_encode }},"timestamp":{{ $timestamp|json_encode }}}
# Older LibreNMS: write each value as "{{ $title }}" (in
# quotes, no |json_encode) — EvoHub repairs line breaks and
# quotes inside values.
# 2. Press Test — EvoHub answers OK and opens no alert.
# 3. Attach the transport to your alert rules (or make it the
# default) and keep "Recovery alerts" on in each rule —
# the recovery is what resolves the alert.
# One EvoHub alert per rule and device. critical → critical,
# warning → medium; recovered (state 0) → resolves;
# acknowledged in LibreNMS (state 2) → no change.LibreNMS + EvoHub — FAQ
How do I connect LibreNMS to EvoHub?
In EvoHub, go to On-Call → Integrations, add LibreNMS, and choose an escalation policy. Then configure LibreNMS with the integration URL EvoHub shows you — the exact steps are on this page.
Do LibreNMS alerts resolve automatically in EvoHub?
Resolves automatically on the recovery alert (keep "Recovery alerts" on in the rule).
How is the LibreNMS 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.Ş.