can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation schedule stored in a database • configurable history • built-in housekeeping procedure Easy configuration • add monitored devices as hosts • hosts are picked up for monitoring, once in the database • apply templates to Zabbix for mass manipulations, 3rd party software integration and other purposes. Permissions system • secure user authentication • certain users can be limited to certain views Full featured and

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909 13 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation schedule stored in a database • configurable history • built-in housekeeping procedure Easy configuration • add monitored devices as hosts • hosts are picked up for monitoring, once in the database • apply templates

• very simple configuration • Centralised monitoring system. All information (configuration, performance data) is stored in relational database • high-level service tree • very easy setup • support 1 For version 1.8 • All hosts now are required to belong to at least one group. • CPU index for system.cpu.util key on Linux now starts with 0. • Key vfs.fs.size returns data in bytes for all operating perf renamed to ntp. Old syntax is still sup- ported. • Trying to run IPv6-enabled daemon on a system without IPv6 support fail: 8 Listener failed with error: socket() for [[(null)]:10051] failed with

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation schedule stored in a database • configurable history • built-in housekeeping procedure Easy configuration • add monitored devices as hosts • hosts are picked up for monitoring, once in the database • apply templates

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062 13 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation schedule stored in a database • configurable history • built-in housekeeping procedure Easy configuration • add monitored devices as hosts • hosts are picked up for monitoring, once in the database • apply templates

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123 14 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation schedule stored in a database • configurable history • built-in housekeeping procedure Easy configuration • add monitored devices as hosts • hosts are picked up for monitoring, once in the database • apply templates

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1542 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation schedule stored in a database • configurable history • built-in housekeeping procedure Easy configuration • add monitored devices as hosts • hosts are picked up for monitoring, once in the database • apply templates

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1719 14 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation schedule stored in a database • configurable history • built-in housekeeping procedure Easy configuration • add monitored devices as hosts • hosts are picked up for monitoring, once in the database • apply templates

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1352 12 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation schedule stored in a database • configurable history • built-in housekeeping procedure Easy configuration • add monitored devices as hosts • hosts are picked up for monitoring, once in the database • apply templates

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000 13 Database error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . can define very flexible problem thresholds, called triggers, referencing values from the backend database Highly configurable alerting • sending notifications can be customized for the escalation schedule stored in a database • configurable history • built-in housekeeping procedure Easy configuration • add monitored devices as hosts • hosts are picked up for monitoring, once in the database • apply templates