Collect host and user inventory as read-only observability compliance evidence through the self-hosted Zabbix JSON-RPC API. Note: Zabbix API is a single JSON-RPC endpoint, not REST resource paths; older Zabbix versions expect the auth token inside the request body/params, while newer versions (6.4+) accept a Bearer auth header -- confirm the customer Zabbix version before configuring the generic connector auth header.
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
The exact Zabbix API endpoints called once connected. All read-only GET requests unless noted.
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
Required
Optional
Zabbix evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Get a guided demo, or start by scanning any domain for free.