Zabbix: Difference between revisions
From DWIKI
m (→FAQ) |
mNo edit summary |
||
| Line 34: | Line 34: | ||
==vmware.hv.cpu.usage[{$URL},{HOST.HOST}]" became not supported: Couldn't resolve host name== | ==vmware.hv.cpu.usage[{$URL},{HOST.HOST}]" became not supported: Couldn't resolve host name== | ||
Set macro {$URL} to https://your.ip/sdk/ (shouldn't discovery figure that out from {$HOST} ? | Set macro {$URL} to https://your.ip/sdk/ (shouldn't discovery figure that out from {$HOST} ? | ||
==unsupported item key== | |||
This might mean it's expecting a value from the script you're calling. | |||
echo 1 | |||
Revision as of 16:23, 12 July 2017
Links
FAQ
Zabbix unreachable poller processes more than 75% busy
Increase StartPollersUnreachable
Check agent
zabbix_get -s my.host.com -k agent.version
ZBX_NOTSUPPORTED
Could be anything, enable logging on agent. It could be version mismatch. Check
zabbix_get -s yourhost -k agent.version
If that works, you're calling for an undefined or unsupported key.
Incorrect trigger expression. Host "xx" does not exist or you have no access to this host.
Means there's no related item.
zabbix_get returns nothing
best look at log on agent side
Zabbix server is not running: the information displayed may not be current
Might be selinux: http://sysads.co.uk/2013/11/zabbix-server-running-alert/
vmware.hv.cpu.usage[{$URL},{HOST.HOST}]" became not supported: Couldn't resolve host name
Set macro {$URL} to https://your.ip/sdk/ (shouldn't discovery figure that out from {$HOST} ?
unsupported item key
This might mean it's expecting a value from the script you're calling.
echo 1
