Closed JustDevZero closed 4 years ago
It looks like the network is not working properly for that image at all, which is weird...
ubuntu@ip-172-30-24-157:~/zabbix$ docker-compose exec zabbix-agent sh
WARNING: Some services (zabbix-agent, zabbix-server, zabbix-snmptraps, zabbix-web-nginx-pgsql) use the 'deploy' key, which will be ignored. Compose does not support 'deploy' configuration - use `docker stack deploy` to deploy to a swarm.
/var/lib/zabbix # ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 115ms
Can it be a IP collision? :/
As you can see on the yaml file, the service zabbix-agent use network zbx_net_backend which stated as internal network "internal = true"
To monitor the zabbix agent just change on the zabbix web from 127.0.0.1
to one of the aliases (eg. zabbix-agent
), that should resolve the issue.
But if you want to expose zabbix agent to external, you can add zbx_net_frontend:
under zabbix-agent service, the port will be shown in docker container ls
output. So in the end zabbix-agent will have 2 interface which you can check using ip addr show
inside the container.
Thanks! Didn't notice that... I was going nuts for being stubborn. As you said using the alias worked without any problem. :+1:
I think this can be closed.
Hi all. I don t have very clear Where i have to put the alias on the zabbix web. Thanks.
Same here! Where I need to put aliases?
Hey. You need to go to zabbix web console and change inventory of host zabbix-server. Interfaces>Agent>DNS name: "zabbix-agent".
It looks like zabbix-agent does not get exposed, in the result of being unable to monitorize zabbix it self:
Here's my docker-compose.yml
And the docker ps:
Is there something I'm missing?