Server & OS Monitoring

Separate host pressure from guest workload problems.

Review resource observations supplied by supported hypervisor, SNMP and hardware sources. Guest filesystem coverage is explicit.

Server monitoring with clear source coverage

A Philippine office or data center may operate both physical servers and virtual guests. Choose the source that supplies the required measurements before setting thresholds. Keep hardware health, host resource pressure and guest observations separate when preparing a handover.

The operational problem

Host resource pressure and guest workload problems require different evidence. Disk allocation on a hypervisor cannot tell you the free space inside a virtual machine.

What you can monitor

Review CPU, memory, network and storage measurements from supported hypervisor or SNMP sources. Add Redfish for available physical server health.

What is included

  • Supported CPU, memory, network and storage observations.
  • Physical health readings when the hardware interface supplies them.
  • Asset history and capacity context without inventing guest filesystem data.

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

Coverage and requirements

Linux and Windows Site Edge packages are collectors. They do not imply a universal guest-agent integration for every operating system.

A practical workflow

  1. Select the supported source for the physical or virtual server.
  2. Connect its authorized Site Edge and read-only identity.
  3. Review resource measurements and separately confirm guest filesystem coverage.
  4. Investigate sustained pressure in the capacity view.

How to set it up

  1. Identify whether the evidence will come from a hypervisor, SNMP profile or Redfish controller.
  2. Connect that source through a Site Edge and select the server or guest to monitor.
  3. Confirm the metric names, units and timestamps before using thresholds or reports.
EXAMPLE DASHBOARD / REPORT REVIEW

Server review: host versus guest

Illustrative dashboard review of a guest reporting resource pressure.

Host resources
Check whether CPU or memory pressure affects the shared host.
Guest resources
Compare the guest observations with the host over the same period.
Storage evidence
Keep allocated capacity, datastore usage and reported guest free space separate.

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

Reports for the decision

Infrastructure and capacity reports preserve the distinction between host measurements and guest filesystem evidence.

Explore report workflows →

Before you begin

Will OpsAI show free space inside every VM?

Only when a supported guest source supplies that observation. Hypervisor allocation and guest free space stay separate.

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.