Infrastructure Monitoring for Cloud, Containers, and Hosts

What Infrastructure Monitoring helps you solve

Turn distributed resources into a connected, actionable infrastructure view

Guance uses DataKit, cloud integrations, and consistent tags to keep resource identity, performance, and dependencies connected. Teams can move from a fleet-wide anomaly to the affected host, container, process, or network path and verify the surrounding application impact.

01Unified resource inventoryExplore hosts, containers, processes, Kubernetes, networks, and cloud resources from one workspace.
02Capacity and performanceTrack CPU, memory, disk, filesystem, network, load, and container saturation over time.
03Topology and impactUse resource and network relationships to understand dependencies and the scope of an incident.
04Correlated contextConnect infrastructure metrics to logs, traces, events, alerts, and application services.

A real investigation path

From a resource anomaly to the affected service and infrastructure boundary

Start with the abnormal resource group, determine whether pressure is sustained, and use topology plus application context to identify the actual scope of impact.

Identify where the anomaly is concentrated

EvidenceResource type, environment, region, service, ownership, and current health

ConclusionReduce the incident from the entire estate to a specific workload or fleet

Data path

DataKit and cloud integrations → Resource inventory and metrics → Topology → Logs, traces, events, and alerts

Best for

For operations, SRE, platform, and cloud teams responsible for hosts, containers, Kubernetes, networks, and hybrid infrastructure.

Requirements

Collection and tags must preserve resource identity. Use APM for request-level code paths and RUM for real user impact.

View setup guide

Do not stop at resource metrics. Add logs, traces, events, and alerts

Keep infrastructure identity and time context attached as you move between metrics, logs, application traces, events, and alerts. This helps teams distinguish resource pressure from application regressions, deployment changes, and downstream failures.

View documentation

Do not stop at resource metrics. Add logs, traces, events, and alerts

Frequently asked questions

What is infrastructure monitoring?

Infrastructure monitoring continuously measures the health, performance, capacity, and availability of hosts, containers, processes, networks, Kubernetes, and cloud resources. Guance also connects these signals to application and log context for investigation.

Which infrastructure metrics should teams monitor?

Common signals include CPU, memory, disk and filesystem usage, network throughput and errors, system load, process health, container resource consumption, and cloud service metrics. The useful set depends on the workload and its service objectives.

How does infrastructure monitoring speed up troubleshooting?

It shows where an anomaly occurs, which resources and services depend on it, and what changed at the same time. Teams can then pivot to related logs, traces, events, and alerts instead of manually aligning several tools.

Who uses Guance Infrastructure Monitoring?

Operations, SRE, platform, cloud, and development teams use it to manage hybrid and multi-cloud estates, Kubernetes and container platforms, and business-critical hosts and services.

Explore more

Resources and further reading

Choose the next step from product documentation, related solutions, and technical guidance.

Monitor every host, container, process, network, and cloud resource in context