Zabbix Documentation 4.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:history_and_trends

Differences

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

Link to this comparison view

Next revision
Previous revision
manual:config:items:history_and_trends [2014/09/25 14:42]
sasha Page moved from 2.4:manual:config:items:history_and_trends to manual:config:items:history_and_trends
manual:config:items:history_and_trends [2019/03/07 09:04] (current)
martins-v dependent items are updated with history at '0'
Line 1: Line 1:
-==== - #3 History and trends ====+==== 3 History and trends ====
  
 === Overview === === Overview ===
Line 11: Line 11:
 You can set for how many days history will be kept:  You can set for how many days history will be kept: 
  
-  * in the item properties form+  * in the item properties ​[[:​manual/​config/​items/​item|form]]
   * when mass-updating items   * when mass-updating items
-  * when [[:2.4/manual/web_interface/frontend_sections/administration/general#​housekeeper|setting up]] Housekeeper ​tasks+  * when [[manual:web_interface:frontend_sections:administration:general#​housekeeper|setting up]] housekeeper ​tasks
  
-Any older data will be removed by the Housekeeper.+Any older data will be removed by the housekeeper.
  
 The general strong advice is to keep history for the smallest possible number of days and that way not to overload the database with lots of historical values. The general strong advice is to keep history for the smallest possible number of days and that way not to overload the database with lots of historical values.
Line 21: Line 21:
 Instead of keeping a long history, you can keep longer data of trends. For example, you could keep history for 14 days and trends for 5 years. ​ Instead of keeping a long history, you can keep longer data of trends. For example, you could keep history for 14 days and trends for 5 years. ​
  
-You can get a good idea of how much space is required by history versus trends data by referring to the [[:2.4/manual/installation/requirements#​database_size|database sizing page]].+You can get a good idea of how much space is required by history versus trends data by referring to the [[manual:installation:requirements#​database_size|database sizing page]].
  
 While keeping shorter history, you will still be able to review older data in graphs, as graphs will use trend values for displaying older data. While keeping shorter history, you will still be able to review older data in graphs, as graphs will use trend values for displaying older data.
  
-<​note>​If history is set to '​0', ​Zabbix ​will only be able to calculate triggers that check the last valueHistorical values would not be stored in the database at all, except for the last value for the item itself.</​note>​ +<​note ​important>If history is set to '​0', ​the item will update ​only dependent items and inventoryNo trigger functions will be evaluated.</​note>​ 
 +<note tip>As an alternative way to preserve history consider to use [[manual/​config/​items/​loadablemodules#​providing_history_export_callbacks|history export]] functionality of loadable modules.</​note>​
 === Keeping trends === === Keeping trends ===
  
Line 32: Line 32:
  
 You can set for how many days trends will be kept:  You can set for how many days trends will be kept: 
-  * in the item properties form+  * in the item properties ​[[:​manual/​config/​items/​item|form]]
   * when mass-updating items   * when mass-updating items
   * when setting up Housekeeper tasks   * when setting up Housekeeper tasks
  
-Trends usually can be kept for much longer than history. Any older data will be removed by the Housekeeper.+Trends usually can be kept for much longer than history. Any older data will be removed by the housekeeper. 
 + 
 +Zabbix server accumulates trend data in runtime in the trend cache, as the data flows in. Server flushes trends into the database (where frontend can find them) in these situations:​ 
 +  * a new hour has started and server receives a new value for the item; 
 +  * a new hour is about to end in less than 5 minutes (no new values) 
 +  * server stops 
 + 
 +To see trends on a graph you need to wait at least to the beginning of the next hour (if item is updated frequently) and at most to the end of the next hour (if item is updated rarely), which is 2 hours maximum. 
 + 
 +When server flushes trend cache and there are already trends in the database for this hour (for example, server has been restarted mid-hour), server needs to use update statements instead of simple inserts. Therefore on a bigger installation if restart is needed it is desirable to stop server in the end of one hour and start in the beginning of the next hour to avoid trend data overlap. 
 + 
 +History tables do not participate in trend generation in any way.
  
-<​note>​If trends are set to '​0',​ Zabbix server does not calculate or store trends at all.</​note>​+<​note ​important>If trends are set to '​0',​ Zabbix server does not calculate or store trends at all.</​note>​
  
-<​note>​The trends are calculated and stored with the same data type as the original values. As the result the average value calculations of unsigned data type values are rounded and the less the value interval is the less precise the result will be. For example if item has values 0 and 1, the average value will be 0, not 0.5.+<​note>​The trends are calculated and stored with the same data type as the original values. As result the average value calculations of unsigned data type values are rounded and the less the value interval is the less precise the result will be. For example if item has values 0 and 1, the average value will be 0, not 0.5.
  
 Also restarting server might result in the precision loss of unsigned data type average value calculations for the current hour.</​note>​ Also restarting server might result in the precision loss of unsigned data type average value calculations for the current hour.</​note>​