Ad Widget

Collapse

unable to set up docker monitoring using zabbix 5.0

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • lastwon
    Junior Member
    • Jul 2020
    • 2

    #1

    unable to set up docker monitoring using zabbix 5.0

    I have recently upgraded to Zabbix 5.0.1 to monitor docker and installed zabbix-agent on a docker server. However, I am into a bit of an issue with errors as following:

    Zabbix Version: 5.0.1
    Zabbix server IP: 192.168.0.60
    Docker server IP: 192.168.0.65

    /etc/zabbix/zabbix_agentd.conf from docker server:

    Code:
    Server=192.168.0.60
    ServerActive=192.168.0.60
    Hostname=docker
    Code:
    [root@docker:/root]# zabbix_get -s 127.0.0.1 -k docker.info
    zabbix_get [904]: Check access restrictions in Zabbix agent configuration
    
    [root@docker:/root]# rpm -qa | grep zabbix
    zabbix-agent2-5.0.2-1.el7.x86_64
    zabbix-release-5.0-1.el7.noarch
    zabbix40-4.0.17-1.el7.x86_64

    Code:
    [root@zabbix:/root]# zabbix_get -s 192.168.0.65 -k docker.info
    ZBX_NOTSUPPORTED: Cannot fetch data.
    
    [root@zabbix:/root]# rpm -qa | grep zabbix
    zabbix-get-5.0.1-1.el7.x86_64
    zabbix-web-5.0.1-1.el7.noarch
    zabbix-web-deps-scl-5.0.1-1.el7.noarch
    zabbix-release-5.0-1.el7.noarch
    zabbix-web-mysql-scl-5.0.1-1.el7.noarch
    zabbix-agent2-5.0.1-1.el7.x86_64
    zabbix-agent-5.0.1-1.el7.x86_64
    zabbix-apache-conf-scl-5.0.1-1.el7.noarch
    zabbix-server-mysql-5.0.1-1.el7.x86_64
    zabbix-java-gateway-5.0.1-1.el7.x86_64
    Please let me know if any additional information is required
    Last edited by lastwon; 16-07-2020, 17:36.
  • visiandy
    Junior Member
    • Jul 2020
    • 8

    #2
    Hey, lastwon!
    You will get error "ZBX_NOTSUPPORTED: Cannot fetch data." if your agent can not access docker socket (/var/run/docker.sock usually). For example you need to add user you're running agent under to "docker" group or run agent as a root. Try to raise agent logging level and check log output, there could be something about either denied access to socker or that agent can not find it (in that case you'll need to change default path in agent config). I had a similar issue, but i was running agent in a container itself.

    Comment

    • lastwon
      Junior Member
      • Jul 2020
      • 2

      #3
      Thank you @visiandy! It worked like a charm.

      Comment

      Working...