---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Zabbix connector instance value parameters

# Zabbix connector instance value parameters {#ariaid-title1}

* Release version: Yokohama
* 
* Updated March 28, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The following table displays the Zabbix connector instance value parameters that you can fill in, as needed, when creating a Zabbix connector instance.
{#zabbix-connector-instance-value-parameters__table_lbn_djz_zbc__entry__2}

| Parameter | Description |
|-|-|
| api_endpoint_suffix | Set this value based on your Zabbix server web interface installation: <https://www.zabbix.com/documentation/current/en/manual/installation/frontend#welcome-screen> Default value: /zabbix/api_jsonrpc.php \[For Apache Server\] |
| debug | Set to true to enable debug logs. Default value: false |
| enable_batch_processing | If batch processing is enabled, metrics details are fetched in batch with 1000 (can be altered by setting appropriate value to - 'max_hosts_per_batch' parameter) hosts per batch. Default value: false |
| groupids | Provide the host group IDs. These IDs will be used to fetch metrics from the hosts attached to the specified groups. This applies only if `enable_batch_processing` is set to true. |
| logPayloadForDebug | Determines whether to print the raw log payload. Set to **true** only for debugging purposes, as printing the raw payload quickly fills up the MID Server logs. Default value: false |
| max_fetch_interval_min | Configured from the 'max_fetch_interval_min' parameter: If the time exceeds 'max_fetch_interval_min', fetching starts from 'max_fetch_interval_min' before the current time; for an INITIAL run without 'lastMetricSignature', the time is set to 'max_fetch_interval_min' before the current time. Default value: 180 minutes |
| max_hosts_per_batch | If batch processing is enabled, metrics details are fetched in batch with 1000 (can be altered by setting appropriate value to - 'max_hosts_per_batch' parameter) hosts per batch. Default value: 1000 |
| offset_min | Specifies the time offset in minutes for adjusting the fetch start time relative to the current time. Default: 5 minutes |
| port | Port number for the Zabbix server to connect to. Default value: empty |
| protocol | Protocol to use when connecting to the Zabbix server. Default value: http |
| with_triggers | It will fetch the trigger information. Default value: false |
[Table 1. Connector instance value parameters]

{#zabbix-connector-instance-value-parameters__table_lbn_djz_zbc}  
Note:  
When monitoring a large number of hosts in Zabbix, fetching massive metric data can impact performance and cause API timeouts; enabling batch processing (enable_batch_processing = true) mitigates this by fetching metrics in batches (default: 1000 hosts, configurable via max_hosts_per_batch), though it increases network calls and must be used when monitoring 10,000+ hosts or facing performance issues.