Having to use some large numbers, for example '86400' to represent the number of seconds in one day, is both difficult and error-prone. This is why you can use some appropriate unit symbols (or suffixes) to simplify Zabbix trigger expressions and item keys.
Instead of '86400' for the number of seconds you can simply enter '1d'. Suffixes function as multipliers.
For time you can use:
Time suffixes support only integer numbers (so '1h' is supported, '1,5h' or '1.5h' are not; use '90m' instead).
Time suffixes are supported in:
ha_set_failover_delay=delayruntime control option
Memory size suffixes are supported in:
For memory size you can use:
Unit symbols are also used for a human-readable representation of data in the frontend.
In both Zabbix server and frontend these symbols are supported:
When item values in B, Bps are displayed in the frontend, base 2 is applied (1K = 1024). Otherwise a base of 10 is used (1K = 1000).
Additionally the frontend also supports the display of:
By using some appropriate suffixes you can write trigger expressions that are easier to understand and maintain, for example these expressions:
last(/host/system.uptime)<86400s avg(/host/system.cpu.load,600s)<10 last(/host/vm.memory.size[available])<20971520
could be changed to: