{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30756,"path":"it-operations-management/health-log-analytics/hla-data-input-splunk-polling-ref.md","title":"Splunk Polling data input configuration fields","bundle":null,"doc_type":null,"release":"australia","body":"\n# Splunk Polling data input configuration fields\n\nDescription of the fields on the Splunk Polling data input configuration form.\n\n## Basic configuration\n\n<table id=\"table_lgv_scp_mdc\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nName of the new data input. This field is required.\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\nDescription of the data input.\n\n</td></tr><tr><td>\n\nExecute on\n\n</td><td>\n\nOption to select whether to use a specific MID Server or a MID Server cluster. This field is required.\n\n</td></tr><tr><td>\n\nMID\n\n</td><td>\n\n\\(Only when the **Execute on** field is set to Specific MID Server.\\)The MID Server to which the logs are streamed.\n\nThis field is required.\n\n</td></tr><tr><td>\n\nMID Server Cluster\n\n</td><td>\n\n\\(Only when **Execute on** is set to Specific MID Server cluster.\\)\n\nThe 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.\n\n**Note:**\n\n-   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.\n-   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.\n-   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. This is true even when that MID Server is down.\n\nFor more information about MID Server clusters, see [Configure a MID Server cluster](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_ConfigureAMIDServerCluster.md).\n\n</td></tr><tr><td>\n\nService instance\n\n</td><td>\n\nThe service instance to which to bind the log data. This field is required.**Note:** If no relevant service instance exists, [create a service instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/create-it-services.md) and add CIs to it. Set the status of the new service instance to Operational.\n\n</td></tr><tr><td>\n\nTransport\n\n</td><td>\n\nThe protocol used for streaming log messages to your ServiceNow instance.\n\n</td></tr><tr><td>\n\nSources count\n\n</td><td>\n\nThe number of log sources this data input has created.\n\n</td></tr><tr><td>\n\nStatus\n\n</td><td>\n\nStatus of the data input.\n\n</td></tr><tr><td>\n\nDisabled since\n\n</td><td>\n\nThe time when the data input stopped or failed.\n\n</td></tr><tr><td>\n\nLast log time\n\n</td><td>\n\nThe time when the last log streamed in the data input.\n\n</td></tr></tbody>\n</table>## Advanced configuration\n\n<table id=\"table_bxk_thp_mdc\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nServer URL\n\n</td><td>\n\nThe URL used to access the Splunk REST API.\n\n</td></tr><tr><td>\n\nQuery\n\n</td><td>\n\nThe query Splunk uses to search your data.\n\n</td></tr><tr><td>\n\nAuthentication Type\n\n</td><td>\n\nThe authentication type.-   Basic authentication: Sends a username and password with each HTTP request. Basic authentication is simpler than token-based authentication, but less secure.\n-   Token authentication: The client obtains a token from an authentication server and uses that token to authenticate against Splunk.\n\n</td></tr><tr><td>\n\nSplunk Poll Credential Alias\n\n</td><td>\n\nThe credential alias to be used. Specify a Splunk Poll credential alias by selecting the magnifying glass icon. Then either select an existing credential alias from the **Connection &amp; Credential Aliases** list, or select **New** to create a new record. The selected credential alias can hold one Basic Auth credential and one Token Auth credential.\n\nFor information about creating a credential alias, see [Credential aliases for Discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/discovery-credential-alias.md).\n\n</td></tr><tr><td>\n\nFrom\n\n</td><td>\n\nThe date and time from which Splunk searches the data.\n\n</td></tr><tr><td>\n\nTo\n\n</td><td>\n\nThe date and time until which Splunk searches the data.\n\n</td></tr></tbody>\n</table>|Field|Description|\n|-----|-----------|\n|Max documents per query|The maximum number of documents retrieved each time log data is fetched from Splunk. Default: 10,000.|\n|Splunk request timeout \\(seconds\\)|The maximum time, in seconds, allowed for data retrieval before the request times out.|\n\n**Parent Topic:**[Data input configuration fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-data-input-config-fields.md)\n\n"}}