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 [2020/01/06 10:51]
martins-v automatic inventory population disallowed for 'log' type of info
manual:config:items:item [2020/05/19 11:37] (current)
marinagen Zabbix spelling corrected
Line 28: Line 28:
 |//​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.\\ //Note// that if a unit is prefixed with ''​!'',​ then no unit prefixes/​processing is applied to item values. See [[#​unit_blacklisting|unit blacklisting]]. ​ | |//​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.\\ //Note// that if a unit is prefixed with ''​!'',​ then no unit prefixes/​processing is applied to item values. See [[#​unit_blacklisting|unit blacklisting]]. ​ |
 |//Update interval// ​ |Retrieve a new value for this item every N seconds. Maximum allowed update interval is 86400 seconds (1 day).\\ [[:​manual/​appendix/​suffixes|Time suffixes]] are supported, e.g. 30s, 1m, 2h, 1d.\\ [[:​manual/​config/​macros/​usermacros|User macros]] are supported.\\ A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.\\ //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.\\ //Note// that the first item poll after the item became active or after update interval change might occur earlier than the configured value.\\ An existing passive item can be polled for value immediately by pushing the //Check now// [[#​form_buttons|button]]. ​ | |//Update interval// ​ |Retrieve a new value for this item every N seconds. Maximum allowed update interval is 86400 seconds (1 day).\\ [[:​manual/​appendix/​suffixes|Time suffixes]] are supported, e.g. 30s, 1m, 2h, 1d.\\ [[:​manual/​config/​macros/​usermacros|User macros]] are supported.\\ A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.\\ //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.\\ //Note// that the first item poll after the item became active or after update interval change might occur earlier than the configured value.\\ An existing passive item can be polled for value immediately by pushing the //Check now// [[#​form_buttons|button]]. ​ |
-|//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]].\\ [[:​manual/​appendix/​suffixes|Time suffixes]] are supported in the //​Interval//​ field, e.g. 30s, 1m, 2h, 1d.\\ [[:​manual/​config/​macros/​usermacros|User macros]] are supported.\\ A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.\\ 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]].\\ [[:​manual/​appendix/​suffixes|Time suffixes]] are supported in the //​Interval//​ field, e.g. 30s, 1m, 2h, 1d.\\ [[:​manual/​config/​macros/​usermacros|User macros]] are supported.\\ A single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.\\ Scheduling is supported since Zabbix ​3.0.0.\\ //Note//: Not available for Zabbix agent active items. ​ |
 |//History storage period// ​ |Select either:\\ **Do not keep history** - item history is not stored. Useful for master items if only dependent items need to keep history.\\ //Note//: Before Zabbix 4.2.5, not keeping history had to be specified by entering %%"​%%0%%"​%% in the storage period field and it could be overridden by global housekeeper settings (now it cannot).\\ **Storage period** - specify the duration of keeping detailed history in the database (1 hour to 25 years). Older data will be removed by the housekeeper. Stored in seconds.\\ [[:​manual/​appendix/​suffixes|Time suffixes]] are supported, e.g. 2h, 1d. [[:​manual/​config/​macros/​usermacros|User macros]] are supported.\\ The //Storage period// value can be overridden globally in //​Administration -> General -> [[manual:​web_interface:​frontend_sections:​administration:​general#​housekeeper|Housekeeper]]//​.\\ If a global overriding setting exists, a green {{manual:​config:​info.png|}} info icon is displayed. If you position your mouse on it, a warning message is displayed, e. g. //​Overridden by global housekeeper settings (1d)//.\\ It is recommended to keep the recorded values for the smallest possible time to reduce the size of value history in the database. Instead of keeping a long history of values, you can keep longer data of trends.\\ See also [[:​manual/​config/​items/​history_and_trends|History and trends]]. ​ | |//History storage period// ​ |Select either:\\ **Do not keep history** - item history is not stored. Useful for master items if only dependent items need to keep history.\\ //Note//: Before Zabbix 4.2.5, not keeping history had to be specified by entering %%"​%%0%%"​%% in the storage period field and it could be overridden by global housekeeper settings (now it cannot).\\ **Storage period** - specify the duration of keeping detailed history in the database (1 hour to 25 years). Older data will be removed by the housekeeper. Stored in seconds.\\ [[:​manual/​appendix/​suffixes|Time suffixes]] are supported, e.g. 2h, 1d. [[:​manual/​config/​macros/​usermacros|User macros]] are supported.\\ The //Storage period// value can be overridden globally in //​Administration -> General -> [[manual:​web_interface:​frontend_sections:​administration:​general#​housekeeper|Housekeeper]]//​.\\ If a global overriding setting exists, a green {{manual:​config:​info.png|}} info icon is displayed. If you position your mouse on it, a warning message is displayed, e. g. //​Overridden by global housekeeper settings (1d)//.\\ It is recommended to keep the recorded values for the smallest possible time to reduce the size of value history in the database. Instead of keeping a long history of values, you can keep longer data of trends.\\ See also [[:​manual/​config/​items/​history_and_trends|History and trends]]. ​ |
 |//Trend storage period// ​ |Select either:\\ **Do not keep trends** - trends are not stored.\\ //Note//: Before Zabbix 4.2.5, not keeping trends had to be specified by entering %%"​%%0%%"​%% in the storage period field and it could be overridden by global housekeeper settings (now it cannot).\\ **Storage period** - specify the duration of keeping aggregated (hourly min, max, avg, count) history in the database (1 day to 25 years). Older data will be removed by the housekeeper. Stored in seconds.\\ [[:​manual/​appendix/​suffixes|Time suffixes]] are supported, e.g. 24h, 1d. [[:​manual/​config/​macros/​usermacros|User macros]] are supported.\\ The //Storage period// value can be overridden globally in //​Administration -> General -> [[manual:​web_interface:​frontend_sections:​administration:​general#​housekeeper|Housekeeper]]//​.\\ If a global overriding setting exists, a green {{manual:​config:​info.png|}} info icon is displayed. If you position your mouse on it, a warning message is displayed, e. g. //​Overridden by global housekeeper settings (7d)//.\\ //Note:// Keeping trends is not available for non-numeric data - character, log and text.\\ See also [[:​manual/​config/​items/​history_and_trends|History and trends]]. ​ | |//Trend storage period// ​ |Select either:\\ **Do not keep trends** - trends are not stored.\\ //Note//: Before Zabbix 4.2.5, not keeping trends had to be specified by entering %%"​%%0%%"​%% in the storage period field and it could be overridden by global housekeeper settings (now it cannot).\\ **Storage period** - specify the duration of keeping aggregated (hourly min, max, avg, count) history in the database (1 day to 25 years). Older data will be removed by the housekeeper. Stored in seconds.\\ [[:​manual/​appendix/​suffixes|Time suffixes]] are supported, e.g. 24h, 1d. [[:​manual/​config/​macros/​usermacros|User macros]] are supported.\\ The //Storage period// value can be overridden globally in //​Administration -> General -> [[manual:​web_interface:​frontend_sections:​administration:​general#​housekeeper|Housekeeper]]//​.\\ If a global overriding setting exists, a green {{manual:​config:​info.png|}} info icon is displayed. If you position your mouse on it, a warning message is displayed, e. g. //​Overridden by global housekeeper settings (7d)//.\\ //Note:// Keeping trends is not available for non-numeric data - character, log and text.\\ See also [[:​manual/​config/​items/​history_and_trends|History and trends]]. ​ |