> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> What the Zabbix monitoring integration brings to your Neo Agent setup

Zabbix monitors your clients' servers, network devices and services: it collects values such as CPU, disk and ping, and raises a problem when a trigger fires. Connect your Zabbix server to Neo once, at the MSP level, with its address and an API token.

## What Neo can do with Zabbix

<CardGroup cols={2}>
  <Card title="The host behind a ticket" icon="server">
    Find the host by name, IP address or the client's host group. Read whether Zabbix can reach it, its open problems, and which templates monitor it.
  </Card>

  <Card title="Is it really down?" icon="heart-pulse">
    Tell a host that is down from a stopped Zabbix agent or an offline proxy, from ping, agent availability and the proxy's last contact.
  </Card>

  <Card title="Latest data and history" icon="chart-line">
    Read the latest CPU, memory, disk or any other value, and its history or hourly trend, to see when a problem started.
  </Card>

  <Card title="Acknowledge and maintenance" icon="bell-slash">
    Acknowledge, comment on and close a problem with the ticket number, put a host in maintenance for planned work, and run a script you defined in Zabbix.
  </Card>
</CardGroup>

With the access you choose, Neo can also change hosts, templates, items, triggers, macros, users and other Zabbix settings. Some changes always ask a technician first, under every access profile, such as changing authentication, a role or a user group, deleting a host, or storing a credential: [the full list](/integrations/zabbix/connecting-to-neo#changes-that-always-ask-a-technician).

## Your clients in Zabbix

Zabbix has no client object of its own: you group hosts by client in host groups (such as `Customers/Acme`) or with tags. Neo finds a client's hosts by searching host group names and tags, so it works with the naming you already use. There is no Organization Mapping tab for Zabbix.

## What Neo never does

* Create an API token or read a token's secret, or start a Zabbix session.
* Export or import a Zabbix configuration. An export can carry passwords Neo cannot remove, and an import makes many changes at once that Neo cannot check one by one.
* Clear an item's history.

Neo also removes the fields Zabbix keeps credentials in (passwords, SNMP communities and passphrases, pre-shared keys, credential headers, HTTP request bodies, and the user name and password in a URL) from every Zabbix answer before an agent sees it. Text you typed elsewhere, such as a script's command or a text macro, reaches the agent as written, so keep secrets in secret macros.

## Next steps

<Card title="Connect Zabbix" icon="plug" href="/integrations/zabbix/connecting-to-neo">
  Create an API token in Zabbix and save it in Neo with your Zabbix address.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.