Configuring Zabbix Observer jobs
Using the Zabbix Observer functionality, you can load monitored servers and their associated network resources, and then visualize this data as a topology view.
Before you begin
The Zabbix Observer supports Zabbix 4.0.3, 6.0.3 and 6.4.11.
Ensure you have the Zabbix server details to hand, such as the username, password and SSL truststore.
Enabling access to the URL routes
To access the URL routes for the topology Swagger documentation, see the Enabling access to URL routes topic.
About this task
A Zabbix Observer job extracts server information and its associated network resources from Zabbix through REST RPC, and the observer loads and updates the resources and their relationships within the topology service.
You define and start the following job.
Full Topology Upload job By default, Load jobs are one-off, transient jobs that do a full upload of all requested topology data as soon as they are triggered.
You can also run these jobs (again) from the Observer UI, or schedule them to run at set times when configuring them.
Procedure
Define or edit the following parameters, then click Run job to save and run the job.
Encryption requirement: See the Configuring observer jobs security topic for more information.
| Parameter | Action | Details |
|---|---|---|
| Unique ID | Enter a unique name for the job | Required |
| The datacenter of zabbix server | Specify the data center in which the Zabbix instance runs | Required. If more than one, list them (comma-separated). |
| Zabbix server | Enter the Zabbix virtual hostname | Required |
| Zabbix username | Specify the Zabbix username | Required |
| Zabbix password | Specify the Zabbix user password | Required |
| Zabbix SSL certificate | Specify a certificate file name | Required |
| HTTPS truststore file name | Specify the truststore file name. The observer generates the trust store file based on the file name provided. Tip: You can use the observer name as file name (<observer>.jks), for example Zabbix.jks. |
Required. The supported format is JKS and the file is relative to $ASM_HOME/security. |
| TrustStore file password | Specify the truststore password the observer will use to decrypt the HTTPS truststore file. Use a password that conforms to your internal security requirements. | Required |
| Zabbix connection timeout (milliseconds) | Timeout, in ms, when querying the Zabbix REST API | Optional. Default is 5000 (5s). |
| Resources to exclude | List resources by name/regex (seperated by " | "), to be excluded from the topology. By default, virtual network interfaces (veth) are not observed. |
| SSL Validation | Choose whether SSL validation is on or off. Turning off SSL validation will use HTTPS without host verification. | Optional |
| Access scope | Enter text to provide a scope for the resources. Access scope can help map alerts to resources when resources in different scopes share the same parameters, such as matchTokens. | Optional. Tip: You can define access scope for locations, project names, namespaces, etc. |
| Generate debug support file | Set this parameter to 'True' in order to capture the output of the next scheduled job run as a file. This file will be stored with an observer's log files and can be used to debug observer issues, for example at the request of your designated support team, or while using a test environment. For one-off jobs (that is, Load jobs), this parameter reverts to 'False' after the next completed run. To examine the output produced, you can load the generated debug file using the File Observer. | Optional |
| Observer job description | Enter additional information to describe the job | Optional |
| Job schedule | Specify when the job runs | Optional. Load jobs only. |