Information flow in Zabbix
Information flow in Zabbix
We have now configured various things in the Zabbix frontend, including data gathering (Item), threshold definition (Trigger), and instructions on what to do if a threshold is exceeded (Action). But how does it all work together? The flow of information between Zabbix entities can be non-obvious at first glance. Let's look at a schematic showing how the pieces go together:
A trigger can also be in the UNKNOWN state. This happens if there is not enough data to determine the current state. As an example, computing the average value for the past 5 minutes when there's no data for the past 10 minutes will make the trigger go into the UNKNOWN state. Events that cause a change to or from the UNKNOWN state do not match normal action conditions.