---
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


---

# Solarwinds connector instance value parameters

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

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

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

| Parameter | Description |
|-|-|
| debug | Set to true to enable debug logs. Default value: false |
| max_fetch_interval_in_min | Number of minutes before the current time when the initial metric collection runs. For example, if the value is 180, the connector fetches metrics from the past 180 minutes. Default value: 180 minutes |
| 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 |
| offset | Specifies the time offset in minutes for adjusting the fetch start time relative to the current time. Default: 0 minutes |
| Port | Port number for the Solarwinds server to connect to. Default value: 17774 |
| protocol | Protocol to use when connecting to the Solarwinds server. Default value: https |
[Table 1. Connector instance value parameters]

{#solarwinds-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.