Technical
Lynx Connectors - Zabbix
Operational Zabbix connector - monitored hosts, active problems by severity, and availability over a window - for status pages and ops dashboards.
lynx_connector_zabbix
· v19.0.1.0.0
· Standard
Beta
What this solves
Lynx Connectors - Zabbix
Registers a zabbix connector type with the Lynx connector framework and answers the operational reads a status page needs: which hosts are monitored, what problems are open right now and how severe they are, and availability computed per host over a window from problem event durations.
Authentication is an API token (Users > API tokens on Zabbix 5.4+) or a username and password. Store the token in Credential Secret and point Endpoint URL at the frontend, for example https://zabbix.example.com/api_jsonrpc.php. config_json.host_group narrows every pull to one host group.
Key Features
Zabbix connector type - JSON-RPC against the frontend endpoint with either an API token or a username and password login, across the 5.4-7.x auth range.
Host inventory - monitored hosts with interfaces, groups and tags.
Active problems - open problems by severity, with acknowledgement state and the triggering host, for mapping to component status.
Availability - uptime per host over the period from problem event durations, counting average-and-above severities as outages.
Host-group scoping - config_json.host_group limits every pull.
Integrates With
lynx_connectors - registers under the shared framework and reuses its REST client.
lynx_status_page - a status source maps a host or host group to a component and translates problem severity into a component status.
Depends on
Try Lynx Connectors - Zabbix on your team.
Free trial, no credit card. Talk to sales when you're ready.