Zabbix Platform
About
Zabbix is software that monitors numerous parameters of a network as well as the health and integrity of servers.
This HTTP connector connects to the Zabbix API to retrieve data from the Zabbix platform. The Zabbix API is a web-based API that is shipped as part of the web frontend. It uses the JSON-RPC 2.0 protocol.
This connector will export different connectors based on the retrieved hosts from the API. For more information on the device, refer to Zabbix's documentation.
Configuration
Connections
HTTP Connection
This connector uses an HTTP connection and requires the following input during element creation:
HTTP CONNECTION:
- IP address/host: The polling IP or URL of the destination.
- IP port: The IP port of the destination (default: 443).
- Device address: The bus address of the device. If the proxy server has to be bypassed, specify BypassProxy.
Initialization
To be able to retrieve data from the API, specify a Username and Password on the Configuration page.
Web Interface
The web interface is only accessible when the client machine has network access to the product.
How to use
General
The General page presents a tree view that allows you to drill down from a Host Group to an individual host and then inspect not only the host properties but also its Triggers and Items.
Hosts
This page presents Zabbix's Host Group and Host information in two tables, along with tag filtering options, allowing you to quickly refine the list of hosts by applying tag-based filtering.
The Host Group table shows a list of host groups, identifying the group ID and name. In this table, you can also enable and disable the polling for each host group.
The Host table shows the hosts belonging to the enabled groups, providing the operator with a consolidated view of all relevant host metadata. For each host, the table displays the host ID, name, status, and group. Other properties such as Proxy Host, IPMI and Maintenance fields are also shown.
Finally, this page also includes a button that opens the Configure DVEs subpage, allowing you to enable or disable DVE instantiation per host.
Triggers
This page provides a comprehensive view of active triggers within the monitored environment. The table lists all triggers, each represented by its Trigger ID, Trigger Description, associated Host, Priority, and Value.
Items
The Item Table lists the monitoring items configured for the monitoring hosts. Each row represents an item with the name assigned to the check, and its description, which explains what the item monitors. The table also shows the last collected value and the timestamp of when it was last updated.
Events
On the Events page, the table lists all events for the monitored hosts, displaying the related host and scope. Each row represents a specific event created (e.g., generated via trigger). The table displays the event ID, the source, the object and its ID, and the timestamp of when the issue occurred.
The properties indicating the current state (e.g., OK, Problem), if the event has been acknowledged, and its severity are also shown in the Events table.
Correlations
The Correlations table lists correlation rules that allow Zabbix to compare multiple events and apply logic, such as closing related problems, suppressing noise, or linking events across hosts or services. The table includes columns for the Correlation ID, the status, the name of the rule, its description, and the filter conditions.
Problems
On the Problems page, you can define for which period you want the records to be polled. The Problems table will then list all currently active or historical problems. Each entry represents a specific problem state detected by Zabbix, displaying details such as the event ID, a description of the trigger, the host where the issue occurred, and the timestamp when the problem was generated. The table also includes the source and object.
Configuration
The Configuration page displays the API version and allows you to define the username, password, and API URL required for connecting to the Zabbix Platform and retrieving data through the API.