---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Splunk Polling data input configuration fields

# Splunk Polling data input configuration fields {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 Minuten Lesedauer

Description of the fields on the Splunk Polling data input configuration form.

## Basic configuration {#hla-data-input-splunk-polling-ref__section_irq_4cp_mdc}

{#hla-data-input-splunk-polling-ref__table_lgv_scp_mdc__entry__2}

| Field | Description |
|-|-|
| Name | Name of the new data input. This field is required. |
| Description | Description of the data input. |
| Execute on | Option to select whether to use a specific MID Server or a MID Server cluster. This field is required. |
| MID | (Only when the Execute on field is set to Specific MID Server.) The MID Server to which the logs are streamed. This field is required. |
| MID Server Cluster | (Only when Execute on is set to Specific MID Server cluster.) The MID Server cluster to which the log data is pulled. This field is required. The data input runs on a single MID Server in the cluster until that MID Server fails. The system then moves all the data input tasks to the next available MID Server in the cluster according to the configured order. Hinweis: * Health Log Analytics supports only failover MID Server clusters. In these clusters, multiple MID Servers are grouped together for failover protection. When selecting a cluster from the data input or integration form, the MID Server clusters list displays only failover clusters. * The MID Server cluster must include only MID Servers that support basic authentication. mTLS is not supported for log ingestion. * Log ingestion must be enabled for each MID Server in the cluster. If log ingestion is not enabled for the active MID Server, Health Log Analytics enables it automatically. * The default maximum number of data inputs or integrations streaming logs to a single MID Server is 10. A cluster passes capacity validation if it contains at least one MID Server with fewer than 10 data inputs or integrations running on it, even when that MID Server is down. {#hla-data-input-splunk-polling-ref__ul_htt_wdq_dwb} For more information about MID Server clusters, see [Configure a MID Server cluster](https://www.servicenow.com/docs/access?context=t_ConfigureAMIDServerCluster&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). |
| Service instance | The service instance to which to bind the log data. This field is required. Hinweis: If no relevant service instance exists, [create a service instance](https://www.servicenow.com/docs/access?context=create-it-services&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) and add CIs to it. Set the status of the new service instance to Operational. |
| Transport | The protocol used for streaming log messages to your ServiceNow instance. |
| Sources count | The number of log sources this data input has created. |
| Status | Status of the data input. |
| Disabled since | The time when the data input stopped or failed. |
| Last log time | The time when the last log streamed in the data input. |
[Tabelle : 1. Getting Started tab]

{#hla-data-input-splunk-polling-ref__table_lgv_scp_mdc}

## Advanced configuration {#hla-data-input-splunk-polling-ref__section_ayc_jnq_mdc}

{#hla-data-input-splunk-polling-ref__table_bxk_thp_mdc__entry__2}

| Field | Description |
|-|-|
| Server URL | The URL used to access the Splunk REST API. |
| Query | The query Splunk uses to search your data. |
| Authentication Type | The authentication type. * Basic authentication: Sends a username and password with each HTTP request. Basic authentication is simpler than token-based authentication, but less secure. * Token authentication: The client obtains a token from an authentication server and uses that token to authenticate against Splunk. {#hla-data-input-splunk-polling-ref__ul_iyq_qmp_mdc} |
| Splunk Poll Credential Alias | The credential alias to be used. Specify a Splunk Poll credential alias by selecting the magnifying glass icon and then either selecting an existing credential alias from the Connection \& Credential Aliases list, or selecting New to create a new record. The selected credential alias can hold one Basic Auth credential and one Token Auth credential. For information about creating a credential alias, see [Credential aliases for Discovery](https://www.servicenow.com/docs/access?context=discovery-credential-alias&version=australia&pubname=australia-platform-security&ft:locale=en-US). |
| From | The date and time from which Splunk searches the data. |
| To | The date and time until which Splunk searches the data. |
[Tabelle : 2. Transport tab]

{#hla-data-input-splunk-polling-ref__table_bxk_thp_mdc} {#hla-data-input-splunk-polling-ref__table_jjz_hhq_mdc__entry__2}

| Field | Description |
|-|-|
| Max documents per query | The maximum number of documents retrieved each time log data is fetched from Splunk. Default: 10,000. |
| Splunk request timeout (seconds) | The maximum time, in seconds, allowed for data retrieval before the request times out. |
[Tabelle : 3. Advanced tab]

{#hla-data-input-splunk-polling-ref__table_jjz_hhq_mdc}