Help in order to clarify some point
Good afternoon everyone, I'm trying to rebuild to better understand the logic of using data in zabbix. can someone tell me if the reasoning I made to better understand how it behaves is wrong?
Zabbix has two types of interrogation:
1.polling
2.trapping.
Both "activate" the use of two types of internal date: history and aggregate functions.
-History: it is needed to calculate the history of each item or trigger
-aggregate functions: they are a sort of items that aggregate and combine values from other items example the cpu load of a group of hosts we are querying
They are applied on the host through the template which is composed of:
applications
item
trigger
graphical .
Item defines a single control or performance and contains the trigger which is a logical representation representing the state of the system.
These operations write within the history but also creating the trend so we will have history that is split in the trend ------> thes are the the two ways of storing collected data in Zabbix.
History keeps each collected value
Trends keep averaged information on hourly basis
While keeping shorter history, still be able to review older data in graphs, as graphs will use trend values for displaying older data
For example, if I have an ICMP module on a router, does the raw data read the history data? It is natural that to make a graph he uses the trend to check for any errors on the internet line instead he reads from the history.
the point is also to understand how zabbix, however, distinguishes or works on these values by cleaning the set parameters with housekeeper and understanding the real difference between raw data and aggregated data.
I certainly did something wrong in reconstructing the situation.
but I would like to understand the data writing logic because I am creating a new server and I would like it to be as lean as possible but understanding only the important data and the differences of how zabbix writes to the database
Zabbix has two types of interrogation:
1.polling
2.trapping.
Both "activate" the use of two types of internal date: history and aggregate functions.
-History: it is needed to calculate the history of each item or trigger
-aggregate functions: they are a sort of items that aggregate and combine values from other items example the cpu load of a group of hosts we are querying
They are applied on the host through the template which is composed of:
applications
item
trigger
graphical .
Item defines a single control or performance and contains the trigger which is a logical representation representing the state of the system.
These operations write within the history but also creating the trend so we will have history that is split in the trend ------> thes are the the two ways of storing collected data in Zabbix.
History keeps each collected value
Trends keep averaged information on hourly basis
While keeping shorter history, still be able to review older data in graphs, as graphs will use trend values for displaying older data
For example, if I have an ICMP module on a router, does the raw data read the history data? It is natural that to make a graph he uses the trend to check for any errors on the internet line instead he reads from the history.
the point is also to understand how zabbix, however, distinguishes or works on these values by cleaning the set parameters with housekeeper and understanding the real difference between raw data and aggregated data.
I certainly did something wrong in reconstructing the situation.
but I would like to understand the data writing logic because I am creating a new server and I would like it to be as lean as possible but understanding only the important data and the differences of how zabbix writes to the database