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.

Practice

1. What is the primary purpose of the docker events command?

easy

A. To show real-time activity and changes in Docker objects

B. To list all Docker images available locally

C. To start a new Docker container

D. To remove unused Docker volumes

Solution

1. Step 1: Understand the command's function

   The docker events command streams live events related to Docker objects like containers, images, and networks.

2. Step 2: Compare with other Docker commands

   Commands like docker images, docker run, and docker volume prune serve different purposes unrelated to real-time event monitoring.

3. Final Answer:

   To show real-time activity and changes in Docker objects -> Option A

4. Quick Check:

   docker events = real-time Docker activity [OK]

Hint: Remember: events = live Docker activity stream [OK]

Common Mistakes:

• Confusing events with listing images
• Thinking it starts containers
• Assuming it cleans volumes

2. Which of the following is the correct syntax to show Docker events filtered by container ID abc123?

easy

A. docker events --filter container=abc123

B. docker events -c abc123

C. docker events --container abc123

D. docker events filter container abc123

Solution

1. Step 1: Recall Docker events filter syntax

   The correct filter syntax uses --filter key=value, so filtering by container ID is --filter container=abc123.

2. Step 2: Check other options for syntax errors

   Options B, C, and D use incorrect flags or missing dashes, making them invalid commands.

3. Final Answer:

   docker events --filter container=abc123 -> Option A

4. Quick Check:

   Filter syntax = --filter key=value [OK]

Hint: Use --filter key=value to filter events [OK]

Common Mistakes:

• Using short flags like -c which don't exist
• Omitting --filter or using wrong flag names
• Writing filter without dashes

3. What will be the output of the command docker events --filter event=start --filter container=mycontainer --since 10m?

medium

A. Shows all events for all containers in the last 10 minutes

B. Shows only start events for container 'mycontainer' from last 10 minutes

C. Shows stop events for container 'mycontainer' from last 10 minutes

D. Shows start events for all containers since 10 minutes ago

Solution

1. Step 1: Analyze the filters used

   The command filters events by event=start and container=mycontainer, so only start events for that container are shown.

2. Step 2: Understand the time filter

   The --since 10m option limits events to those in the last 10 minutes.

3. Final Answer:

   Shows only start events for container 'mycontainer' from last 10 minutes -> Option B

4. Quick Check:

   Filters combine to narrow events [OK]

Hint: Multiple --filter options combine to narrow events [OK]

Common Mistakes:

• Ignoring the container filter
• Confusing event=start with stop
• Misunderstanding --since time filter

4. You run docker events --filter event=stop --filter container=webapp but see no output even though the container stopped recently. What is the likely cause?

medium

A. The docker events command does not support filtering

B. The container never stopped

C. The container name is incorrect or misspelled

D. You need to add --since to see recent events

Solution

1. Step 1: Verify container name correctness

   If the container name is wrong or misspelled, no matching events will appear.

2. Step 2: Check command capabilities and event timing

   The docker events command supports filtering, and recent stop events should show without --since if they happened after the command started.

3. Final Answer:

   The container name is incorrect or misspelled -> Option C

4. Quick Check:

   Correct container name needed for filtering [OK]

Hint: Check container name spelling when no events appear [OK]

Common Mistakes:

• Assuming filtering is unsupported
• Forgetting container names are case-sensitive
• Thinking --since is always required

5. You want to monitor Docker events for container dbserver and automatically trigger a script when it stops. Which command correctly streams only stop events for that container?

hard

A. docker events --container=dbserver --event=stop

B. docker events --filter event=stop --container dbserver

C. docker events --filter stop --filter container=dbserver

D. docker events --filter container=dbserver --filter event=stop

Solution

1. Step 1: Use correct filter syntax for container and event

   The correct syntax uses --filter key=value. So --filter container=dbserver and --filter event=stop are valid.

2. Step 2: Identify invalid options

   Options B, C, and D use incorrect flags like --container or missing event= format, which are invalid.

3. Final Answer:

   docker events --filter container=dbserver --filter event=stop -> Option D

4. Quick Check:

   Use --filter key=value for all filters [OK]

Hint: Always use --filter key=value for event and container filters [OK]

Common Mistakes:

• Using --container or --event flags incorrectly
• Omitting 'event=' or 'container=' in filters
• Mixing filter syntax with invalid flags