SSM Virtualization

VMware and Proxmox, on the same screen as your network.

Add vCenter or a Proxmox cluster once: hosts, virtual machines, LXC containers and datastores are discovered automatically and join the same inventory as your network devices. Nothing is installed in the VMs; add the Netronus Agent only to the VMs where you want more detail.

Request a demo See capabilities

Monitoring › Virtualization: hypervisors, clusters, hosts, VMs and the busiest virtual machines

The problem

What gets in the way today

Hypervisor here, network there

When a VM slows down, three different tools are opened to find out whether the host, the datastore or the network is to blame.

Forgotten snapshots and backups

Old snapshots fill datastores and failed backups go unnoticed.

An inventory that is always stale

When new and deleted VMs are added to monitoring by hand, the inventory never matches reality.

The solution

Agentless, automatic, connected

Netronus reads the hypervisor’s management API with a read-only account. New VMs appear on their own; deleted VMs are archived with their history kept. Because VM → host → datastore → LUN relationships are built, you can go from a VM’s page to the storage underneath it and on to the SAN port.

vCenter Server and standalone ESXi 6.7, 7.0, 8.0
Proxmox VE 7.x and 8.x, single node or cluster
VMware changes tracked every minute: new, deleted, power state, vMotion

End-to-end chain

Relationships are discovered automatically and shown on every asset page.

VM
Host
Datastore
LUN
Array
SAN port

End-to-end chain: virtual machines → datastore → LUN → pool → array → SAN switch port

Capabilities

What you get

Automatic discovery

Clusters, hosts, VMs, LXC containers and datastores enter the inventory on their own; browse them as vCenter › Datacenter › Cluster › Host › VM in the tree.

VM performance

CPU, CPU ready, memory, ballooning and swap, virtual disk read/write and latency, virtual NIC traffic.

Snapshots and backups

Snapshot count and age; backup jobs, replication and task history on Proxmox.

Cluster health

VMware HA/DRS state; Proxmox quorum and HA state.

Ceph and ZFS

Ceph (pools, OSDs, PG state), ZFS and LVM-thin usage on Proxmox storage.

Host details

Host sensor summary, connection and maintenance state; product, version and hardware.

Ready-made alarm templates

CPU ready, disk latency, snapshots older than 7 days, failed backups, HA errors, datastore usage, quorum loss, Ceph health and more.

Data coverage and agent upgrade

Every VM page shows what comes from the hypervisor and what from the guest tools; generate the agent install command with one click if needed.

Least privilege

A read-only role in vCenter and an auditor (PVEAuditor) API token in Proxmox are enough.

Screenshots

See it in the product

Virtual machine page: VM → host → vCenter → datastore chain and Data coverage

Technical summary

At a glance

Item	Detail
VMware	vCenter Server and ESXi 6.7, 7.0, 8.0 (vSphere Web Services API)
Proxmox	Proxmox VE 7.x, 8.x (REST API; API token recommended)
Installation	Agentless: a read-only account on the hypervisor, nothing installed in VMs
Discovery	Full discovery every 5 minutes; VMware changes every minute
Performance	One-minute collection
Relationships	VM → host → cluster, VM → datastore, datastore → LUN (by NAA ID or NFS path)
Deleted VMs	Archived; historical metrics are kept
In-guest detail	With the Netronus Agent, attached to the same asset by BIOS/VM UUID

Roadmap

Coming next

These items are planned and not part of the current release.

Roadmap Hyper-V and Nutanix support
Roadmap Kubernetes (node, pod, service) monitoring

See Netronus in your own environment

We will set up a demo on your network, show the screens with your own devices and prepare a quote for the modules you need.

Request a quote Request a demo