- Q: I am monitoring network traffic, but the numbers are unrealistically huge.
A: As the data is likely provided as a counter, make sure the result is stored as delta (speed per second) on Zabbix.
- Q: I'm monitoring a 10 G interface speed in bytes per second, and when the interface is loaded, I lose values.
A: Make sure Type of information is set to Numeric (unsigned). This way, you'll lose the precision of a fraction of a bit, but keep all the values.
- Q: Zabbix does not like the formula for my calculated item.
A: Make sure to use proper quoting, especially if the referenced item keys have quotes. For example, if the referenced item key is key["parameter",param] in the calculated item formula, it can be used as last("key["parameter",param]"). Notice the escaping of the inner double quotes with backslashes.
- Q: I'm trying to use an item key, such as proc.num['apache'], but it does not work.
A: Zabbix supports only double quotes; do not use single quotes for quoting.
- Q: I'm trying to use a trigger expression, such as {host:item.LAST()=13}, but it does not work.
A: The problem could be case sensitivity, almost everything is case-sensitive in Zabbix: item keys, their parameters, host names, trigger functions, and so on. If you come from Windows, keep reminding yourself that case matters.