Zabbix Documentation 2.4

2.23.04.0 (current)In development:4.2 (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 [2016/09/23 07:45]
martins-v realistic values for 'year' in 'log time format'
manual:config:items:item [2018/06/29 08:12] (current)
martins-v simple change discards negative values
Line 29: Line 29:
 |//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]]. ​ |
-|//Store value// ​ |**As is**  - no pre-processing\\ **Delta (speed per second)** - evaluate value as (**value**-**prev_value**)/​(**time**-**prev_time**),​ where\\ //value// - current value\\ //​value_prev//​ - previously received value\\ //time// - current timestamp\\ //​prev_time//​ - timestamp of previous value\\ This setting is extremely useful to get speed per second for a constantly growing value.\\ If current value is smaller than the previous value, Zabbix discards that difference (stores nothing) and waits for another value. This helps to work correctly with, for instance, a wrapping (overflow) of 32-bit SNMP counters.\\ //Note//: As this calculation may produce floating point numbers, it is recommended to set the 'Type of information'​ to //Numeric (float)//, even if the incoming raw values are integers. This is especially relevant for small numbers where the decimal part matters. If the floating point values are large and may exceed the '​float'​ field length in which case the entire value may be lost, it is actually suggested to use //Numeric (unsigned)//​ and thus trim only the decimal part.\\ **Delta (simple change)** - evaluate as (**value**-**prev_value**),​ where\\ //value// - current value\\ //​value_prev//​ - previously received value|+|//Store value// ​ |**As is**  - no pre-processing\\ **Delta (speed per second)** - evaluate value as (**value**-**prev_value**)/​(**time**-**prev_time**),​ where\\ //value// - current value\\ //​value_prev//​ - previously received value\\ //time// - current timestamp\\ //​prev_time//​ - timestamp of previous value\\ This setting is extremely useful to get speed per second for a constantly growing value.\\ If current value is smaller than the previous value, Zabbix discards that difference (stores nothing) and waits for another value. This helps to work correctly with, for instance, a wrapping (overflow) of 32-bit SNMP counters.\\ //Note//: As this calculation may produce floating point numbers, it is recommended to set the 'Type of information'​ to //Numeric (float)//, even if the incoming raw values are integers. This is especially relevant for small numbers where the decimal part matters. If the floating point values are large and may exceed the '​float'​ field length in which case the entire value may be lost, it is actually suggested to use //Numeric (unsigned)//​ and thus trim only the decimal part.\\ **Delta (simple change)** - evaluate as (**value**-**prev_value**),​ where\\ //value// - current value\\ //​value_prev//​ - previously received value\\ This setting can be useful to measure a constantly growing value. If the current value is smaller than the previous value, Zabbix discards that difference (stores nothing) and waits for another value.|
 |//Show value// ​ |Apply value mapping to this item. Value mapping does not change received values, it is for displaying data only.\\ It works with integer items only.\\ For example, "​Windows service states"​.| |//Show value// ​ |Apply value mapping to this item. Value mapping does not change received values, it is for displaying data only.\\ It works with integer items only.\\ For example, "​Windows service states"​.|
 |//Log time format// ​ |Available for items of type **Log** only. Supported placeholders:​\\ ​    * **y**: //Year (1970-2038)//​\\ ​    * **M**: //Month (01-12)//​\\ ​    * **d**: //Day (01-31)//​\\ ​    * **h**: //Hour (00-23)//​\\ ​    * **m**: //Minute (00-59)//​\\ ​    * **s**: //Second (00-59)//​\\ ​    If left blank the timestamp will not be parsed.\\ For example, consider the following line from the Zabbix agent log file:\\ " 23480:​20100328:​154718.045 Zabbix agent started. Zabbix 1.8.2 (revision 11211)."​\\ It begins with six character positions for PID, followed by date, time, and the rest of the line.\\ Log time format for this line would be "​pppppp:​yyyyMMdd:​hhmmss"​.\\ Note that "​p"​ and ":"​ chars are just placeholders and can be anything but "​yMdhms"​. | |//Log time format// ​ |Available for items of type **Log** only. Supported placeholders:​\\ ​    * **y**: //Year (1970-2038)//​\\ ​    * **M**: //Month (01-12)//​\\ ​    * **d**: //Day (01-31)//​\\ ​    * **h**: //Hour (00-23)//​\\ ​    * **m**: //Minute (00-59)//​\\ ​    * **s**: //Second (00-59)//​\\ ​    If left blank the timestamp will not be parsed.\\ For example, consider the following line from the Zabbix agent log file:\\ " 23480:​20100328:​154718.045 Zabbix agent started. Zabbix 1.8.2 (revision 11211)."​\\ It begins with six character positions for PID, followed by date, time, and the rest of the line.\\ Log time format for this line would be "​pppppp:​yyyyMMdd:​hhmmss"​.\\ Note that "​p"​ and ":"​ chars are just placeholders and can be anything but "​yMdhms"​. |