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/06/20 13:10]
martins-v value mapping works not only with integers
manual:config:items:item [2020/05/19 11:35] (current)
marinagen Zabbix spelling corrected
Line 26: Line 26:
 |//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).\\ 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 Zabbix ​3.0.0.\\ //Note//: Not available for Zabbix agent active items. ​ |
 |//History storage period\\ (in days)// ​ |Number of days to keep detailed history in the database. Older data will be removed by the housekeeper.\\ Starting with Zabbix 2.2, this value can be overridden globally in //​Administration -> General -> [[manual:​web_interface:​frontend_sections:​administration:​general#​housekeeper|Housekeeper]]//​. If the global setting exists, a warning message is displayed:​\\ {{manual:​config:​override_item.png|}}\\ It is recommended to keep the recorded values for the smallest possible number of days to reduce the size of value history in the database. Instead of keeping 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\\ (in days)// ​ |Number of days to keep detailed history in the database. Older data will be removed by the housekeeper.\\ Starting with Zabbix 2.2, this value can be overridden globally in //​Administration -> General -> [[manual:​web_interface:​frontend_sections:​administration:​general#​housekeeper|Housekeeper]]//​. If the global setting exists, a warning message is displayed:​\\ {{manual:​config:​override_item.png|}}\\ It is recommended to keep the recorded values for the smallest possible number of days to reduce the size of value history in the database. Instead of keeping 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\\ (in days)// ​ |Keep aggregated (hourly min, max, avg, count) detailed history for N days in the database. Older data will be removed by the housekeeper.\\ Starting with Zabbix 2.2, this value can be overridden globally in //​Administration -> General -> [[manual:​web_interface:​frontend_sections:​administration:​general#​housekeeper|Housekeeper]]//​. If the global setting exists, a warning message is displayed:​\\ {{manual:​config:​override_trends.png|}}\\ //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\\ (in days)// ​ |Keep aggregated (hourly min, max, avg, count) detailed history for N days in the database. Older data will be removed by the housekeeper.\\ Starting with Zabbix 2.2, this value can be overridden globally in //​Administration -> General -> [[manual:​web_interface:​frontend_sections:​administration:​general#​housekeeper|Housekeeper]]//​. If the global setting exists, a warning message is displayed:​\\ {{manual:​config:​override_trends.png|}}\\ //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]]. ​ |