Documentation
Zabbix
Connecting REAP to Zabbix (opens in a new tab): prerequisites, permissions, setup, what is read and written, troubleshooting.
Overview
Planned, not available today: REAP would read Zabbix (opens in a new tab) problems and metrics as evidence. Today, incidents Zabbix raises in ServiceNow (opens in a new tab) or Jira (opens in a new tab) reach REAP through the ITSM.
Status Planned Not available today and without a date. The sections below describe the design, so a reviewer can see what the integration would read and write; tell us if you need it.
Prerequisites
- Zabbix (opens in a new tab) server with API access
- API user with read-only role
Permissions requested
| Scope | Permission | Why |
|---|---|---|
| Read | Problems, hosts, items, history via the Zabbix (opens in a new tab) API | Evidence and prioritization |
Setup
- Create the API user and token.
- In REAP: Integrations → Zabbix (opens in a new tab) → URL, token; select host groups.
- Test with a recent problem.
What REAP reads
- Problems, host status, item history in scope
What REAP writes
- Nothing
Troubleshooting
| Symptom | Likely cause | Check |
|---|---|---|
| Authentication failed | Token expired or user disabled | Regenerate token |
Changelog
- September 2026 · page created (draft).
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai