If your organisation runs SolarWinds, Nagios, Zabbix, or Zenoss, you've made smart, proven choices in monitoring infrastructure. These are tools your teams know well, with years of tuning, templates, and configuration behind them.
The gap isn't in the monitoring. It's in what happens after the alerts fire.
"Every monitoring tool generates alerts in its own language, in its own console. Cross-system correlation requires a layer above them all — one that speaks every dialect simultaneously."
RightITnow ECM is that layer. It connects natively to SolarWinds, Nagios, Zabbix, and Zenoss via pre-built connectors — ingesting alerts from all of them into a single correlation engine. Your tools keep running exactly as they are. ECM adds the intelligence on top.
One engine. Four native connectors. One unified NOC view.
ECM doesn't ask you to rip and replace. It sits above your existing tools, connects to each via a pre-built native connector, and starts correlating alerts across all of them — in hours, not months.
SolarWinds
NPM, SAM, NCM, and the Orion/Observability platform. Network and infrastructure alerts flow into ECM automatically.
Nagios
Core and XI. Consolidates multiple Nagios instances into one correlated view — eliminating alert floods and manual cross-instance checking.
Zabbix
Open source and Cloud. Replaces scripted trigger dependencies with ECM's visual correlation rule builder across your full stack.
Zenoss
Service Dynamics and Core. Zenoss hybrid IT events correlate with every other source in your stack — giving your NOC full context, not just Zenoss-visible scope.
What your stack can do with ECM — versus without it.
| Capability | With ECM | Tools alone |
|---|---|---|
| Cross-tool alert correlation | ✓ Automatic | ✗ Manual |
| Unified NOC console | ✓ One view | ✗ 4 separate consoles |
| Alert deduplication across tools | ✓ Automatic | ✗ Duplicate noise |
| Bi-directional ITSM lifecycle | ✓ End-to-end | ✗ Notifications only |
| Root cause across domains | ✓ Topology-aware | ✗ Per-tool scope only |
| Existing tools replaced? | ✓ None — all stay | n/a |
Three outcomes teams see within the first week.
Alert noise drops immediately.
When a single infrastructure event triggers alerts in SolarWinds, Nagios, and Zabbix simultaneously, ECM deduplicates them into one correlated incident. NOC teams consistently report event volume dropping dramatically within days — before any custom configuration has even been applied.
Chronic issues hidden by tool silos become visible.
Recurring problems that are split across monitoring domains — a network fault visible in SolarWinds, a downstream application symptom in Zenoss — can go unconnected for months. Cross-system correlation makes the relationship obvious the moment both alerts fire.
Incidents open, route, and close without manual intervention.
ECM's bidirectional ITSM integration means the full incident lifecycle — creation, routing, acknowledgement, and closure — runs automatically. When the underlying issue clears across all correlated sources, the ticket closes. No chasing. No stale incidents.
What operations teams say after connecting ECM.
"Chronic issues that had been long masked became obvious within days, allowing us to dramatically cut down our event volume — before we'd even trained our team."
IT Operations Director — Financial Services"Our NOC now only watches ECM. Response times improved. We unified our workflow across technology areas and reduced administrative overhead significantly."
Global Infrastructure Operations"We deployed a central event processing console against our existing legacy systems in record time. RightITnow provided a simple, cost-effective licensing model."
Enterprise IT Operations Team