See www.zabbix.com for the official Zabbix site.

Docs/specs/ZBXNEXT-341

From Zabbix.org
Jump to: navigation, search

New concept for UNKNOWN events

ZBXNEXT-341

Status: v1.0

Owner: Alexei, Sasha

Reasoning

A monitoring system should produce two types of events: problem and recovery. Zabbix currently generates also 'unknown' events, which is quite confusing to Zabbix users. Why shall we tell to the world that Zabbix is unable to execute certain checks or recalculate trigger expression? It should be considered as an internal event, i.e. event not exposed to end users or external systems.

It will also bring a number of short- and long-term benefits:

  1. No confusion related to the unknown events. List of events will be much cleaner: a single OK instead of OK->UNKNOWN->OK.
  2. Same logic (no unknowns) for events and IT Services
  3. Only Zabbix server will produce new events, GUI won't do it anymore.
    1. Performance of GUI for host, trigger and item related operation will be improved
  4. Zabbix Server will not generate unknown events on startup. Server startup time will be significantly improved.
  5. Zabbix Server will not use IDS table for generation of new events, which will lead to much better performance.
    1. No deadlocks related to IDS (see also 1.)

Overview

Two types of trigger based events will be generated: PROBLEM and OK. It means that only significant events will be produced.

A new type of events will be introduced: internal events. Internal events will be used to notify Zabbix administrators about configuration related issues, for example, unable to calculate trigger value, item goes to not supported state, etc. These events will be visible to administrators only.

Specification (PART 1. Removal of unknown events)

See ZBXNEXT-1574

Specification (PART 2. Internal events)

See ZBXNEXT-1575