Infrastructure

Infrastructure monitoring starts with the Host Agent. Install it once per machine and it reports CPU, memory, disk and network for the host, every process the OS is running, and every container on that box, with no extra config per service. On Kubernetes the same agent runs as a DaemonSet and walks the cluster for you: nodes, namespaces, workloads and pods show up already linked to the containers underneath them. On ECS it rides along as a sidecar in the task definition, on EC2 or Fargate, and pulls task and container metrics from the ECS metadata endpoint. The hierarchy comes from where the agent is running, not from you tagging hosts to clusters by hand.

Features

Related Features

What did you think of this content?