Monitoring that sees the whole data centre
Nexus NMS unifies network, server, virtualization, cloud, application and facility power & cooling telemetry onto one operating spine — self-hosted, agent and agentless. Every engine proves itself on deploy with its own self-test, so “it’s monitoring” is something you can verify.
One spine, every layer
Network, server, virtualization and facility signal on a single path.
The capability map
Eighteen engines across one monitoring spine
Built in seven delivery waves — from discovery through facility capacity planning — each engine with a concrete self-test before it ships.
Discovery & Registration
Wave 1Network sweep and credentialed probe find and classify every device, host and cloud resource — no manual entry.
Unified Asset Inventory
Wave 1One canonical record per asset with site → rack → U-position and tenant, read by every other engine.
Collector & Polling
Wave 1Agent or agentless polling on a configurable interval, with health self-monitoring and per-target isolation.
Network Device Monitoring
Wave 2Interface utilization and errors, device health, NetFlow/sFlow/IPFIX top-talkers and wireless association.
Server & OS Monitoring
Wave 2CPU, memory, disk and process metrics from Windows and Linux — agent or agentless — with service state.
Virtualization & Cloud
Wave 2Hypervisor and guest-VM metrics plus cloud instance metrics, mapped back to host and account.
Environmental & Power
Wave 2PDU outlet power, UPS state and runtime, rack temperature and humidity on the same cadence as IT telemetry.
Topology & Dependency
Wave 3L2/L3 topology and service / power-chain dependency, with “what breaks if this fails” impact preview.
Dashboards, NOC & Rack
Wave 3Composable widgets, a NOC wall view and 2D rack elevations coloured by live asset status.
Threshold & Anomaly
Wave 4Static thresholds and learned rolling baselines, multi-condition rules and scheduled maintenance windows.
Alerting & Correlation
Wave 4Multi-channel notification, on-call escalation and root-alarm identification — one cause, one alert.
Application & Synthetic
Wave 5HTTP(S)/TCP/DNS and multi-step synthetic checks, uptime history and availability SLA computation.
Log Management
Wave 5Centralized ingestion, full-text search and time-correlation of logs against the metric / alert timeline.
Root-Cause Workspace
Wave 5One timeline of metrics, events and logs per incident, with security signal and resolution notes.
Remediation & Config
Wave 6Trigger-bound runbooks, network/device config backup and a full change audit trail with diffs.
Cooling & Capacity
Wave 6CRAC/CRAH monitoring, rack thermal maps and what-if capacity simulation before you commit space.
Reporting, SLA & Compliance
Wave 7Scheduled per-site / per-tenant reports, SLA computation and immutable, checksummed audit export.
API, RBAC & Multi-Tenant
Wave 7A versioned REST API over every engine, ITSM webhook connectors and tenant-scoped role-based access.
How signal flows
From first discovery to the right alert
Nothing is monitored until it is known. Nexus NMS discovers and registers every asset, attaches it to agent or agentless collection, then correlates, detects and alerts — so a single root cause produces one actionable alert, not fifty symptoms.
- Discover & register every device, host, VM and facility asset
- Collect on one cadence — IT and facility telemetry side by side
- Correlate into topology; detect on thresholds & learned baselines
- Alert, remediate with runbooks, then plan ahead on capacity
The operating spine
Ten stages, one path for every signal.
The power & cooling layer, on the same dashboard
Pure IT monitoring stops at the server. Nexus NMS keeps going — PDU outlet power, UPS state and runtime, rack temperature and humidity, and CRAC/CRAH status — so a temperature breach shows up next to a CPU spike, not in a separate tool. Remaining power, cooling and rack-space headroom per site is computed from live telemetry, with what-if simulation before you commit floor space.
- PDU / UPS power telemetry & power-chain mapping
- Rack thermal maps, CRAC/CRAH status & hot-spot detection
- Live power / cooling / space headroom & what-if capacity planning
Headroom per site
Illustrative — computed from live telemetry per rack and site
What makes Nexus NMS different
A monitoring platform that verifies itself
Monitoring you can’t trust is worse than none. Nexus NMS is built to a single doctrine: one testable unit per capability, a mandatory self-test on real inputs, and a build that refuses to ship if a test is red.
- Every engine carries a deterministic self-test — known input → expected result
- Real behaviour only — live collector data and real device/API paths, no mocks
- Whole-platform proof via
GET /api/platform/selftest - Green-or-it-doesn’t-ship — a red self-test blocks the build
Built in seven waves
Each wave ships its full interface — UI, CLI, API and docs — together.
Foundation
Discovery, inventory & the collection framework.
Core telemetry
Network, server, virtualization & facility collection.
Correlate & detect
Topology, dashboards, thresholds & alerting.
Automate & harden
Runbooks, capacity, reporting, RBAC & API.
Under the hood
Enterprise-grade, open foundations
Deploy your way
Runs where your estate lives
On-premises
Inside your data centre, next to the devices it polls.
Air-gapped
Offline installer — no internet required to stand up.
Docker
Bundled images, up in minutes with Compose.
Your cloud
AWS, Azure or GCP — deployed into your own account.
See Nexus NMS watching your estate
We’ll walk you through discovery, the facility layer and the self-test proof, then scope a deployment for your sites.