Zabbix Zabbix

Collect your monitored hosts inventory and alerts from Zabbix

The Zabbix connector allows you to centralize your monitored hosts inventory, alerts and performance metrics from your Zabbix platform.

Objective

The Zabbix connector retrieves the following information:

  • Monitored hosts inventory
  • Active alerts and triggers
  • Performance metrics and historical data

Prerequisites

  • Access to Zabbix with API rights
  • Zabbix API key OR username/password credentials

Information to provide in OverView

FieldDescription
API URLURL of the Zabbix API (e.g., https://zabbix.example.com/api_jsonrpc.php)
API KeyZabbix API key (optional if username/password provided)
UsernameZabbix username (optional if API Key provided)
PasswordZabbix password (optional if API Key provided)

Note: At minimum, provide the API URL plus either an API Key or a Username/Password combination.

Procedure

Option 1: Use an API token (Zabbix 6.0+)

  1. Log in to Zabbix with an administrator account.
  2. Go to Administration > General > API tokens.
  3. Click Create API token.
  4. Name the token OverView with appropriate expiration.
  5. Select the required permissions:
    • Read access to hosts
    • Read access to alerts/triggers
    • Read access to history
  6. Click Create and copy the generated token.

Option 2: Use username/password

  1. Create a dedicated user in Zabbix:
    • Username: oversoc-api
    • Password: Generate a strong password
  2. Assign the appropriate role with read permissions.
  3. Record the credentials.

Configure the connector in OverView

  1. In OverView, go to Data Sources Settings > Sources.
  2. Select Zabbix and click Configure.
  3. Fill in the fields:
    • API URL: Complete URL of the Zabbix API
    • API Key: Generated API token (if used)
    • Username: Zabbix username (if used)
    • Password: Zabbix password (if used)
  4. Click Test Connection to verify the connection.
  5. Click Save Configuration.

View Zabbix API tokens documentation

Required Permissions

Minimum required permissions:

  • Read hosts and configurations
  • Read alerts and triggers
  • Access to historical data and metrics
  • Read performance information
Alternative: file import through DropPoint

The API access described above is the recommended method for this connector. Where it is not available (a segregated network, a version or licence without API, an export you already produce), OverView accepts file exports, to be uploaded to the bucket dedicated to Zabbix.

Where do the files go?

Bucket : s3://zabbix/

Example : s3://zabbix/export.csv

The procedure is described in the OverView DropPoint guide: generating credentials, configuring the client, then sending files from the OverView web interface, the AWS CLI or an SDK. Its examples come pre-filled with this bucket when you follow this link.