Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Configure
After installing the OpsCx for Zabbix on the OpsCx host system, execute the following configuration steps:
- Configure the OpsCx for Zabbix. See Configuring the Integration topic.
- Configure the login credentials. See Configuring Login Credentials topic.
- Start the integration services. See Managing the Integration Services topic.
- Import and activate policies in OpsCx. See Importing and Activating the Zabbix Policies topic.
Configuring the Integration
To be able to connect to the Zabbix system and to establish a receiving server on the OpsCx system (needed for subscription mode), you need to set the basic options in the configuration files.
-
Open the appropriate configuration file:
Windows:
%OvDataDir%conf\HPBsmIntZabbix\zabbix_events.conf%OvDataDir%conf\HPBsmIntZabbix\zabbix_metrics.conf%OvDataDir%conf\HPBsmIntZabbix\zabbix_topology.confLinux:
/var/opt/OV/conf/HPBsmIntZabbix/zabbix_events.conf/var/opt/OV/conf/HPBsmIntZabbix/zabbix_metrics.conf/var/opt/OV/conf/HPBsmIntZabbix/zabbix_topology.confThe options are listed in the section
nodes, in the appropriate subsection (sourceorsink), and formatted as:"<option name>" : "<value>", -
Search for the option
zabbix_server_hostnameand set the Zabbix server hostname or IP address.For example:
"zabbix_server_hostname" : "zbxhost1.company.com",
You can set additional options, such as the ports used, number of days for which the old events are collected, the polling interval, and more. For a detailed list of available options for each collector, see Event Collection Options on page 1, Metric Collection Options on page 1, and Topology Collection Options topic.
After you set the hostname, continue with Configuring Login Credentials topic.
You must restart the OpsCx for Zabbix services after any change to the configuration.
Event Collection Options
Windows: %OvDataDir%conf\HPBsmIntZabbix\zabbix_events.conf
Linux: /var/opt/OV/conf/HPBsmIntZabbix/zabbix_events.conf
| Option | Description |
|---|---|
| Section: source | |
|
|
The Zabbix server hostname or IP address. This parameter is required. |
zabbix_server_port
|
The service name or port used to establish the connection with the Zabbix server. The default ports are Default: |
zabbix_server_protocol
|
The protocol used to communicate with Zabbix. You need to change it to Default: |
interval
|
The time (in seconds) to wait after collecting the data Default: |
zabbix_event_timestamp_filename |
Timestamp persistency filename. Default: |
zabbix_event_init_age
|
Maximum age of alerts for the initial run. On the initial run (without having a timestamp file), the integration will fetch alerts with modification timestamp not older than the given age (in minutes). Default: |
|
|
The name of the Lua script which processes events data. Default: |
package-path
|
Additional search path for Lua modules. Default: |
|
|
The host node list used for data output filtering. When a node does not exist in the list, the integration adds it to the list and forwards it.
Otherwise, it forwards the node (or its child, metric, or event data) only if it is present with the index different from The following syntax is used in the file:
Where:
Do not change the Default: |
|
Section: sink |
|
use-ssl
|
If set to Default: |
uri
|
The URI to send the web service request to. The string must not contain the protocol, hostname or port fields but only the URI part of an URL. Default: |
server-name
|
Hostname or IP address of the remote OpsCx host. Default: |
port
|
The service name or port to use for establishing the connection. Default: |
use-persistency
|
If set to true, all incoming messages will first be persisted into a file-based store before sending them to the remote host. It also enables the retry mechanism. Default: |
persistency-dir
|
Directory path, used for the persistence layer. Directory must exist. Default: |
persistency-max-size
|
File size limit (in KB), which needs to be exceeded before the persistence layer starts writing into a new output file. Default: |
persistency-max-files
|
Maximum number of persistence files to keep. Default: |
persistency-prefix
|
Prefix for the persistence files. This will be used for looking up existing persistence files on program start. Default: |
retry-wait
|
Amount of seconds to wait before retrying to send an HTTP request, in case of an error. The retry mechanism requires the parameter Default: |
auth-username
|
Username for authentication against the remote web service endpoint. If |
auth-password
|
Password for the authentication. If |
root-element
|
Name of the XML root element Default: |
use-store
|
The option that, when set to The option is by default not visible in the configuration file and you need to add it to change the value. Default value: |
Metric Collection Options
Windows: %OvDataDir%conf\HPBsmIntZabbix\zabbix_metrics.conf
Linux: /var/opt/OV/conf/HPBsmIntZabbix/zabbix_metrics.conf
| Option | Description |
|---|---|
| Section: source | |
zabbix_server_hostname
|
The Zabbix server hostname or IP address. This parameter is required. |
zabbix_server_port
|
The service name or port used to establish the connection with the Zabbix server. The default ports are Default: |
zabbix_server_protocol
|
The protocol used to communicate with Zabbix. You need to change it to Default: |
|
|
The name of the Lua script which processes events data. Default: |
|
|
Additional search path for Lua modules. Default: |
zabbix-metric-keys
|
Specifies which metrics the integration should try to fetch. See the Zabbix documentation for a list of supported keys. You can find the list at Where Metric keys must be separated by a pipe ( Default:
|
zabbix_metric_timestamp_filename
|
Timestamp persistency filename. Default: |
script-interval
|
Script running interval in seconds. Default: |
|
|
The maximum age of metrics to include (in minutes). Keep this value aligned with the value of the option Default: |
|
|
The host node list used for data output filtering. When a node does not exist in the list, the integration adds it to the list and forwards it.
Otherwise, it forwards the node (or its child, metric, or event data) only if it is present with the index different from The following syntax is used in the file:
Where:
Do not change the Default: |
| Section: sink | |
use-ssl
|
If set to true, the connections will be encrypted using SSL v3 Default: |
uri
|
The URI to send the web service request to. The string must not contain the protocol, hostname, or port fields but only the URI part of an URL. Default: |
server-name
|
Hostname or IP address of the remote OpsCx host. Default: |
|
|
The service name or port to use for establishing the connection. Default: |
|
|
If set to true, all incoming messages will first be persisted into a file-based store before sending them to the remote host. It also enables the retry mechanism. Default: |
|
|
Directory path, used for the persistence layer. Directory must exist. Default: |
persistency-max-size
|
File size limit (in KB), which needs to be exceeded before the persistence layer starts writing into a new output file. Default: |
persistency-max-files
|
Maximum number of persistence files to keep. Default: |
persistency-prefix : |
Prefix for the persistence files. This will be used for looking up existing persistence files on program start. Default: |
retry-wait
|
Amount of seconds to wait before retrying to send an HTTP request, in case of an error. The retry mechanism requires the parameter Default: |
|
|
Username for authentication against the remote web service endpoint. If use-store is set to true, the string specified in this parameter will be used as key for fetching the username from the credential store. |
|
|
The password for authentication. If |
root-element
|
Name of the XML root element. Default: |
use-store
|
The option that, when set to The option is by default not visible in the configuration file and you need to add it to change the value. Default value: |
Topology Collection Options
Windows: %OvDataDir%conf\HPBsmIntZabbix\zabbix_topology.conf
Linux: /var/opt/OV/conf/HPBsmIntZabbix/zabbix_topology.conf
| Option | Description |
|---|---|
|
Section: source |
|
|
|
The Zabbix hostname or IP address. This parameter is required. |
|
|
The service name or port used to establish the connection. The default ports are Default: |
zabbix_server_protocol
|
The protocol used to communicate with Zabbix. You need to change it to Default: |
|
|
The name of the Lua script which processes topology data. Default: |
|
|
The time (in seconds) to wait after re-running the script. Default: |
package-path
|
Additional search path for Lua modules Default: |
|
|
The host node list used for data output filtering. When a node does not exist in the list, the integration adds it to the list and forwards it.
Otherwise, it forwards the node (or its child, metric, or event data) only if it is present with the index different from The following syntax is used in the file:
Where:
Do not change the Default: |
| Section: sink (toposink) | |
filename
|
The XML output filename. Default: |
| Section: processor(zabbixselfdiscoveryprocess) | |
filename
|
The name of the Lua script file. The file must exist and be a valid Lua script Default: |
interval
|
Script running interval in seconds. Default: |
| Section: sink(zabbixselfdiscoverysink) | |
filename
|
Topology self-discovery output file name Default: |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: