Why monitoring containers matters in Docker - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is monitoring container resource usage important?

Imagine you run many containers on a server. Why should you monitor their CPU and memory usage?

A To stop containers automatically when they use any CPU

B To detect if a container is using too many resources and might slow down others

C Because containers never use resources, so monitoring is not needed

D To increase the size of the container images

💡 Hint

Think about how one container using too much CPU affects others.

Monitoring resource usage helps keep containers from slowing down the whole system by using too much CPU or memory.

💻 Command Output

intermediate

What does this Docker stats command output show?

Run docker stats --no-stream on a server with two containers. What does the output tell you?

Docker

CONTAINER ID   NAME       CPU %     MEM USAGE / LIMIT     MEM %     NET I/O       BLOCK I/O     PIDS
abc123         webapp     5.23%     50MiB / 2GiB          2.44%     1.2MB / 1MB   0B / 0B       10
xyz789         db         80.00%    1.5GiB / 2GiB         75.00%    5MB / 3MB     10MB / 5MB    50

A The db container is using most CPU and memory, which might slow down the webapp container

B Both containers are using no resources

C The webapp container is using more CPU than the db container

D The output shows container logs

💡 Hint

Look at CPU % and MEM % columns to compare usage.

The db container uses 80% CPU and 75% memory, which is high. The webapp uses much less. This can cause performance issues.

🔀 Workflow

advanced

Which step is missing in this container monitoring setup?

You want to monitor container logs and resource usage continuously. You set up Prometheus to collect metrics but forget one important step. What is it?

A Building container images with Dockerfile

B Writing application code

C Running containers with <code>docker run</code>

D Installing and configuring exporters inside containers or on the host

💡 Hint

Prometheus needs data sources to collect metrics from.

Exporters provide metrics to Prometheus. Without them, Prometheus has no data to monitor.

❓ Troubleshoot

advanced

Why might container metrics stop updating in your monitoring dashboard?

Your monitoring dashboard shows container metrics but suddenly stops updating for one container. What could be a likely cause?

A You updated the container's environment variables

B The container image size increased

C The container crashed or stopped running

D You restarted the monitoring dashboard

💡 Hint

If a container is not running, can it send metrics?

If the container is stopped or crashed, it cannot provide metrics, so monitoring data stops updating.

✅ Best Practice

expert

What is the best practice for monitoring containers in a production environment?

Choose the best practice for effective container monitoring in production.

A Use centralized monitoring tools with alerting and log aggregation for all containers

B Manually check each container's logs daily

C Ignore monitoring because containers are isolated

D Only monitor containers when users report problems

💡 Hint

Think about automation and early problem detection.

Centralized monitoring with alerts and logs helps detect and fix issues quickly before users notice problems.