Docker events for real-time monitoring - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Real-time Docker event stream output

You run the command docker events --filter 'event=start' --filter 'container=myapp'. What output do you expect when the container myapp starts?

Docker

docker events --filter 'event=start' --filter 'container=myapp'

A A JSON line showing the start event for container 'myapp' with timestamp and container ID

B A list of all containers currently running, including 'myapp'

C An error message: 'unknown flag: --filter'

D No output until the container 'myapp' stops

💡 Hint

The command listens for events filtered by type and container name.

The 'docker events' command streams real-time events. Filtering by 'start' and container name shows start events only for that container.

🧠 Conceptual

intermediate

Purpose of Docker events in monitoring

What is the main purpose of using docker events in real-time monitoring?

A To build Docker images from a Dockerfile

B To get a live stream of Docker daemon events like container start, stop, and network changes

C To display the current resource usage of containers

D To list all Docker images available on the host

💡 Hint

Think about what 'events' means in system monitoring.

Docker events provide a live feed of actions happening in the Docker daemon, useful for monitoring container lifecycle and system changes.

❓ Troubleshoot

advanced

Troubleshooting missing Docker events output

You run docker events --filter 'event=stop' but see no output even after stopping containers. What is the most likely cause?

A The filter syntax is incorrect and causes the command to fail silently

B The Docker daemon is not running

C You are not running the command with sufficient permissions (not root or in docker group)

D Docker events only show start events, not stop events

💡 Hint

Consider user permissions for accessing Docker daemon events.

Accessing Docker events requires permissions. Without them, the command runs but shows no events.

🔀 Workflow

advanced

Using Docker events to trigger an alert

You want to trigger a script whenever any container stops. Which command pipeline correctly listens for stop events and runs alert.sh?

A docker ps -a --filter 'status=exited' | ./alert.sh

B docker events --filter 'event=stop' --format '{{.ID}}' > alert.sh

C docker logs --follow | grep 'stop' | ./alert.sh

D docker events --filter 'event=stop' | while read line; do ./alert.sh; done

💡 Hint

Think about streaming events and running a script on each event line.

The command streams stop events and pipes each line to a loop that runs the alert script.

✅ Best Practice

expert

Efficient filtering of Docker events for multiple event types

You want to monitor both container start and die events in real-time with minimal resource use. Which command is best?

A docker events --filter 'event=start' --filter 'event=die'

B docker events | grep -E 'start|die'

C docker events --filter 'event=start,die'

D docker events --filter 'event=start' && docker events --filter 'event=die'

💡 Hint

Check how multiple filters are combined in docker events.

Multiple --filter options combine with AND logic, but for event filters, Docker treats multiple event filters as OR, so specifying both filters separately is correct.