OpenNMS and ilert: Smarter Incident Response for Network Teams

OpenNMS is now an official integration partner of ilert, the incident management platform built for teams that run always-on services. With the new ilert OpenNMS plugin, alarms raised in OpenNMS flow directly into ilert, where they reach the right on-call responder through the channels they actually answer: push notifications, SMS, voice calls, and chat.

The result is a monitoring and incident response workflow that works end to end. OpenNMS detects the problem. ilert makes sure a person acts on it. When the alarm is acknowledged or cleared in OpenNMS, ilert stays in sync automatically, so the two systems always agree on what is still open.

Detection is only half the job

A network monitoring platform earns its keep by catching problems early. But catching a problem and getting it fixed are two different things. Between them sits a familiar gap: the alarm fires, and someone has to notice it, decide whether it matters, and find the person who can resolve it. At 3 a.m., or on a holiday weekend, that gap is where downtime lives.

Most teams close it with a patchwork of email notifications, chat channels, and manually maintained phone lists. It works until it doesn't. Alerts get buried, the wrong person is paged, or nobody is paged at all.

ilert exists to close that gap. It handles on-call scheduling, escalation policies, multi-channel notifications, and the analytics that show how quickly teams are responding. Pairing it with OpenNMS means the alarm data you already trust now drives a response process you can rely on.

How the integration works

The integration is a plugin that runs inside OpenNMS. Once installed, it watches the alarm stream and forwards matching alarms to an ilert alert source. From there, ilert takes over routing and notification.

A few things stand out for teams evaluating it:

You choose what gets forwarded. A flexible filter decides which alarms reach ilert, whether that is everything at major severity and above, alarms on a specific group of nodes, or a particular class of problem. Nothing pages a human unless you say it should.
Priority follows severity. Critical and major alarms create high-priority alerts that run your escalation policy. Lower severities create low-priority alerts that inform without waking anyone up.
Short blips stay quiet. An optional hold-down delay waits before alerting, so an outage that resolves itself in a minute or two never becomes a page.
Status stays in sync. Acknowledging an alarm in OpenNMS accepts the alert in ilert. Clearing it resolves the alert. Responders see the real state of the network, not a stale copy.
Every alert links back. Each ilert alert carries a deep link to the alarm in OpenNMS, so the responder lands on the details with one tap.
Multiple teams, multiple routes. Different classes of alarm can be sent to different ilert alert sources, each with its own escalation policy.

Setup takes a few minutes on OpenNMS Meridian 2026, and the same plugin runs on Horizon 35 or later for community users. The full installation and configuration walkthrough, including filter examples and troubleshooting, lives in ilert's OpenNMS integration documentation.

Who benefits

Network operations teams get a dependable path from alarm to responder without building and maintaining their own notification scripts. On-call rotations, escalations, and acknowledgments are handled in one place.

Managed service providers can route alarms from different customer environments or node groups to different teams, each with its own escalation policy, while keeping OpenNMS as the single source of monitoring truth.

Teams consolidating their tooling gain a modern incident management layer on top of OpenNMS. ilert is hosted in Germany, GDPR compliant, and ISO 27001 certified, and it connects to the chat, ticketing, and collaboration tools teams already use. For organizations reconsidering their incident management platform, ilert also publishes migration guidance for teams moving off tools that are being retired.

For OpenNMS users, the partnership reflects a broader commitment: the platform should fit cleanly into the operational stack you already run, rather than asking you to work around it.

Get started

The integration is available today for OpenNMS Meridian 2026 and for Horizon 35 and later. The plugin is open source and published on GitHub.

Read the overview on ilert's OpenNMS integration page
Follow the step-by-step integration documentation to install and configure the plugin
New to ilert? Start a free trial directly from the integration page

If you are already running OpenNMS and want help planning the rollout, or you are evaluating OpenNMS for the first time, contact our team. We are glad to walk through how OpenNMS and ilert fit into your environment.

Jump to section

About the Author: Kyle Callahan

At OpenNMS, I focus on helping enterprise clients and strategic partners achieve success through effective network monitoring solutions. My role centers on understanding customer needs, fostering trust, and building long-term partnerships that deliver value. By guiding organizations through their monitoring journey and ensuring they have the right tools and support, I aim to create meaningful relationships that drive mutual growth and success.

Published On: November 5th, 2026Last Updated: November 5th, 20264 min read