WatchlogWatchlog
WATCHLOG INTEGRATION
D

Monitor Docker.

Monitor Docker container health, resource usage, restarts, network I/O, and lifecycle events across all your Docker hosts.

Start monitoring freeView documentation →
26 metrics·OOM + restart events·30s setup
WHAT WATCHLOG COLLECTS

Complete Docker observability.

The Watchlog Agent collects these metrics automatically once the Docker integration is enabled.

docker.containers.running
Running Containers
Number of containers in a running state
docker.containers.stopped
Stopped Containers
Containers that have exited or been stopped
container.cpu.percent
CPU Usage %
CPU utilization per container as percentage of host CPU
container.memory.usage
Memory Usage
Memory consumed by each container in bytes
container.memory.percent
Memory Limit %
Memory usage relative to the container memory limit
container.net.rx_bytes
Network Rx Bytes/sec
Data received over the container network interface
container.net.tx_bytes
Network Tx Bytes/sec
Data transmitted over the container network interface
container.blkio.read_bytes
Block IO Read/sec
Bytes read from disk by the container process
container.blkio.write_bytes
Block IO Write/sec
Bytes written to disk by the container process
container.restart_count
Restart Count
Total restarts since the container was created
container.oom_kill
OOM Kill Events
Times a container process was killed for exceeding memory limits
docker.images.count
Image Count
Total Docker images present on the host
LIVE DASHBOARD

Docker at a glance.

A pre-built Docker dashboard activates the moment you enable the integration — no configuration required.

● Docker Dashboard● Live
Running Containers
14
CPU (api-gateway)
34%
Mem (postgres)
1.8 GB / 2 GB
Restarts (1h)
2
OOM Kills (24h)
0
Net Rx/sec
24 MB/s
USE CASES

What engineers use Docker monitoring for.

⌇
Container resource profiling

See CPU and memory per container side by side. Identify resource hogs before they starve neighboring containers on the same host.

▣
Restart loop detection

Alert on containers exceeding a restart threshold in a time window — catch crash loops before they exhaust restart policies.

◈
OOM kill prevention

Monitor memory usage relative to container limits. Get warned before containers hit their ceiling and get killed by the kernel.

⊕
Docker Compose service monitoring

Group metrics by Compose service name. See which services in your stack are unhealthy without drilling into individual containers.

WHY WATCHLOG

Fewer blind spots. Earlier warnings.

Engineering teams that monitor Docker with Watchlog catch failure signals before they become incidents.

  • ✓See which containers are approaching their memory limit before OOM kills happen
  • ✓Alert on restart count spikes that indicate application crashes or bad deploys
  • ✓Track container CPU usage to rightsize resource limits in Docker Compose or K8s
  • ✓Monitor network I/O per container to detect unexpected traffic between services
  • ✓Know when a container has stopped before the service it powers becomes unavailable
QUICK SETUP

Docker monitoring in under 2 minutes.

No YAML. No config files. The Watchlog Agent detects Docker on your host and begins collecting immediately.

01
Install the Watchlog Agent

Deploy the agent on your Docker host. It connects to the Docker socket automatically.

02
Enable Docker integration

Open Watchlog → Integrations → Docker and click Enable. The agent requires read access to /var/run/docker.sock.

03
Container metrics in 60s

Per-container CPU, memory, network, and restart events appear in under one minute.

INSTALL WATCHLOG AGENT
sudo apiKey="$WATCHLOG_API_KEY" server="$WATCHLOG_SERVER" MEMORY="300M" bash -c "$(curl -L https://watchlog.io/ubuntu/watchlog-script.sh)

The agent automatically detects Docker running on your host and begins collecting metrics immediately.

GET STARTED

Start monitoring Docker now.

Full Docker visibility in under 2 minutes. No credit card required.

Start monitoring freeRequest demo →

Questions? Contact us at [email protected]