If you like or use this project, please provide feedback to author - Star it ★.

Start one container and monitor all Docker containers on your Docker host. Zabbix Docker monitoring is used - all docker module container metrics are available except docker.xnet. Custom template Zabbix Agent XXL is provided as well. Zabbix agent stress testing is supported as well. Quick start:

docker run \
  --name=zabbix-agent-xxl \
  -h $(hostname) \
  -p 10050:10050 \
  -v /:/rootfs \
  -e "ZA_Server=<ZABBIX SERVER IP/DNS NAME>" \
  -d monitoringartist/zabbix-agent-xxl-limited:latest

Ubuntu/Debian users need also -v /var/run:/var/run.

Tested on CoreOS, RHEL, CentOS, Ubuntu, Debian, Boot2docker, Photon OS.

Please donate to author, so he can continue to publish other awesome projects for free:

Subcribe for Paid Zabbix Agent XXL 3.0 updates right now.

We would like to publish paid version as a Docker image monitoringartist/zabbix-agent-xxl soon. It won't have any limitations of public limited image and some additional features will be included. Current roadmap:

• host metrics - see example of Zabbix Agent XXL template with some host metrics
• realtime docker.discovery
• Kubernetes monitoring - again realtime container discovery

No classic rpm/deb package installation or Zabbix module compilation. Just start zabbix-agent-xxl container and your Docker container metrics will be collected from the Docker daemon or cgroup layer.

• zabbix_agent_bench - utility to test performance of Zabbix agent
• zabbix-server-stress-test - loadbable agent module for stress testing

Zabbix agent stress testing:

docker run \
  --name=zabbix-agent-xxl \
  -h $(hostname) \
  -p 10050:10050 \
  -v /:/rootfs \
  -e "ZA_Server=<ZABBIX SERVER IP/DNS NAME>" \
  -d monitoringartist/zabbix-agent-xxl-limited:latest
  
# used HW - 8xCPU Intel(R) Xeon(R) CPU E31270 @ 3.40GHz:
docker exec -ti zabbix-agent-xxl zabbix_agent_bench -timelimit 30 -key stress.ping --threads 50
Testing 1 keys with 50 threads (press Ctrl-C to cancel)...
stress.ping :	1225787	0	0

=== Totals ===

Total values processed:		1225787
Total unsupported values:	0
Total transport errors:		0
Total key list iterations:	1225787

Finished! Processed 1225787 values across 50 threads in 30.002141605s (40856.650040 NVPS)

You can use any agent config variable, just add prefix ZA_. If you don't specify custom settings, then default Zabbix agent settings will be used.

Example:

docker run \
  --name=zabbix-agent-xxl \
  -h $(hostname) \
  -p 10050:10050 \
  -v /:/rootfs \
  -e "ZA_Server=<ZABBIX SERVER IP/DNS NAME>" \
  -e "ZA_ServerActive=<ZABBIX SERVER IP/DNS NAME>" \
  -e "ZA_StartAgents=10" \
  -e "ZA_Timeout=30" \
  -d monitoringartist/zabbix-agent-xxl-limited:latest

Some settings are excluded and you can't override them: AllowRoot, LoadModulePath, LoadModule, LogType, because Docker monitoring module is used.

Be aware of limited monitoringartist/zabbix-agent-xxl-limited functionalities:

• zabbix agent provides only docker metrics, TLS fearures and agent's Zabbix server IP check are disabled
• zabbix-agent-xxl-limited container publish statistic information

Source code of limited zabbix-agent is published in src directory.

• Puppet for dockerized zabbix-agent-xxl-limited
• Ansible for dockerized zabbix-agent-xxl-limited
• docker-compose for dockerized zabbix-agent-xxl-limited

Check container logs docker logs zabbix-agent-xxl. Development is driven by customer. You can still report bugs, however customer bugs/feature requests will be prioritized. Please provide all details to replicate your issue (Docker/OS version, how was started zabbix-agent/monitored container, listing of you cgroup pseudofiles, ....). Keep in mind that limited Docker image doesn't provide all Zabbix agent features.

Free public Docker image monitoringartist/zabbix-agent-xxl-limited has best effort support. Paid private Docker image monitoringartist/zabbix-agent-xxl has a standard tech support and its issues are prioritized. Our typical response time is 1 working day.

Our zabbix-agent-xxl Docker images are security scanned regularly. All detected vulnerabilities are fixed*:

• Critical vulnerabilities - within 72 hours of notification
• Major vulnerabilities - within 7 days of notification

*except Zabbix security issues, which will be reported directly to Zabbix vendor

Devops Monitoring zExpert, who loves monitoring systems, which start with letter Z. Those are Zabbix and Zenoss.

Professional monitoring services: