Skip to main content
Connect your Zabbix monitoring server so Myrmex can review hosts, problems, and metrics. Myrmex reaches Zabbix over its JSON-RPC API (/api_jsonrpc.php) through a Collector on your network. Every request runs live, on demand — Myrmex returns only what you ask for and copies or stores nothing from Zabbix on its side. Credentials are resolved on your side and never pass through the model.

​
What Myrmex Can Do

Monitor hosts

List hosts and their availability to see what Zabbix is watching.

Review problems

Read current problems and triggers to support alert triage.

Read metrics

Query items and their latest values live and return only what you asked for.

Check server health

Read Zabbix status to confirm the monitoring server is healthy.

​
Before You Start

  • A Collector that can reach the Zabbix frontend over HTTPS (default port 443; self-hosted often uses 80 or 8080). See Collector mode.
  • A Zabbix user with a read role and an API token (API tokens require Zabbix 5.4 or later).

​
Step 1 — Create the Credential in Zabbix

1

Choose or create a user

In Users → Users, use or create an account with a read-only role that can see the hosts and problems Myrmex should monitor.
2

Generate an API token

Go to Users → API tokens, create a token for that user, set an optional expiry, and copy the value (shown only once). Myrmex sends it as a Bearer token to the Zabbix API (/api_jsonrpc.php).
Assign a read-only role so the token can monitor without changing anything in Zabbix.

​
Step 2 — Add the Integration in Myrmex

From the Directory, choose Add Integration → Zabbix, then fill in:

​
Connect

Click Connect to validate the API connection and finish. Zabbix then appears under Environment → Integrations, and you can ask about it in the Workspace or through the Integration Specialist agent.
The API lives at /api_jsonrpc.php on the Zabbix frontend. Point the URL and Port at the frontend the Collector can reach, not the database or server process.