The Opsgenie alternative for LibreNMS

LibreNMS gives you deep network monitoring; NOCgenie gives you the on-call response. Configure a LibreNMS API/webhook transport and every alert is deduplicated, routed by schedule, and escalated until acknowledged. A drop-in Opsgenie replacement that maps LibreNMS severities and recoveries out of the box.

Connect LibreNMS to NOCgenie

  1. 1
    Create a LibreNMS integration in NOCgenie
    Settings → Integrations → new LibreNMS integration; copy the inbound URL.
  2. 2
    Add an API transport in LibreNMS
    Settings → Alerting → Transports → API, method POST, with the JSON body template below.
  3. 3
    Map severities + recoveries
    critical→P1, warning→P3; state=0 (or severity ok) auto-closes. Alerts dedup on host + rule.
{"host":"{{ $hostname }}","sysName":"{{ $sysName }}","title":"{{ $title }}",
 "rule":"{{ $name }}","severity":"{{ $severity }}","state":{{ $state }},
 "id":"{{ $id }}","msg":"{{ $msg }}","faults":{{ $faults }}}
# POST to: https://app.nocgenie.com/api/v1/inbound/<your-token>

FAQ

What LibreNMS fields does NOCgenie use?

host/sysName, the rule name, severity, state and msg. Severity sets priority; state 0 (recovered) or severity ok auto-closes.

Will a flapping device spam my on-call?

No. Alerts dedup on host + rule, and NOCgenie's flood protection collapses storms into a single notification.

Ready before prod isn't.

Start free in minutes — route your first LibreNMS alert to the right responder today.

Start free

Other integrations

PrometheusGrafanaObserviumZabbixUptime KumaAll →