Infrastructure monitoring

Read the infrastructure as a connected system

CPU, memory, disk, load, and network signals are useful when compared with service state, agent freshness, and the asset's history. A reachable server can still have a failed application service; a slow website can be caused by more than host resource pressure.

Separate evidence from assumption

1. Select the correct workspace and server.
2. Check when the agent last reported and which metrics it supports.
3. Choose a time range that includes the reported change.
4. Compare related service and website checks.
5. Document unknown or missing coverage in the report.

The resource-signals guide gives a practical sequence for investigation.