Server Monitoring2 min read

    How to Monitor Docker Containers

    Share

    Overview

    Docker is an OS-level virtualization tool that delivers software in isolated packages called containers. Xitoring's Docker integration automatically detects and gathers useful data about your Docker containers, images, volumes, and networks — giving you full visibility into your containerized environments.

    What Can It Monitor?

    • Container Status — Running, stopped, paused, or restarting states for each container
    • CPU Usage — Per-container CPU utilization
    • Memory Usage — RAM consumption per container and overall
    • Network I/O — Bytes sent/received per container
    • Disk I/O — Read/write operations per container
    • Container Count — Total running, stopped, and paused containers
    • Images — Number of images and disk space used
    • Volumes — Volume count and usage statistics
    • Networks — Active Docker networks

    Prerequisites

    • Docker installed and running on your Linux server
    • Xitogent agent installed
    • No additional configuration or modules required

    How to Activate the Integration

    The Docker integration is the simplest to set up. Run the Xitogent CLI:

    xitogent integrate
    

    Select Docker from the list of available integrations. That's it — the connection between Xitogent and Docker is enabled immediately, and metrics start flowing to your dashboard.

    Setting Up Triggers

    You can create custom triggers to get alerted on container issues. Monitor parameters such as:

    • Container status changes (stopped/crashed)
    • CPU and memory usage per container
    • Network throughput anomalies
    • Disk I/O spikes

    Navigate to Triggers on your server page, select Docker, choose a metric, set your threshold, and configure notification channels.

    Tips

    • Docker integration requires zero configuration — just select it from the CLI
    • Monitor Container Status to catch crashed containers immediately
    • Track Memory Usage per container to prevent OOM kills
    • Use container-level CPU alerts to detect runaway processes
    • Currently supported on Linux servers