Zenoss monitors your hybrid infrastructure. ECM correlates it with everything else.
RightITnow ECM includes a native Zenoss connector. Zenoss alerts flow directly into ECM's correlation engine — alongside SolarWinds, Nagios, Zabbix, SCOM, and CloudWatch — giving your NOC one unified, actionable view across your entire monitoring estate.
ECM connects to Zenoss — and goes beyond it
RightITnow ECM doesn't replace Zenoss. It connects to it — pulling its alerts into a unified correlation engine alongside every other tool in your stack.
Native Zenoss connector included
ECM's native Zenoss connector ingests events and alerts from Zenoss Service Dynamics and Zenoss Core directly into ECM's correlation engine. Zenoss continues to provide its hybrid IT monitoring capabilities. ECM adds the cross-system intelligence layer — correlating Zenoss events with alerts from SolarWinds, Nagios, Zabbix, SCOM, IBM Netcool, VMware, and more in a single unified NOC console.
What Zenoss alone can't do
Even if you're happy with Zenoss as a monitoring tool, these are the gaps that ECM is specifically built to fill.
Zenoss monitors its domain — it doesn't correlate across all your tools
Zenoss provides strong hybrid IT monitoring visibility, but its event correlation is limited to what Zenoss itself monitors. ECM ingests Zenoss events and correlates them with alerts from SolarWinds, Nagios, Zabbix, and SCOM — connecting the dots your NOC currently draws manually.
No published pricing — every deal requires a sales engagement
Zenoss does not publish pricing on its website. IT buyers must enter a full sales process to understand costs, making budget planning and competitive evaluation more time-consuming than necessary.
Resource-intensive to deploy and maintain at enterprise scale
Zenoss is well-suited for large enterprises with dedicated teams, but deployment and ongoing maintenance require significant expertise. Adding ECM on top of an existing Zenoss investment adds value without adding deployment complexity.
Event-to-incident automation requires additional configuration
Zenoss can integrate with ITSM tools, but a fully automated, bidirectional incident lifecycle — automatic creation, routing, acknowledgement, and closure — requires ECM as the orchestration layer sitting above Zenoss.
Zenoss was acquired — roadmap and support trajectory uncertain
Zenoss was acquired and has changed strategic direction, raising questions about long-term product investment. Adding ECM as the cross-system correlation layer provides a stable, independent foundation regardless of what happens to individual monitoring vendors.
Zenoss alerts lack context from your other monitoring tools
A Zenoss event for a failing device may have upstream or downstream context visible only in SolarWinds or Nagios. Without ECM's cross-source correlation, NOC teams make decisions with incomplete information — slowing MTTR.
RightITnow ECM + Zenoss vs. Zenoss alone
This isn't about replacing Zenoss — it's about what you gain when ECM sits on top of it.
| Capability | ECM + Zenoss | Zenoss alone |
|---|---|---|
| Cross-system event correlation | ✓ Zenoss + SolarWinds + Nagios + Zabbix + more | ✗ Zenoss-monitored sources only |
| Native Zenoss connector | ✓ Yes — alerts ingest automatically | n/a |
| Bi-directional ITSM integration | ✓ Auto create, route, acknowledge, close | Requires additional configuration |
| NOC single pane of glass | ✓ All tools in one console | ✗ Zenoss console only |
| Automated deduplication | ✓ Across all connected sources | Within Zenoss only |
| Pricing transparency | ✓ Clear ECM licensing | ✗ No published pricing |
| Cross-domain root cause | ✓ Topology-aware across all tools | ✗ Limited to Zenoss-visible scope |
| Vendor stability | ✓ Independent, focused roadmap | ✗ Post-acquisition uncertainty |
What teams say after adding ECM
Real results from organizations that added RightITnow ECM as their cross-system correlation layer.
"We deployed a central event processing console against our existing legacy systems in record time. RightITnow provided a simple, cost-effective licensing model."
"Our NOC now only watches ECM, which has improved response times. We've unified our workflow across technology areas, which reduced administrative overhead."
"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."
Connect Zenoss to ECM in hours
The native connector is pre-built. Getting Zenoss alerts flowing into ECM takes hours, not weeks.
Connect the Zenoss connector
ECM's native Zenoss connector is pre-built for Zenoss Service Dynamics and Zenoss Core. Point it at your Zenoss instance and events start flowing into ECM immediately.
Add your other monitoring tools
Connect SolarWinds, Nagios, Zabbix, SCOM, VMware, CloudWatch, and more. Each tool's alerts feed into the same ECM correlation engine alongside Zenoss.
Configure cross-system correlation rules
Use ECM's visual drag-and-drop interface to define deduplication, suppression, and cross-domain correlation rules across Zenoss and all your other tools.
Automate the incident lifecycle
ECM automatically creates, routes, acknowledges, and closes incidents in your Service Desk — bidirectionally — when correlated events clear across all sources including Zenoss.
Frequently asked questions
Ready to get more out of Zenoss?
See how RightITnow ECM connects to Zenoss and correlates its alerts across your entire monitoring stack — in a single unified NOC console.
Book a live demo