Overview

Zabbix monitors your clients’ servers, network devices and services: it collects values such as CPU, disk and ping, and raises a problem when a trigger fires. Connect your Zabbix server to Neo once, at the MSP level, with its address and an API token.

​

What Neo can do with Zabbix

With the access you choose, Neo can also change hosts, templates, items, triggers, macros, users and other Zabbix settings. Some changes always ask a technician first, under every access profile, such as changing authentication, a role or a user group, deleting a host, or storing a credential: the full list.

​

Your clients in Zabbix

Zabbix has no client object of its own: you group hosts by client in host groups (such as Customers/Acme) or with tags. Neo finds a client’s hosts by searching host group names and tags, so it works with the naming you already use. There is no Organization Mapping tab for Zabbix.

​

What Neo never does

• Create an API token or read a token’s secret, or start a Zabbix session.
• Export or import a Zabbix configuration. An export can carry passwords Neo cannot remove, and an import makes many changes at once that Neo cannot check one by one.
• Clear an item’s history.

Neo also removes the fields Zabbix keeps credentials in (passwords, SNMP communities and passphrases, pre-shared keys, credential headers, HTTP request bodies, and the user name and password in a URL) from every Zabbix answer before an agent sees it. Text you typed elsewhere, such as a script’s command or a text macro, reaches the agent as written, so keep secrets in secret macros.

​

Next steps