search

monitoringartist / zabbix-docker-monitoring

:whale: Docker/Kubernetes/Mesos/Marathon/Chronos/LXC/LXD/Swarm container monitoring - Docker image, Zabbix template and C module
https://hub.docker.com/r/monitoringartist/zabbix-agent-xxl-limited/
GNU General Public License v2.0
1.19k stars 268 forks source link

Cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/docker//22ceac2c1007/cpuacct.stat' #139

Closed jbollman7 closed 4 years ago

jbollman7 commented 4 years ago

I am running zabbix agent with the zabbix_docker_monitoring.so module. The agent can "see" the cdocker conatiner running however it can not read any of the metrics files. My /etc/zabbix/zabbix_agentd.conf

cat /etc/zabbix/zabbix_agentd.conf 
PidFile=/var/run/zabbix/zabbix_agentd.pid
LogFile=/var/log/zabbix/zabbix_agentd.log
LogFileSize=128
Server=10.7.10.119
ServerActive=10.7.10.119
Hostname=pdx1_sgh01_n02.faction.cloud
Include=/etc/zabbix/zabbix_agentd.d/*.conf
LoadModulePath=/etc/zabbix
LoadModule=./zabbix_module_docker.so

I *think my issue is due to that double forward slash? 

tail /var/log/zabbix/zabbix_agentd.log
123169:20200226:143116.208 Cannot open metric file: '/sys/fs/cgroup/memory/docker//fc38108cca43/memory.stat'
123168:20200226:143117.209 Cannot open metric file: '/sys/fs/cgroup/memory/docker//96b0f4e08e5f/memory.stat'
123168:20200226:143118.210 Cannot open metric file: '/sys/fs/cgroup/memory/docker//cdaecf238758/memory.stat'
123168:20200226:143119.000 Cannot open metric file: '/sys/fs/cgroup/memory/docker//9c8079967e2c/memory.stat'
123168:20200226:143120.007 Cannot open metric file: '/sys/fs/cgroup/memory/docker//fd648c678a1c/memory.stat'
123169:20200226:143121.008 Cannot open metric file: '/sys/fs/cgroup/memory/docker//84aa67386fca/memory.stat'
123168:20200226:143122.033 Cannot open metric file: '/sys/fs/cgroup/memory/docker//4b49922800ee/memory.stat'
123168:20200226:143123.035 Cannot open metric file: '/sys/fs/cgroup/memory/docker//eaa96d8bbd3d/memory.stat'
123168:20200226:143124.036 Cannot open metric file: '/sys/fs/cgroup/memory/docker//860af6b7e387/memory.stat'
123169:20200226:143125.037 Cannot open metric file: '/sys/fs/cgroup/memory/docker//3237d1fe9a92/memory.stat'

1. cat /etc/release

CentOS Linux release 7.6.1810 (Core) 
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

CentOS Linux release 7.6.1810 (Core) 
CentOS Linux release 7.6.1810 (Core)

2. uname -a

Linux pdx1_sgh01_n02.faction.cloud 3.10.0-957.12.1.el7.x86_64 #1 SMP Mon Apr 29 14:59:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

3. docker info

Client:
 Debug Mode: false

Server:
 Containers: 36
  Running: 23
  Paused: 0
  Stopped: 13
 Images: 7
 Server Version: 18.09.6
 Storage Driver: overlay2
  Backing Filesystem: xfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: b34a5c8af56e510852c35414db4c1f4fa6172339
 runc version: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 3.10.0-957.12.1.el7.x86_64
 Operating System: CentOS Linux 7 (Core)
 OSType: linux
 Architecture: x86_64
 CPUs: 40
 Total Memory: 251.6GiB
 Name: pdx1_sgh01_n02.faction.cloud
 ID: VH6G:REV6:A4XY:ZONF:PEXP:J2LR:N6BY:WGGR:QQK3:DHD2:FIAF:Y26N
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Username: jrsmithfaction
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

WARNING: API is accessible on http://0.0.0.0:2376 without encryption.
         Access to the remote API is equivalent to root access on the host. Refer
         to the 'Docker daemon attack surface' section in the documentation for
         more information: https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

4. find /sys/fs/cgroup/cpu,cpuacct/ -name "docker"

/sys/fs/cgroup/cpu,cpuacct/docker
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-35cba82b51af.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-d0e1b0b08f4f96ef5a3b0429ae9a5d713d7f0727b812f0a43677acc18fd16734-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-f801cd670b1553da45d2f1419c83612df8a908400b94e994e876f46baa1edc8e-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-fc38108cca43391959a1ba157fa0c1493a2f20ccf5b46a3be140eeb6521fb9dc-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-14a3d87dd34462c6679f76f1b66faad722c47ff3ed1323cc202933d05d0c772b-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-579e60084f5ee4d492943d7519abd8e9bd3310539fdcb381322e7d192f8aa989-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-4b49922800ee8f4a770ea24c4d104f9eff918b7a2ca7fd321639b9407d5376fb-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-default.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-96b0f4e08e5f5524a3416ffd3f59430bbb0b826083bb09065e13cf5686d090c8-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-cdaecf238758d3327103f1844553bc3b822ad774aa2015dba51785d195638928-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-2e184b42261eeac6b5884c3271fddf797dbc29658c71f581d673b4a63f09c246-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-bc820d500e99cce5724d6a661ebd8f9433665d5e800b6fbcf462091e33573116-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-3e51727e54c784a6caa4735f154ea27e5998e7f8b0368177c56f1bd42de94578-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-ca3db6d98372121061384ccc4df4a224c8b35919a601a19200e6aa5f42bfd523-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-fd648c678a1ce6a654bab71ec2e0d313c00c71172e9a6fd04c4a6508c86025ed-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-eaa96d8bbd3d3d4a8e56ae730ca8be54e2699815b44dd8446fbdd62e8340a720-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-9c8079967e2c554768d27b3d2123d28bdb6c85c58c67eeac7c1b3bf60a5dba0f-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-c6c7f4ee77b49b63a9be9a21ad230efb2553bcbaced0e94014a5fd2f0abb3530-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-84aa67386fca6b72071cd4127e49eefc86269ccbb2da71f61f71f73e0468f294-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-6369cab15b23457759e9e68d1d1591607352035ac7ffe27a9c8771f77cd0ebc6-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-3237d1fe9a9272bebcb0abbc0b269c340c7219c028a5dc325de4ee829b4e349a-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-e51f7da47b121e9255e1d912005fa8a09ce7dddc7e095e9bb6f73bf7fd260148-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-513f97ae082962dcaed23208d773d879d5b82a908d4dc8f10b7becdb8cc8eb96-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-860af6b7e387b06d7e42c222853a9ddd05259996cfbdeb2d19f5f2bdb7aece0c-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-b42d185d5e2bea4d753b7c3c762bedbdd8805ce210ccddc61d77eb631f488f22-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-147a940ee4c2a9b3a48855247e0b728e73dfdd2baba983db55c2805662521e4b-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-a221c470a7bb.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-87a1b1ee94f1.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-8a79b7f5a23a.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-622b505555cb.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-311ebba37717.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-4d537d648b9d.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-22ceac2c1007de4ccd355a28d0292d0c64898d5096544ede233ce2bdee2c022e-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-765e86abbb1777339bef742f35720287ed9466a4b4555804a9e1fa45f931fd92-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-b062e46f899dc0586fad50f4662ebd277f7e616a7d4bc8c0081d2b2db5039ed7-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-cdd7f2f683c9ef8ac2656d3a31558f2db5f93fad07410ac5d452173f30aaf087-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-0a2201629fe0.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-b21896090919.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-24a753cce017f5e95c5f71a696d590e8fd858826d8ae544b06f4e083d909f934-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-1a4f79916bad1a48249c11e6d68cef52fe09538c591b21b55b8a7cbf7a4e2968-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-e5e14990e8d7.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-3f4ba80094061f425240e8cecba427c795b66c06f7d5193db9c2699be3785da4-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-3c77aab55003.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/run-docker-netns-6d12cc0866e8.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-e4e3fc6924eaaaa3edfb8731cd6adaebb12dc06caa7b349b95750a3063d72af4-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-6dc6653acf36907f1e135120c59868a85cdd2e30bc7faeb8b619b51a86c8d903-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-72944f226bac2bc681184b42587947f25de1a552559f73c1d7a8558d091c48e4-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-4aae9637854bf6e28478f0814d51bdab3978ac8a74f640d899c8f279a8161e6f-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-7f84c5c5f19eb51c4368bbed1d1c9eb1f320cb0ad83f14d90c35cd91583c863b-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-4191805e6ed7a528ce39e3a2bdb1a67371db985624c9d5d643e4dac05ffd15be-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-778270d2e57ba7e05c926b59f80fe2f2636b08528a2b1e8430827ecb8748336e-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-43577d6c2201022a4c812154e055a195afc4306040d7da78cb5f33c070f23a03-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-819056d8d6ed78c8252d51bb4cef3ba0ecc1f6b1bd22ba64ad5939415c1bd11d-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-08ff88cbd5ad87649484aa0a0aa833c23ac2d20e3743c293f3edd44068b3af3e-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-d03d33c9e9d05cd947c63784f6d4c8862ed16b539ae5b262aed13abbf86e3ba7-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-43c12d35f7c61c26a7f0206282d0b536954bc2e0d601ed6359ddc947471e32e5-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-containers-69a0acc240c875e453b532c4df93826e8ce72d4bdb9716decc379d26128d26a0-mounts-shm.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-005caa058742839b95779f4a857d4a4e461ea995f94492f87e03713354c68e25-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/var-lib-docker-overlay2-c0fe0aa1894de121730297703dfc953028753bf1c6b0bfdcdcbedfcf3e17e97c-merged.mount
/sys/fs/cgroup/cpu,cpuacct/system.slice/docker.service
  1. ls -lah /sys/fs/cgroup/cpu,cpuacct/docker 
    drwxr-xr-x 25 root root 0 Feb 21 14:34 .
drwxr-xr-x  5 root root 0 Feb 21 14:33 ..
drwxr-xr-x  2 root root 0 Feb 21 14:34 1a4f79916bad1a48249c11e6d68cef52fe09538c591b21b55b8a7cbf7a4e2968
drwxr-xr-x  2 root root 0 Feb 21 14:34 22ceac2c1007de4ccd355a28d0292d0c64898d5096544ede233ce2bdee2c022e
drwxr-xr-x  2 root root 0 Feb 21 14:34 24a753cce017f5e95c5f71a696d590e8fd858826d8ae544b06f4e083d909f934
drwxr-xr-x  2 root root 0 Feb 21 14:34 3237d1fe9a9272bebcb0abbc0b269c340c7219c028a5dc325de4ee829b4e349a
drwxr-xr-x  2 root root 0 Feb 21 14:34 3f4ba80094061f425240e8cecba427c795b66c06f7d5193db9c2699be3785da4
drwxr-xr-x  2 root root 0 Feb 21 14:34 4b49922800ee8f4a770ea24c4d104f9eff918b7a2ca7fd321639b9407d5376fb
drwxr-xr-x  2 root root 0 Feb 21 14:34 579e60084f5ee4d492943d7519abd8e9bd3310539fdcb381322e7d192f8aa989
drwxr-xr-x  2 root root 0 Feb 21 14:34 69a0acc240c875e453b532c4df93826e8ce72d4bdb9716decc379d26128d26a0
drwxr-xr-x  2 root root 0 Feb 21 14:34 6dc6653acf36907f1e135120c59868a85cdd2e30bc7faeb8b619b51a86c8d903
drwxr-xr-x  2 root root 0 Feb 21 14:34 72944f226bac2bc681184b42587947f25de1a552559f73c1d7a8558d091c48e4
drwxr-xr-x  2 root root 0 Feb 21 14:34 765e86abbb1777339bef742f35720287ed9466a4b4555804a9e1fa45f931fd92
drwxr-xr-x  2 root root 0 Feb 21 14:34 84aa67386fca6b72071cd4127e49eefc86269ccbb2da71f61f71f73e0468f294
drwxr-xr-x  2 root root 0 Feb 21 14:34 860af6b7e387b06d7e42c222853a9ddd05259996cfbdeb2d19f5f2bdb7aece0c
drwxr-xr-x  2 root root 0 Feb 21 14:34 96b0f4e08e5f5524a3416ffd3f59430bbb0b826083bb09065e13cf5686d090c8
drwxr-xr-x  2 root root 0 Feb 21 14:34 9c8079967e2c554768d27b3d2123d28bdb6c85c58c67eeac7c1b3bf60a5dba0f
drwxr-xr-x  2 root root 0 Feb 21 14:34 b062e46f899dc0586fad50f4662ebd277f7e616a7d4bc8c0081d2b2db5039ed7
drwxr-xr-x  2 root root 0 Feb 21 14:34 cdaecf238758d3327103f1844553bc3b822ad774aa2015dba51785d195638928
drwxr-xr-x  2 root root 0 Feb 21 14:34 cdd7f2f683c9ef8ac2656d3a31558f2db5f93fad07410ac5d452173f30aaf087
-rw-r--r--  1 root root 0 Feb 21 14:34 cgroup.clone_children
--w--w--w-  1 root root 0 Feb 21 14:34 cgroup.event_control
-rw-r--r--  1 root root 0 Feb 21 14:34 cgroup.procs
-r--r--r--  1 root root 0 Feb 21 14:34 cpuacct.stat
-rw-r--r--  1 root root 0 Feb 21 14:34 cpuacct.usage
-r--r--r--  1 root root 0 Feb 21 14:34 cpuacct.usage_percpu
-rw-r--r--  1 root root 0 Feb 21 14:34 cpu.cfs_period_us
-rw-r--r--  1 root root 0 Feb 21 14:34 cpu.cfs_quota_us
-rw-r--r--  1 root root 0 Feb 21 14:34 cpu.rt_period_us
-rw-r--r--  1 root root 0 Feb 21 14:34 cpu.rt_runtime_us
-rw-r--r--  1 root root 0 Feb 21 14:34 cpu.shares
-r--r--r--  1 root root 0 Feb 21 14:34 cpu.stat
drwxr-xr-x  2 root root 0 Feb 25 08:57 d0e1b0b08f4f96ef5a3b0429ae9a5d713d7f0727b812f0a43677acc18fd16734
drwxr-xr-x  2 root root 0 Feb 21 14:34 e4e3fc6924eaaaa3edfb8731cd6adaebb12dc06caa7b349b95750a3063d72af4
drwxr-xr-x  2 root root 0 Feb 21 14:34 eaa96d8bbd3d3d4a8e56ae730ca8be54e2699815b44dd8446fbdd62e8340a720
drwxr-xr-x  2 root root 0 Feb 21 14:34 fc38108cca43391959a1ba157fa0c1493a2f20ccf5b46a3be140eeb6521fb9dc
drwxr-xr-x  2 root root 0 Feb 21 14:34 fd648c678a1ce6a654bab71ec2e0d313c00c71172e9a6fd04c4a6508c86025ed
-rw-r--r--  1 root root 0 Feb 21 14:34 notify_on_release
-rw-r--r--  1 root root 0 Feb 21 14:34 tasks
jangaraj commented 4 years ago

https://github.com/monitoringartist/zabbix-docker-monitoring#troubleshooting

jbollman7 commented 4 years ago

I have set the debug level to 4 as suggested. This is what i see now i still see that double slash in the file path. Also now it looks like a commissioning issue somewhere?

129636:20200227:071233.118 Requested [docker.up[/96b0f4e08e5f]]
129636:20200227:071233.118 In zbx_module_docker_up()
129636:20200227:071233.118 In zbx_module_docker_get_fci()
129636:20200227:071233.118 Translating container name to fci by using docker.inspect
129636:20200227:071233.118 In zbx_module_docker_inspect_exec()
129636:20200227:071233.118 In zbx_docker_api_detect()
129636:20200227:071233.118 In zbx_docker_perm()
129636:20200227:071233.118 Additional permission of Zabbix Agent are not detected - only basic docker metrics are available
129636:20200227:071233.118 Docker's socket API is not available
129636:20200227:071233.118 Default fci will be used, because zbx_module_docker_inspect_exec FAIL: Docker's socket API is not available
129636:20200227:071233.118 Metric source file: /sys/fs/cgroup/cpu,cpuacct/docker//96b0f4e08e5f/cpuacct.stat
129636:20200227:071233.119 Cannot open metric file: '/sys/fs/cgroup/cpu,cpuacct/docker//96b0f4e08e5f/cpuacct.stat', container doesn't run
129636:20200227:071233.119 Sending back [0]
129636:20200227:071233.119 __zbx_zbx_setproctitle() title:'listener #1 [waiting for connection]'
129637:20200227:071233.119 __zbx_zbx_setproctitle() title:'listener #2 [processing request]'
129637:20200227:071233.119 Requested [docker.cpu[/9c8079967e2c,total]]
129637:20200227:071233.119 In zbx_module_docker_cpu()
129637:20200227:071233.119 In zbx_module_docker_get_fci()
129637:20200227:071233.119 Translating container name to fci by using docker.inspect
129637:20200227:071233.119 In zbx_module_docker_inspect_exec()
129637:20200227:071233.119 In zbx_docker_api_detect()
129637:20200227:071233.119 In zbx_docker_perm()
129637:20200227:071233.119 Additional permission of Zabbix Agent are not detected - only basic docker metrics are available
129637:20200227:071233.119 Docker's socket API is not available
129637:20200227:071233.119 Default fci will be used, because zbx_module_docker_inspect_exec FAIL: Docker's socket API is not available
jangaraj commented 4 years ago

Additional permission of Zabbix Agent are not detected - only basic docker metrics are available 129636:20200227:071233.118 Docker's socket API is not available -> https://github.com/monitoringartist/zabbix-docker-monitoring#additional-docker-permissions