Splunk Polling data input configuration fields
Summarize
Summary of Splunk Polling Data Input Configuration Fields
This configuration guide explains the fields available in the Splunk Polling data input form within ServiceNow Yokohama release. It helps you set up and manage how log data is polled from Splunk into your ServiceNow instance, ensuring efficient and secure log ingestion through MID Servers or MID Server clusters.
Show less
Basic Configuration
- Name: Required field to name the new data input.
- Description: Optional field to describe the data input.
- Execute on: Select whether to use a specific MID Server or a MID Server cluster for the data input.
- MID Server / MID Server Cluster: Depending on the selection above, specify the exact MID Server or cluster to stream logs. Failover clusters are supported to ensure continuous log ingestion. Clusters must have MID Servers supporting basic authentication (mTLS not supported) and enabled log ingestion. Capacity limits apply to data inputs per MID Server.
- Service Instance: Required field to bind the log data to a specific service instance, which must be operational and have relevant CIs assigned.
- Transport: Defines the protocol used for streaming logs to ServiceNow.
- Sources Count, Status, Disabled Since, Last Log Time: These fields provide status and operational metadata about the data input.
Advanced Configuration
Transport Tab
- Server URL: URL for accessing the Splunk REST API.
- Query: Splunk search query to retrieve desired log data.
- Authentication Type: Choose between basic authentication (username/password) or token authentication (more secure, token-based).
- Splunk Poll Credential Alias: Select or create a credential alias that holds authentication credentials for Splunk access.
- From / To: Define the time range for Splunk to search the data.
Advanced Tab
- Max Documents per Query: Limits the number of documents retrieved per request from Splunk (default 10,000) to control load and performance.
- Splunk Request Timeout (seconds): Sets the maximum time allowed for data retrieval before timing out.
Practical Implications for ServiceNow Customers
By correctly configuring these fields, customers can ensure reliable and secure ingestion of Splunk log data into ServiceNow for Health Log Analytics and other use cases. Proper selection of MID Servers or clusters and authentication methods aligns with operational needs and security policies. Time range and query settings allow precise control over the data retrieved. Understanding these configuration options helps optimize performance and maintain continuous log streaming with failover support.
Description of the fields on the Splunk Polling data input configuration form.
Basic configuration
| 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. Note: For more information about MID Server clusters, see Configure a MID Server cluster.
|
| Service instance | The service instance to which to bind the log data. This field is required. Note: If no relevant service instance exists, create a service instance 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. |
Advanced configuration
| 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.
|
| 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. |
| From | The date and time from which Splunk searches the data. |
| To | The date and time until which Splunk searches the data. |
| 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. |