Alert setup for container health in Docker - Step-by-Step Execution

Process Flow - Alert setup for container health

Start Container

↓

Define Healthcheck

↓

Container Runs Healthcheck Command

↓

Healthcheck Result: Success or Failure

↓

Docker Updates Container Health Status

↓

Monitoring Tool Queries Health Status

↓

If Unhealthy -> Trigger Alert

↓

Notify User or System

↓

End

This flow shows how Docker runs health checks on containers, updates their status, and triggers alerts if unhealthy.

Execution Sample

Docker

docker run -d --name myapp \
  --health-cmd='curl -f http://localhost/ || exit 1' \
  --health-interval=30s \
  --health-retries=3 \
  myapp-image

# Monitor health status

docker inspect --format='{{.State.Health.Status}}' myapp

Runs a container with a health check command and inspects its health status.

Process Table

Step	Action	Healthcheck Command Result	Health Status	Alert Triggered
1	Container starts running	N/A	starting	No
2	Healthcheck runs first time	Success	healthy	No
3	Healthcheck runs second time	Success	healthy	No
4	Healthcheck runs third time	Failure	healthy	No
5	Healthcheck runs fourth time	Failure	healthy	No
6	Healthcheck runs fifth time	Failure	unhealthy	Yes - after 3 failures
7	Alert sent to user/system	N/A	unhealthy	Yes

💡 Alert triggered after 3 consecutive healthcheck failures, container marked unhealthy.

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
Health Status	starting	healthy	healthy	healthy	healthy	unhealthy	unhealthy
Failure Count	0	0	0	1	2	3	3
Alert Triggered	No	No	No	No	No	Yes	Yes

Key Moments - 2 Insights

Why does the alert only trigger after the third failure and not the first unhealthy status?

Because the healthcheck retries are set to 3, Docker waits for 3 consecutive failures before marking the container unhealthy and triggering the alert, as shown in rows 4-6 of the execution table.

What does the healthcheck command do in this setup?

It runs a simple curl command to check if the container's service is responding. Success means the service is healthy; failure means it is not, as seen in the 'Healthcheck Command Result' column.

Visual Quiz - 3 Questions

Look at the execution table, what is the health status after the second healthcheck run?

A starting

B unhealthy

C healthy

D unknown

💡 Hint

Check the 'Health Status' column at Step 3 in the execution table.

At which step is the alert first triggered according to the execution table?

A Step 6

B Step 4

C Step 2

D Step 7

💡 Hint

Look at the 'Alert Triggered' column and find the first 'Yes'.

If the health-retries were set to 1 instead of 3, when would the alert trigger?

A Never triggers

B After the first failure (Step 4)

C After the third failure (Step 6)

D At container start

💡 Hint

Refer to how failure count affects alert triggering in the variable_tracker.

Concept Snapshot

Docker container health alert setup:
- Use --health-cmd to define a test command
- Set --health-interval for check frequency
- Use --health-retries to allow failures before alert
- Docker marks container unhealthy after retries fail
- Monitoring tools query health status to trigger alerts

Full Transcript

This visual execution shows how Docker runs health checks on a container using a command like curl. The container starts with status 'starting'. Each health check runs periodically. Success results keep status 'healthy'. Failures increase a failure count. After 3 consecutive failures, Docker marks the container 'unhealthy' and triggers an alert. The alert notifies users or systems to take action. This process helps keep containers monitored and issues detected early.