2 Other event sources

Service events

• Problem event - when service status is changed from OK to PROBLEM
• OK event - when service status is changed from PROBLEM to OK

The event contains details of the service state change - when it happened and what the new state is.

Discovery events

Zabbix periodically scans the IP ranges defined in network discovery rules. Frequency of the check is configurable for each rule individually. Once a host or a service is discovered, a discovery event (or several events) are generated.

Zabbix generates the following events:

Active agent auto-discovery events

If configured, active agent autoregistration event is created when a previously unknown active agent asks for checks or if the host metadata has changed. The server adds a new auto-registered host, using the received IP address and port of the agent.

For more information, see the page.

Internal events

Internal events happen when:

• an item changes state from ‘normal’ to ‘unsupported’
• a low-level discovery rule changes state from ‘normal’ to ‘unsupported’
• a low-level discovery rule changes state from ‘unsupported’ to ‘normal’
• a trigger changes state from ‘normal’ to ‘unknown’

Internal events are only created when internal actions for these events are enabled. To stop generation of internal events (for example, for items becoming unsupported), disable all actions for internal events in Alerts → Actions → Internal actions.

If internal actions are disabled, while an object is in the ‘unsupported’ state, recovery event for this object will still be created.

If internal actions are enabled, while an object is in the ‘unsupported’ state, recovery event for this object will be created, even though ‘problem event’ has not been created for the object.