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

Docs/specs/ZBXNEXT-584

From Zabbix.org
Jump to: navigation, search

Multiple server support for active checks

ZBXNEXT-584

Status: Draft

Summary

Zabbix agent currently supports only one server in active mode - first host from the Server configuration parameter is used. This will be extended to support reporting to multiple Zabbix servers.

Specification

Zabbix agent will be extended and will support reporting to multiple servers in parallel. For each active server, a new active item process will be created. Each process will work with one server in an independent fashion. For the purpose of specifying multiple servers a new configuration parameter will be introduced. Behaviour will be different in the 1.8 implementation and 2.0 implementation.

Active items are retrieved from each server independently and verified independently. Values for items are sent only to the host that provided their configuration.

Details

1.8 implementation
  • A new configuration parameter is added: ServerActive
  • If ServerActive is specified, Server is not used for active checks, only for passive checks
  • If ServerActive is not specified, Server is used same as before, that is, first host is used for active checks
  • If Zabbix agent can't parse some part of the addresses, it will refuse to start up with a message "error in ServerActive option at position <pos>", printing out the character position where the problematic content starts
    • If an address is specified twice in ServerActive, agent will refuse to start up with an additional message 'address "host:port" specified more than once'
  • ServerActive is a comma-separated list of host:port pairs
    • Port for each entry is optional. If the port is not specified, ServerPort port is used. If ServerPort is not specified, default port is used
    • IPv6 addresses must be enclosed in square brackets if port for that host is specified
    • Example entry: ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[::1]
2.0 implementation
  • A new configuration parameter is added: ServerActive
  • Configuration parameters DisablePassive and DisableActive should be removed
  • A configuration parameter StartAgents should accept 0
  • Server is not used for active checks, only for passive checks even if ServerActive is not specified
  • If Zabbix agent can't parse some part of the addresses, it will refuse to start up with a message "error in ServerActive option at position <pos>", printing out the character position where the problematic content starts
    • If an address is specified twice in ServerActive, agent will refuse to start up with an additional message 'address "host:port" specified more than once'
  • ServerActive is a comma-separated list of host:port pairs
    • Port for each entry is optional. If the port is not specified, default port is used
    • IPv6 addresses must be enclosed in square brackets if port for that host is specified
  • ServerPort parameter is removed
  • Users upgrading to 2.0 agents will have to remove ServerPort variable. If they are using active checks, they will have to list Zabbix server or proxy address in the new ServerActive parameter.
    • Example entry: ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[::1]

API changes

No API changes required

Database changes

No database changes required