Docker Integration
Container-level CPU, memory, network, and log monitoring with automatic service discovery. One docker run command — full visibility into every container on your host within seconds.
How It Works
Run the TigerOps Container
Launch the TigerOps agent as a privileged container with access to the Docker socket. A single docker run command — no host-level installation needed.
Auto-Discover All Containers
TigerOps reads the Docker socket and instantly discovers every running container, including its image, name, labels, environment, and compose project.
Metrics & Logs Stream In
CPU throttling, memory usage, OOMKill events, network I/O, block I/O, and stdout/stderr logs for every container begin flowing to TigerOps within seconds.
AI Detects Anomalies
The AI SRE tracks per-container baselines and fires incidents for memory leaks, sustained CPU spikes, container crashes, and unhealthy healthcheck states.
What You Get Out of the Box
Per-Container Resource Metrics
CPU usage per core, memory utilization and limits, network receive/transmit bytes, and block I/O reads/writes — all per container, per second.
Docker Compose Awareness
Automatically groups containers by docker-compose project, service name, and stack for easy filtering and aggregate dashboards.
Container Log Tailing
Tails stdout and stderr from all containers in real time, enriching each log line with container name, image, and compose service metadata.
Healthcheck State Monitoring
Tracks Docker healthcheck pass/fail state and fires alerts when containers become unhealthy — before they are terminated and restarted.
OOMKill Detection
Captures OOMKill events from the Linux kernel cgroup subsystem and correlates them with memory trend data and recent image changes.
Image & Registry Visibility
Track which image versions are running across your fleet, detect when containers drift from expected tags, and monitor image pull errors.
Docker Compose Setup
Add TigerOps to your existing docker-compose.yml or run it standalone.
# Add this service to your existing docker-compose.yml
services:
tigerops-agent:
image: tigerops/agent:latest
container_name: tigerops-agent
restart: unless-stopped
environment:
- TIGEROPS_API_KEY=${TIGEROPS_API_KEY}
- TIGEROPS_SITE=us1.tigerops.io
- TIGEROPS_LOGS_ENABLED=true
- TIGEROPS_APM_ENABLED=true
# Name your environment for filtering
- TIGEROPS_ENV=production
- TIGEROPS_HOSTNAME=${HOSTNAME}
volumes:
# Docker socket for container discovery
- /var/run/docker.sock:/var/run/docker.sock:ro
# Host proc for system metrics
- /proc:/host/proc:ro
- /sys:/host/sys:ro
# Container logs
- /var/lib/docker/containers:/var/lib/docker/containers:ro
pid: host
security_opt:
- apparmor:unconfined
# Or run standalone with docker run:
# docker run -d --name tigerops-agent \
# -e TIGEROPS_API_KEY=<YOUR_KEY> \
# -v /var/run/docker.sock:/var/run/docker.sock:ro \
# -v /proc:/host/proc:ro \
# tigerops/agent:latestCommon Questions
Does TigerOps require privileged mode for Docker monitoring?
TigerOps needs access to the Docker socket (/var/run/docker.sock) to discover containers and collect stats. The agent container itself does not need to run in full privileged mode — CAP_SYS_PTRACE and read access to the socket is sufficient for most metrics. Log collection may require additional volume mounts.
Does TigerOps support Docker Swarm?
Yes. TigerOps auto-discovers Swarm services, tasks, and node membership. Metrics are grouped by service name and stack, giving you aggregate views across replicated services without per-container configuration.
Can I filter which containers TigerOps monitors?
Yes. You can include or exclude containers using Docker label selectors in the TigerOps agent configuration. This is useful for excluding infrastructure containers (like the TigerOps agent itself) or focusing on specific compose projects.
How does Docker log collection compare to a log shipper like Fluentd?
TigerOps log collection from Docker is zero-configuration and enriches logs with container metadata automatically. For large-scale log pipelines where you need log routing, transformation, or multi-destination forwarding, using Fluentd or Fluent Bit to forward to TigerOps is also supported.
Does TigerOps work on Docker Desktop for local development?
Yes. Docker Desktop on macOS and Windows exposes the Docker socket and TigerOps works with it. This is useful for local debugging, but TigerOps is primarily designed for production Linux Docker environments.
Full Docker Visibility in Seconds
No credit card required. One command. No host-level install.