Container metrics collection in Docker - Commands & Configuration

Introduction

When you run containers, you want to know how much CPU, memory, and other resources they use. Container metrics collection helps you see this information so you can keep your apps healthy and fix problems quickly.

When you want to check if a container is using too much memory and might crash.

When you need to monitor CPU usage of your app containers to avoid slowdowns.

When you want to track network traffic inside containers to detect unusual activity.

When you want to collect data to improve your app's performance over time.

When you want to see resource usage before scaling your containers up or down.

Commands

This command shows the current CPU, memory, and network usage of all running containers once. It helps you get a quick snapshot of resource use.

Terminal

docker stats --no-stream

Expected Output

CONTAINER ID   NAME          CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS

b1c3f2a4d5e6   my-app        0.15%     50MiB / 1GiB          4.88%     1.2MB / 1.1MB     0B / 0B           5

→

--no-stream - Show metrics only once instead of continuously updating

This command continuously shows live metrics for all running containers. It updates every second so you can watch resource use over time.

Terminal

docker stats

Expected Output

CONTAINER ID   NAME          CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS

b1c3f2a4d5e6   my-app        0.20%     52MiB / 1GiB          5.07%     1.3MB / 1.1MB     0B / 0B           5

b1c3f2a4d5e6   my-app        0.18%     51MiB / 1GiB          4.98%     1.3MB / 1.1MB     0B / 0B           5

This command shows CPU and memory usage for the container named 'my-app' once, using a simple custom format for easier reading.

Terminal

docker stats my-app --no-stream --format "{{.Name}}: CPU {{.CPUPerc}}, MEM {{.MemUsage}}"

Expected Output

my-app: CPU 0.15%, MEM 50MiB / 1GiB

→

--format - Customize the output format for easier reading

Key Concept

If you remember nothing else from this pattern, remember: docker stats shows real-time resource use of containers to help you monitor their health.

Common Mistakes

Running 'docker stats' without specifying --no-stream when you only want a snapshot.

The command will keep running and updating, which can be confusing if you only want one result.

Add the --no-stream flag to get a single snapshot of container metrics.

Trying to get metrics for a container that is not running.

Docker stats only works for running containers and will show no output or an error.

Make sure the container is running before using docker stats.

Not using --format to simplify output when scripting or automating monitoring.

Raw output can be hard to parse and use in scripts.

Use the --format flag to get only the needed fields in a clean format.

Summary

Use 'docker stats --no-stream' to get a one-time snapshot of container resource usage.

Use 'docker stats' to watch live, updating metrics for all running containers.

Use '--format' to customize the output for easier reading or automation.

Practice

1. What does the docker stats command primarily show?

easy

A. Logs of a specific container

B. List of all Docker images on the system

C. Live resource usage metrics of running containers

D. Docker daemon configuration settings

Solution

1. Step 1: Understand the purpose of docker stats

   This command is designed to display live resource usage statistics such as CPU, memory, and network for running containers.

2. Step 2: Differentiate from other Docker commands

   Other commands like docker images list images, docker logs show logs, and docker info shows daemon info, so they do not match the description.

3. Final Answer:

   Live resource usage metrics of running containers -> Option C

4. Quick Check:

   docker stats = live container metrics [OK]

Hint: Remember: stats = live resource usage [OK]

Common Mistakes:

• Confusing stats with logs
• Thinking stats shows images
• Assuming stats shows config

2. Which of the following is the correct syntax to get a single snapshot of container metrics without continuous updates?

easy

A. docker stats --no-stream

B. docker stats --single

C. docker stats --once

D. docker stats --snapshot

Solution

1. Step 1: Identify the flag for single snapshot

   The --no-stream flag tells docker stats to show metrics once and exit instead of streaming live updates.

2. Step 2: Verify other options

   Flags like --single, --once, and --snapshot are not valid Docker flags for this command.

3. Final Answer:

   docker stats --no-stream -> Option A

4. Quick Check:

   Single snapshot flag = --no-stream [OK]

Hint: Use --no-stream for one-time metrics [OK]

Common Mistakes:

• Using invalid flags like --single
• Omitting the flag and expecting single output
• Confusing with other Docker commands

3. What will be the output of the command docker stats --no-stream my_container if my_container is running?

medium

A. A continuous live stream of resource usage for all containers

B. Logs of my_container

C. An error saying container not found

D. A single snapshot of resource usage metrics for my_container

Solution

1. Step 1: Understand the command components

   docker stats --no-stream requests a single snapshot, and specifying my_container limits output to that container only.

2. Step 2: Predict the output

   Since my_container is running, the command outputs one snapshot of its resource usage metrics, not a stream or logs.

3. Final Answer:

   A single snapshot of resource usage metrics for my_container -> Option D

4. Quick Check:

   --no-stream + container name = single snapshot for that container [OK]

Hint: Add container name for focused single snapshot [OK]

Common Mistakes:

• Expecting continuous stream despite --no-stream
• Confusing stats output with logs
• Assuming error if container is running

4. You run docker stats --no-stream my_container but get an error: Error: No such container: my_container. What is the most likely cause?

medium

A. You need to add --all flag to see stopped containers

B. The container my_container is not running or does not exist

C. Docker daemon is not running

D. The --no-stream flag is invalid

Solution

1. Step 1: Analyze the error message

   The error clearly states the container my_container cannot be found, meaning it is either stopped or never created.

2. Step 2: Check other options

   The --no-stream flag is valid, Docker daemon errors would be different, and docker stats does not support --all to show stopped containers.

3. Final Answer:

   The container my_container is not running or does not exist -> Option B

4. Quick Check:

   Error 'No such container' means container missing [OK]

Hint: Check container existence before stats command [OK]

Common Mistakes:

• Assuming flag is wrong
• Thinking Docker daemon is down
• Trying unsupported flags like --all

5. You want to monitor CPU and memory usage of two specific containers named webapp and db with a single snapshot. Which command should you run?

hard

A. docker stats --no-stream webapp db

B. docker stats webapp db --no-stream

C. docker stats --no-stream --filter webapp --filter db

D. docker stats --filter name=webapp,db --no-stream

Solution

1. Step 1: Understand how to specify multiple containers

   Docker stats accepts container names as arguments separated by spaces to monitor multiple containers.

2. Step 2: Use the correct flag placement

   The --no-stream flag should come before container names; docker stats --no-stream webapp db places it correctly.

3. Step 3: Evaluate other options

   docker stats webapp db --no-stream incorrectly places the flag after container names, causing Docker to interpret --no-stream as a container name and resulting in an error. Options C and D use invalid or unsupported --filter syntax for this command.

4. Final Answer:

   docker stats --no-stream webapp db -> Option A

5. Quick Check:

   Multiple containers + --no-stream = docker stats --no-stream webapp db [OK]

Hint: List containers after --no-stream for snapshot [OK]

Common Mistakes:

• Using invalid --filter syntax
• Placing flags after container names incorrectly
• Trying to monitor stopped containers