Monitoring that generates no action is just decoration. Integrating Zabbix with GLPI turns alerts into traceable tickets with an owner, SLA and history.
Why integrate
- Alerts become tickets with a number, owner and SLA
- Elimination of ignored alerts (emails nobody reads)
- Traceability: incident history per monitored asset
- Metrics: time between detection and resolution
Integration methods
Option A: Automations Module (NexTool)
The simplest path. Configure a webhook in Zabbix that sends data to the Automations module endpoint. In NexTool, map the Zabbix fields to GLPI fields using JSONPath.
Option B: GLPI REST API
Configure a Media Type in Zabbix (JavaScript webhook) that calls the GLPI API directly to create tickets.
Option C: External script
A Python/Bash script that receives Zabbix alerts and calls the GLPI API. More flexible, but requires maintenance.
Configuration via NexTool Automations
- In GLPI, activate the Automations module and create a webhook receiver
- In Zabbix, create a Media Type of Webhook type pointing to the endpoint
- Configure the Action in Zabbix to send data to the webhook when triggers fire
- In NexTool, map: host → asset, trigger → title, severity → priority
Suggested data for the ticket
- Title: [Zabbix] {TRIGGER.NAME} - {HOST.NAME}
- Description: Host: {HOST.NAME}, IP: {HOST.IP}, Trigger: {TRIGGER.NAME}, Severity: {TRIGGER.SEVERITY}
- Priority: mapped from Zabbix severity
- Category: "Monitoring" or "Infrastructure"
