Zabbix Documentation 2.0

3.04.04.45.0 (current)| In development:5.2 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:config:triggers:suffixes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:config:triggers:suffixes [2014/09/26 11:32]
sasha Links adapted because of a move operation
manual:config:triggers:suffixes [2016/10/17 10:44] (current)
martins-v logical reworking of 'unit symbol' section
Line 3: Line 3:
 === Overview === === Overview ===
  
-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 ​or item keys. +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'​ you can simply enter '​1d'​. Suffixes function as multipliers. Instead of '​86400'​ you can simply enter '​1d'​. Suffixes function as multipliers.
  
-=== Time unit suffixes ​===+=== Trigger expressions ​=== 
 + 
 +Time and memory size suffixes are supported in trigger [[expression|expression]] constants and function parameters.
  
 For time you can use: For time you can use:
Line 17: Line 19:
   * **w** - weeks    * **w** - weeks 
  
-Time unit suffixes are supported in: +Time suffixes are also supported in parameters of the **zabbix[queue,<​from>,<​to>​]** [[manual:config:​items:​itemtypes:​internal|internal item]] and the last parameter of [[manual:​config:​items:​itemtypes:​aggregate|aggregate checks]]. 
 + 
 +For memory size you can use: 
 + 
 +  * **K** - kilobyte 
 +  * **M** - megabyte 
 +  * **G** - gigabyte 
 +  * **T** - terabyte ​
  
-  - [[expression|trigger expressions]] (constants and function parameters) +=== Other uses ===
-  - parameters of the **zabbix[queue,<​from>,<​to>​]** [[manual:​config:​items:​itemtypes:​internal|internal item]]  +
-  - last parameter of [[manual:​config:​items:​itemtypes:​aggregate|aggregate checks]]+
  
-=== Prefix ​symbols ​===+Unit symbols ​are also used for a human-readable representation of data in the frontend.
  
-In both Zabbix server and frontend these prefix ​symbols are supported ​for both display and usage in trigger expressions (constants and function parameters):+In both Zabbix server and frontend these symbols are supported:
  
   * **K** - kilo    * **K** - kilo 
Line 32: Line 39:
   * **T** - tera    * **T** - tera 
  
-When item values ​other than in B, Bps are displayed in the frontend, ​base of 10 is used (1K = 1000). Apart from that, base is applied ​(1K = 1024everywhere.+When item values in B, Bps are displayed in the frontend, base is applied ​(1K = 1024). Otherwise a base of 10 is used (1K = 1000).
  
 Additionally the frontend also supports the display of: Additionally the frontend also supports the display of:
Line 48: Line 55:
   {host:​system.uptime[].last(0)}<​86400   {host:​system.uptime[].last(0)}<​86400
   {host:​system.cpu.load.avg(600)}<​10   {host:​system.cpu.load.avg(600)}<​10
 +  {host:​vm.memory.size[available].last(0)}<​20971520
  
 could be changed to:  could be changed to: 
Line 54: Line 62:
   {host:​system.uptime.last(0)}<​1d   {host:​system.uptime.last(0)}<​1d
   {host:​system.cpu.load.avg(10m)}<​10   {host:​system.cpu.load.avg(10m)}<​10
 +  {host:​vm.memory.size[available].last(0)}<​20M