I am evaluating Zabbix to replace an aging Nagios/Custom solution. We monitor about 200+ end points with 10-30 metrics per end-point. Setup was easy. Thanks.
I have auto-recovery scripts working for a couple of simple services (e..g imap, httpd, etc). The basic functionality is working well on our few test nodes.
The next step is that we want to integrate with our ticketing system (proprietary) with open/close capabilities.
I can see how we can easily create the ticket with the remote command action. We can use curl and some marcos to open the ticket via the helpdesk API.
However, I don't see where we can capture the helpdesk API response and associate it with a specific event in Zabbix. The helpdesk returns a ticket ID that must be included in any future ticket updates.
Can Zabbix trap this return value as a marco and then use it on a future action?
The example workflow would be something as follows:
1) Service fails (e.g. apache, redis, email, etc)
2) Stage 1 autorecovery fails (e.g. running simple service restart)
3) Severity escalates
4) Ticket created in ticketing system via remote command (e.g. curl call to api). Helpdesk API returns Ticket ID. Zabbix records this as a marco for future actions.
5) Secondary auto-recovery tools or tech fixes the problem
6) Ticket is closed vi remote command. (e.g. curl post to helpdesk using the ticketid, host ip, and status).
I know we could write middleware to associate the zabbix event id with the ticket id but we are trying to avoid any middleware.
I have auto-recovery scripts working for a couple of simple services (e..g imap, httpd, etc). The basic functionality is working well on our few test nodes.
The next step is that we want to integrate with our ticketing system (proprietary) with open/close capabilities.
I can see how we can easily create the ticket with the remote command action. We can use curl and some marcos to open the ticket via the helpdesk API.
However, I don't see where we can capture the helpdesk API response and associate it with a specific event in Zabbix. The helpdesk returns a ticket ID that must be included in any future ticket updates.
Can Zabbix trap this return value as a marco and then use it on a future action?
The example workflow would be something as follows:
1) Service fails (e.g. apache, redis, email, etc)
2) Stage 1 autorecovery fails (e.g. running simple service restart)
3) Severity escalates
4) Ticket created in ticketing system via remote command (e.g. curl call to api). Helpdesk API returns Ticket ID. Zabbix records this as a marco for future actions.
5) Secondary auto-recovery tools or tech fixes the problem
6) Ticket is closed vi remote command. (e.g. curl post to helpdesk using the ticketid, host ip, and status).
I know we could write middleware to associate the zabbix event id with the ticket id but we are trying to avoid any middleware.