Words and Phrases
Zabbix
The Operations Connector for Zabbix (OpsCx for Zabbix) enables you to establish a link between the Zabbix network monitoring solution and Operations Manager i.
The OpsCx for Zabbix is an add-on for the OpsCx, providing the following Zabbix specific functionality:
- Event synchronization between Zabbix and OMi
- Metric synchronization between Zabbix and OMi
- Topology synchronization between Zabbix and OMi
This functionality enables you to consolidate management data from Zabbix environments into an Operations Manager i solution.
OpsCx for Zabbix is a GenInt-based integration. If you installed other GenInt based connectors, see Installation topic for additional details.
Concepts
The OpsCx for Zabbix is installed on the OpsCx system and uses a Web Service interface to collect the events, metrics, and topology from the Zabbix system. No additional components need to be installed on the Zabbix system.
Event Collection
Zabbix events are collected and processed by the event collector script. The event collector receives events from the Zabbix server through its Web Service interface using the HTTP protocol.
Events are collected from the Zabbix system periodically, using a preset alarm polling interval. By default, the polling interval is set to 60 seconds. In case a poll is not executed as planned, the next poll collects all events that were newly created or changed since the last successful poll.When the collector is started for the first time, existing Zabbix events are collected and forwarded (by default, events from the last 10 days are forwarded).
Event data is mapped to the OMi conform form using a web service policy. The policy also sets the drilldown URL for each event.
| Zabbix event severity | OMi event severitiy |
|---|---|
| Disaster | Critical |
| High | Major |
| Average | Minor |
| Warning | Warning |
| Information | Normal |
Metric Collection
The metric collector runs regularly (by default every 5 minutes) and collects all current Zabbix metrics through the Web Service interface using the HTTP protocol. The metrics are stored on the OpsCx system for further processing by OMi.
Metric data is mapped to the OMi conform form using a web service policy.
Topology Collection
Topology data is collected by the topology collector script that is run regularly (by default, every hour). The topology collector receives data from the Zabbix server through its Web Service interface using the HTTP protocol and forwards it to the OpsCx for further processing. Topology objects are then mapped to the RTSM using the local topology synchronization component provided by the OpsCx.
The topology collector always collects all objects, not just the new or modified ones.
Topology objects are mapped to the RTSM using an XML file policy. The mapping rules map the following CI types:
host_nodeip_address
In addition, the topology self-discovery policy retrieves topology data about the Zabbix integration environment itself. See the following figure for an example.
