is not reflected in documentation of 4.X but is present in documentation of 5.X and 6.X but i found a workaround.. you take the result of only one key and created the others three parts .. so you can use wmi.get[<namespace>,<query>] in independent way i was able to get in a testing way data using direct wmi query call: wmi.get[root\cimv2,"Select ResponseTime From Win32_PingStatus where Address = '8.8.8.8'"]
i try to use zabbix 6.4 and still does not get such key getall so i guess each part of the result should get one by one:
but when i choose agent (in passive) getall is available
hi as i commented in commit https://github.com/Semiadmin/zbx-win-agent-ping/commit/ec2fce6ff12e7978f8ced602a9c624109a136853#comments of PR #2 seems this template does not work with proxy monitoring (agent active)?
well zabbix are not a good open source "community" i already put a bug that still today does not get a fix https://support.zabbix.com/browse/ZBX-21217
is not reflected in documentation of 4.X but is present in documentation of 5.X and 6.X but i found a workaround.. you take the result of only one key and created the others three parts .. so you can use
wmi.get[<namespace>,<query>]in independent way i was able to get in a testing way data using direct wmi query call:wmi.get[root\cimv2,"Select ResponseTime From Win32_PingStatus where Address = '8.8.8.8'"]i try to use zabbix 6.4 and still does not get such key getall so i guess each part of the result should get one by one:
but when i choose agent (in passive) getall is available