Product Guides
Infrastructure
Use Infrastructure to inspect host and container health when a service symptom may be caused by capacity or resource pressure.
Overview
Use Infrastructure when service symptoms may share host or container pressure. It helps separate one-service application behavior from broader resource pressure.
Use this page after you know the approximate symptom and need to decide which evidence should come next. Keep the service, environment, and time range consistent as you move from summary pages to request-level detail.
How to read this page
Use Hosts for machine-level pressure and Containers for workload-level pressure. Use topology when a resource relationship matters more than a single row. Return to Services or Runtime after identifying the affected resource.
- Shared pressure
- Several services degrading together can point to a shared host, container, or resource boundary.
- Topology
- Topology helps identify whether resources are related before comparing service symptoms.
- Service impact
- Infrastructure pressure matters most when it lines up with service latency, errors, or runtime changes.
Investigation workflow
Use this sequence when you need to move from a broad symptom to evidence you can share with another teammate.
- 1
Open Infrastructure when multiple services degrade in the same time window.
- 2
Check hosts, containers, and topology for sustained pressure.
- 3
Return to Services and Runtime to confirm which user-facing services were affected.
Interpretation note
Do not treat high resource use as bad without service impact. Do not compare hosts or containers outside the incident window. Do not stop at infrastructure. Confirm the affected service behavior.