Virtualization & Cloud
Add a hypervisor or a cloud account once. TechSavve finds every host, virtual machine and instance on it, monitors them and documents them.
Add the platform once. Get the whole estate.
Add a vCenter, an ESXi host, a Hyper-V host or System Center Virtual Machine Manager, a Proxmox VE cluster or a KVM host, and the site collector reads everything on it. You do not add hosts or virtual machines one by one, and nothing is installed on them.
- Hosts with their hardware, clusters with HA, DRS and EVC, virtual machines, datastores and storage
- Standard and distributed switches with their VLANs, and the addresses each guest reports
- Snapshots, VMware Tools and vCenter’s own alarms
- Read again every 15 minutes, or as often as you set
Hypervisors TechSavve reads
VMware vCenter and ESXi
A whole vCenter, or a standalone ESXi host, read through the vSphere API with a read-only account.
Microsoft Hyper-V and SCVMM
A Hyper-V host over WinRM, or everything System Center Virtual Machine Manager manages.
Proxmox VE and KVM
Proxmox VE through its API with a read-only token, and KVM / libvirt hosts over SSH.
Hosts and VMs become monitored devices
Found, not typed in
Hosts and every running virtual machine become devices automatically. A machine you already monitor is matched by its address or name instead of being added twice. You can switch either off for each account.
Down means down
A virtual machine that is powered off or suspended shows as down at once. One that is removed from the hypervisor is retired a day later, and one you delete stays deleted.
Calm first day
New devices get a 24-hour learning period before they can open incidents. Each VM is linked to the host it runs on, so a host failure is one incident, not one per VM.
Documented for you
VLANs from the port groups, subnets and IP addresses from what the guests report, datastores as storage assets, and which VM runs on which host and uses which datastore go straight into IPAM, Inventory and the service map. Anything you have documented by hand is never overwritten, and an entry you delete stays deleted.
Warnings and capacity forecasts
Health findings
Datastores running out of space, snapshots left behind for months, vCenter alarms, hosts reporting hardware problems, clusters running without HA or DRS, and VMs running without VMware Tools.
Capacity running out
TechSavve keeps a daily history of datastore space and of each cluster’s CPU and memory, and from about a week of it forecasts when each will run out.
Respects your windows
Maintenance windows hold findings back during planned work, just like every other alert.
Cloud platforms
Connect an account with read-only credentials. TechSavve reads it directly from the platform, with no collector needed, and keeps it current.
AWS and Microsoft Azure
Regions and zones, instances, disks, databases and load balancers. Instances become monitored devices, with CPU from CloudWatch on AWS, and CloudWatch alarms, Azure resource health and Azure Monitor metrics are available as monitors.
Google Cloud, Oracle Cloud, IBM Cloud and Vultr
Regions, zones and virtual machines, which become monitored devices just like AWS and Azure instances.
Vercel and Supabase
Vercel projects and domains, and Supabase projects and their databases.
Secrets stay out
Read-only access is all TechSavve asks for, credentials are encrypted, and passwords or environment variables a provider returns are never stored.
See TechSavve RMM in action
Book a free demo with the DFWTechPros team.