Virtualization Monitoring

Investigate a virtual machine in the context of its host.

Bring Proxmox, VMware and Hyper-V inventory and available performance measurements into the same operational view.

Virtualization monitoring for Philippine IT teams

Use the platform API and a Site Edge with approved access to your management network. Review the connection test and discovered resources before activating hosts or guests. Keep version, licensing, permissions and guest tools in the coverage review.

Proxmox monitoring

Review the Proxmox endpoint and read-only API access, then select the discovered resources you need. Compare available host, virtual machine and container observations. Allocated virtual disk capacity is not evidence of free space inside a guest.

VMware monitoring: ESXi and vCenter

Decide whether your collection source is an ESXi host or vCenter, and validate API access for that endpoint. Review discovered host and VM relationships with the measurements actually returned. An ESXi test does not certify every vCenter version or licensing combination.

Microsoft Hyper-V monitoring

Plan the supported Hyper-V access path from the assigned collector and review the required host permissions. Confirm that selected hosts and virtual machines supply current observations. Check guest-specific measurements separately; host inventory alone does not establish guest operating-system coverage.

The operational problem

A virtual machine warning can originate from a shared host or storage resource. Separate platform consoles make that relationship harder to investigate.

What you can monitor

Connect Proxmox, VMware and Hyper-V inventory with available host, VM, container and performance information.

What is included

  • Selected platform inventory and host-to-guest relationships.
  • Performance observations supplied by the connected platform API.
  • Virtualization reports and resource-specific investigation links.

Plan limits and optional services are shown on the pricing page.

Coverage and requirements

Platform APIs, permissions and licensing influence available data. Missing hardware sensors and guest filesystems are never filled with estimates.

A practical workflow

  1. Choose the platform and a collector with the necessary network access.
  2. Send its read-only credential through the encrypted setup flow.
  3. Review discovered hosts and guests with their reported capabilities.
  4. Compare the affected guest with its host before deciding the next action.

How to set it up

  1. Choose the platform endpoint and a Site Edge that can reach it.
  2. Use the encrypted credential setup flow with a read-only identity and validate TLS trust.
  3. Test discovery, review guests and required parents, then activate only the selected resources.
EXAMPLE DASHBOARD / REPORT REVIEW

Virtualization report: shared host investigation

Illustrative review of one guest and its parent host during an incident.

Guest
Read the affected guest’s available performance measurements.
Parent host
Compare host pressure and other observed workloads in the same period.
Evidence limits
Identify absent hardware or guest filesystem observations before making a capacity decision.

AOT-authored example of how to read the product. It contains no customer measurements or promised outcomes.

Reports for the decision

Virtualization and Infrastructure Health reports retain host-to-guest context and the selected timezone.

Explore report workflows →

Before you begin

Is VMware monitoring identical to Proxmox monitoring?

No. Each adapter uses its supported APIs and reports the measurements available from that platform.

How do I evaluate this product?

Create an evaluation workspace and connect one supported source. Your seven-day trial begins on the first successful telemetry, with no card required and no automatic charge.