Zabbix Documentation 3.0

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:config:items:item

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:items:item [2019/03/06 12:02]
martins-v 0 is also possible for 'history/trend storage'
manual:config:items:item [2019/04/16 12:40] (current)
martins-v incoming values with a fractional part may be trimmed before the custom multiplier is applied
Line 24: Line 24:
 |//Data type// ​ |Data type is used for integer items in order to specify the expected data type:\\ **Boolean** - textual representation translated into either 0 or 1. Thus, '​TRUE'​ is stored as 1 and '​FALSE'​ is stored as 0. All values are matched in a case-insensitive way. Currently recognized values are, for:\\ //TRUE// - true, t, yes, y, on, up, running, enabled, available\\ //FALSE// - false, f, no, n, off, down, unused, disabled, unavailable\\ Additionally,​ any non-zero numeric value is considered to be TRUE and zero is considered to be FALSE. \\ **Octal** - data in octal format\\ **Decimal** - data in decimal format\\ **Hexadecimal** - data in hexadecimal format\\ Zabbix will automatically perform the conversion to numeric.\\ The conversion is done by Zabbix server (even when a host is monitored by Zabbix proxy). ​ | |//Data type// ​ |Data type is used for integer items in order to specify the expected data type:\\ **Boolean** - textual representation translated into either 0 or 1. Thus, '​TRUE'​ is stored as 1 and '​FALSE'​ is stored as 0. All values are matched in a case-insensitive way. Currently recognized values are, for:\\ //TRUE// - true, t, yes, y, on, up, running, enabled, available\\ //FALSE// - false, f, no, n, off, down, unused, disabled, unavailable\\ Additionally,​ any non-zero numeric value is considered to be TRUE and zero is considered to be FALSE. \\ **Octal** - data in octal format\\ **Decimal** - data in decimal format\\ **Hexadecimal** - data in hexadecimal format\\ Zabbix will automatically perform the conversion to numeric.\\ The conversion is done by Zabbix server (even when a host is monitored by Zabbix proxy). ​ |
 |//​Units// ​ |If a unit symbol is set, Zabbix will add post processing to the received value and display it with the set unit postfix.\\ By default, if the raw value exceeds 1000, it is divided by 1000 and displayed accordingly. For example, if you set //bps// and receive a value of 881764, it will be displayed as 881.76 Kbps. \\ Special processing is used for **B** (byte), **Bps** (bytes per second) units, which are divided by 1024. Thus, if units are set to **B** or **Bps** Zabbix will display:\\ 1 as 1B/1Bps\\ 1024 as 1KB/1KBps\\ 1536 as 1.5KB/​1.5KBps\\ Special processing is used if the following time-related units are used:\\ **unixtime** - translated to "​yyyy.mm.dd hh:​mm:​ss"​. To translate correctly, the received value must be a //Numeric (unsigned)//​ type of information.\\ **uptime** - translated to "​hh:​mm:​ss"​ or "N days, hh:​mm:​ss"​\\ For example, if you receive the value as 881764 (seconds), it will be displayed as "10 days, 04:​56:​04"​\\ **s** - translated to "yyy mmm ddd hhh mmm sss ms"; parameter is treated as number of seconds.\\ For example, if you receive the value as 881764 (seconds), it will be displayed as "10d 4h 56m"\\ Only 3 upper major units are shown, like "1m 15d 5h" or "2h 4m 46s". If there are no days to display, only two levels are displayed - "1m 5h" (no minutes, seconds or milliseconds are shown). Will be translated to "< 1 ms" if the value is less than 0.001.\\ See also the [[#​unit_blacklist|unit blacklist]]. ​ | |//​Units// ​ |If a unit symbol is set, Zabbix will add post processing to the received value and display it with the set unit postfix.\\ By default, if the raw value exceeds 1000, it is divided by 1000 and displayed accordingly. For example, if you set //bps// and receive a value of 881764, it will be displayed as 881.76 Kbps. \\ Special processing is used for **B** (byte), **Bps** (bytes per second) units, which are divided by 1024. Thus, if units are set to **B** or **Bps** Zabbix will display:\\ 1 as 1B/1Bps\\ 1024 as 1KB/1KBps\\ 1536 as 1.5KB/​1.5KBps\\ Special processing is used if the following time-related units are used:\\ **unixtime** - translated to "​yyyy.mm.dd hh:​mm:​ss"​. To translate correctly, the received value must be a //Numeric (unsigned)//​ type of information.\\ **uptime** - translated to "​hh:​mm:​ss"​ or "N days, hh:​mm:​ss"​\\ For example, if you receive the value as 881764 (seconds), it will be displayed as "10 days, 04:​56:​04"​\\ **s** - translated to "yyy mmm ddd hhh mmm sss ms"; parameter is treated as number of seconds.\\ For example, if you receive the value as 881764 (seconds), it will be displayed as "10d 4h 56m"\\ Only 3 upper major units are shown, like "1m 15d 5h" or "2h 4m 46s". If there are no days to display, only two levels are displayed - "1m 5h" (no minutes, seconds or milliseconds are shown). Will be translated to "< 1 ms" if the value is less than 0.001.\\ See also the [[#​unit_blacklist|unit blacklist]]. ​ |
-|//Use custom multiplier// ​ |If you enable this option, all received values will be multiplied by the integer or floating-point value set in the value field.\\ Use this option to convert values received in KB, MBps, etc into B, Bps. Otherwise Zabbix cannot correctly set [[manual:​config:​triggers:​suffixes|prefixes]] (K, M, G etc).\\ Starting with Zabbix 2.2, using scientific notation is also supported. E.g. 1e+70. ​ |+|//Use custom multiplier// ​ |If you enable this option, all received values will be multiplied by the integer or floating-point value set in the value field.\\ Use this option to convert values received in KB, MBps, etc into B, Bps. Otherwise Zabbix cannot correctly set [[manual:​config:​triggers:​suffixes|prefixes]] (K, M, G etc).\\ //Note// that if the item type of information is //Numeric (unsigned)//,​ incoming values with a fractional part will be trimmed (i.e. '​0.9'​ will become '​0'​) before the custom multiplier is applied.\\ Starting with Zabbix 2.2, using scientific notation is also supported. E.g. 1e+70. ​ |
 |//Update interval (in sec)// ​ |Retrieve a new value for this item every N seconds. Maximum allowed update interval is 86400 seconds (1 day).\\ //Note//: If set to %%"​%%0%%"​%%,​ the item will not be polled. However, if a custom interval (flexible/​scheduling) also exists with a non-zero value, the item will be polled during the custom interval duration.| |//Update interval (in sec)// ​ |Retrieve a new value for this item every N seconds. Maximum allowed update interval is 86400 seconds (1 day).\\ //Note//: If set to %%"​%%0%%"​%%,​ the item will not be polled. However, if a custom interval (flexible/​scheduling) also exists with a non-zero value, the item will be polled during the custom interval duration.|
 |//Custom intervals// ​ |You can create custom rules for checking the item:\\ **Flexible** - create an exception to the //Update interval// (interval with different frequency)\\ **Scheduling** - create a custom polling schedule.\\ For detailed information see [[manual:​config:​items:​item:​custom_intervals|Custom intervals]]. Scheduling is supported since Zabix 3.0.0.\\ //Note//: Not available for Zabbix agent active items. ​ | |//Custom intervals// ​ |You can create custom rules for checking the item:\\ **Flexible** - create an exception to the //Update interval// (interval with different frequency)\\ **Scheduling** - create a custom polling schedule.\\ For detailed information see [[manual:​config:​items:​item:​custom_intervals|Custom intervals]]. Scheduling is supported since Zabix 3.0.0.\\ //Note//: Not available for Zabbix agent active items. ​ |