Docker Container Monitoring
Axibase Time Series Database (ATSD) allows IT operations teams to monitor Linux containers in concert with existing management systems.
ATSD continuously collects availability status, performance metrics and detailed configurations from containers in a single repository and exposes the data to upstream tools (CMDB, monitoring, alerting, event management) via the API, notifications, and scheduled reporting. It provides operations teams the necessary visibility, control, and automation into Linux containers while delivering a unified view of container performance to development and QA teams.
The data is collected by Axibase Collector instances installed locally on each Docker host.
- Seamlessly collect detailed configurations and statistics at the host, container, volume, and network level from multiple Docker hosts.
- Analyze incoming data with the built-in rule engine and escalate actionable data to upstream alerting and monitoring systems.
- Automatically compose application and service dashboards using image and container-labels for filtering and roll-ups.
- Provide development and operations teams a search interface to quickly locate resources as the environment grows in size and scope.
- Distribute scheduled reports on historical and estimated host and container utilization to prevent performance bottlenecks.
Linux Container Monitoring
- Collect CPU, memory, I/O, volume, and network statistics from Docker hosts and containers.
- Correlate container utilization with OS-level usage for triage and diagnostics.
- Instantly visualize data with built-in, real-time host and container dashboards.
- Automatically build service dashboards using image and container labels.
- Perform detailed inventory scans of the Docker environment including hosts, images, containers, volumes, and networks.
- Notify applications and operations teams in case of container misplacement.
- Enforce labeling standards to ensure CMDB accuracy.
Compliance and Security
- Intercept and react to life-cycle events such as new image pulls, container starts, container command executions.
- Identify images and containers that violate pre-approved black-lists and white-lists.
- Perform enterprise-wide inventory queries to identify configuration abnormalities.
- Scan launch parameters and variables to ensure secrets and credentials are protected.
For installation on Kubernetes refer to this Kubernetes Installation Guide.
Start ATSD container on one of the Docker hosts.
password variables with custom credentials. These credentials are used by collectors to insert data into ATSD.
Minimum password length is 6 characters.
$ docker run -d --name=atsd -p 8443:8443 -p 8081:8081 \ --env COLLECTOR_USER_NAME=username \ --env COLLECTOR_USER_PASSWORD=password \ --env COLLECTOR_USER_TYPE=api-rw \ axibase/atsd:latest
Wait for the database to initialize.
docker logs -f atsd
[ATSD] ATSD user interface: [ATSD] http://172.17.0.2:8088 [ATSD] https://172.17.0.2:8443 [ATSD] ATSD start completed. Time: 2017-09-26 15-12-10. [ATSD] Collector account 'collector' created. Type: 'writer'.
Launch Axibase Collectors
Launch an Axibase Collector instance on each Docker host.
collector variables with collector credentials specified above.
atsd_hostname variable with the hostname of the Docker host where ATSD container is running.
The hostname must be resolvable from the Docker host where collector is installed.
$ docker run -d --name axibase-collector \ --volume /var/run/docker.sock:/var/run/docker.sock \ --env=DOCKER_HOSTNAME=`hostname -f` \ axibase/collector \ -atsd-url=https://collector:collector@atsd_hostname:8443 \ -job-enable=docker-socket
Wait for the collector to initialize.
docker logs -f axibase-collector
... [Collector] Waiting for Collector to bind to port 9443 ...( 6 of 30 ) [Collector] Collector web interface: [Collector] https://172.17.0.3:9443 [Collector] https://127.0.0.1:9443 [Collector] Collector start completed.
Log in to the ATSD web interface at
Create a built-in administrator account.
Open Entities > Docker Hosts and Entities > Docker Containers tabs and verify that records are available as displayed on the below screenshots.
Open Configuration > Rules and import alerting rules into the rule engine.
Full-text Series Metadata Search
Docker inspect files
Environment Settings and Versions
Custom Composite Summary
Performance, availability and configuration rules
Messages and Events