Public Repository

Last pushed: a year ago
Short Description
Please use better agent image https://hub.docker.com/r/monitoringartist/dockbix-agent-xxl-limited/
Full Description

2nd generation of this successful image (400k+ pulls) has been released. Now with Docker metrics and also with OS Linux host metric support. Please use better Zabbix agent Docker image:
https://hub.docker.com/r/monitoringartist/dockbix-agent-xxl-limited/

Thank you!

Run command (only for the record):

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

Author

Devops Monitoring Expert, who loves monitoring systems and cutting/bleeding edge technologies: Docker,
Kubernetes, ECS, AWS, Google GCP, Terraform, Lambda, Zabbix, Grafana, Elasticsearch, Kibana, Prometheus, Sysdig, ...

Summary:

Professional devops / monitoring / consulting services:

Docker Pull Command
Owner
monitoringartist

Comments (2)
jangaraj
a year ago

Don't use localhost in container, because localhost in container != localhost of docker host.

doublebyte
a year ago

Hi, first of all thanks for doing this. It's a great job to have dockerized monitoring of the docker containers!
I was trying to run this, and launched first the zabbix-db
container and the zabbix server (localhost:10050). Then I launched this container, pointing to ZA_Server=http://localhost:10051 . There are no errors, and everything seems to be running as expected, but when I access the web interface in localhost:80, my containers are nowhere to be seen! Is there something that I need to configure in the UI, maybe? sorry if this is a configuration problem, but I am not very experienced with Zabbix either. And thanks in advance for the reply