Alert setup for container health in Docker - Time & Space Complexity

Time Complexity: Alert setup for container health

O(n)

Understanding Time Complexity

We want to understand how the time to check container health and trigger alerts changes as the number of containers grows.

How does adding more containers affect the alert system's work?

Scenario Under Consideration

Analyze the time complexity of the following Docker health check and alert setup snippet.

HEALTHCHECK --interval=30s --timeout=5s --start-period=5s --retries=3 \
  CMD curl -f http://localhost/health || exit 1

# Pseudo alert script
while true; do
  for container in $(docker ps -q); do
    status=$(docker inspect --format='{{.State.Health.Status}}' $container)
    if [ "$status" != "healthy" ]; then
      echo "Alert: Container $container is $status"
    fi
  done
  sleep 30
 done
    

This code sets a health check for each container and runs a loop to check all containers' health status every 30 seconds, alerting if any are unhealthy.

Identify Repeating Operations

Look for repeated actions in the alert checking process.

• Primary operation: Looping through all running containers to check health status.
• How many times: Once every 30 seconds, checking each container once per loop.

How Execution Grows With Input

As the number of containers increases, the alert script checks more containers each cycle.

Input Size (n)	Approx. Operations per 30s
10 containers	10 health status checks
100 containers	100 health status checks
1000 containers	1000 health status checks

Pattern observation: The number of health checks grows directly with the number of containers.

Final Time Complexity

Time Complexity: O(n)

This means the time to check and alert grows linearly as you add more containers.

Common Mistake

[X] Wrong: "Checking container health is constant time no matter how many containers run."

[OK] Correct: Each container must be checked individually, so more containers mean more checks and more time.

Interview Connect

Understanding how monitoring scales with system size is key to building reliable alerting systems in real projects.

Self-Check

"What if the alert script checked only containers that recently changed status? How would the time complexity change?"