Containers

Every container your telemetry names, wherever it runs.

1 min read Updated Oct 21, 2026 Sentinel Platform Team

infrastructurecontainersdockerkubernetes

How containers appear #

A container appears when a signal reports a container.name resource attribute. Containers are discovered from spans, logs and metrics together, so a container that only writes logs is still listed.

Identity #

Each container is identified by the host it runs on and its container name. That pair is what makes two containers with the same name on different hosts two different containers.

Container detail #

Image — the container image, when reported.
Orchestrator — Kubernetes when a pod name is present, otherwise Docker.
CPU and memory — averaged over the selected window.
Environment and service — where it runs and what it belongs to.
Host — the machine it runs on.
Running since — the first time it was seen in the window.

A container that is reporting is treated as running. A container that exits stops reporting and leaves the window.

Filtering #

The containers view can be narrowed by:

orchestrator
host
service
env
state

Finding a container #

Filter by service to see every container a service runs in.
Filter by host to see one machine's containers.
Filter by orchestrator to separate Kubernetes from Docker workloads.

A container with no CPU or memory figures has not reported the container metric families. Adding those metrics to your collector is what fills the two columns.

Onward #

A container belongs to a machine — Hosts — and, in a cluster, to a pod: Kubernetes. When you want the dependency view rather than the machine view, Network flows.