Splunk
StackState Self-hosted v5.1.x
Last updated
StackState Self-hosted v5.1.x
Last updated
The StackState Splunk integration synchronizes events, metrics, health and topology data from Splunk to StackState. The integration uses StackState Agent V2 to collect Splunk events, metrics, health and topology data.
Splunk is a StackState core integration.
StackState Agent V2 periodically connects to the configured Splunk instance to execute Splunk saved searches and retrieve data:
Topology data from the searches configured in the Splunk Topology Agent check.
Metrics data from the searches configured in the Splunk Metrics Agent check.
Events data from the searches configured in the Splunk Events Agent check.
Health data from the searches configured in the Splunk Health Agent check.
The Agents push retrieved data to StackState.
StackState translates incoming data:
Topology data is translated into components and relations.
Metrics data is available in StackState as a metrics telemetry stream.
Events are available in StackState as a log telemetry stream.
Health information is added to associated components and relations.
A running Splunk instance.
A Splunk user account with access to Splunk saved searches. The user should have the capability search to dispatch and read Splunk saved searches.
A compatible StackState Agent V2 installed on a machine that can connect to both Splunk and StackState.
The Splunk StackPack provides all the necessary configuration to easily work with Splunk topology data in StackState. Install the Splunk StackPack from the StackState UI StackPacks > Integrations screen. You will need to enter the following details:
Splunk instance name - A unique name to identify the Splunk instance in StackState.
Splunk API URL - The URL where the Splunk API can be reached. For example: http://splunk.network.local:8089.
After the StackPack has been installed, you should follow the instructions below to configure the required Splunk checks on StackState Agent V2.
A Splunk check must be configured on StackState Agent V2 for each type of data you want to retrieve from Splunk:
Splunk Health check - to retrieve health data from Splunk
Splunk Topology check - to retrieve topology data from Splunk
Splunk Events check - to retrieve events data from Splunk
Splunk Metrics check - to retrieve metrics data from Splunk
Each Splunk check configured on StackState Agent V2 must include authentication details to allow the Agent to connect to your Splunk instance and execute the configured Splunk saved searches.
Two authentication mechanisms are available:
Token-based authentication supports Splunk authentication tokens. An initial Splunk token is provided in the Splunk check configuration. This initial token is used the first time the check starts, it's then exchanged for a new token. For details on using token based authentication with Splunk, see the Splunk documentation (docs.splunk.com).
Token-based authentication is preferred over HTTP basic authentication and will override basic authentication in case both are configured.
To enable token-based authentication, the following parameters should be included in the section authentcation.token_auth of each StackState Agent V2 Splunk check configuration file:
name - Name of the user who will use this token.
initial_token - An initial, valid token. This token will be used once only and then replaced with a new generated token requested by the integration.
audience - The Splunk token audience.
token_expiration_days - Validity of the newly requested token. Default 90 days.
renewal_days - Number of days before a new token should be refreshed. Default 10 days.
The first time the check runs, the configured initial_token will be exchanged for a new token. After the configured renewal_days days, another new token will be requested from Splunk with a validity of token_expiration_days.
It's recommended to use token-based authentication.
With HTTP basic authentication, the username and password specified in the StackState Agent V2 check configuration files are used to connect to Splunk. These parameters are specified in the section authentication.basic_auth of each StackState Agent V2 Splunk check configuration file.
To check the status of the Splunk integration, run the status subcommand and look for splunk_topology, splunk_metrics or splunk_events under Running Checks:
The Splunk integration can retrieve the following data:
When the Splunk Events Agent check is configured, events will be retrieved from the configured Splunk saved search or searches. Events retrieved from splunk are available in StackState as a log telemetry stream in the stackstate-generic-events data source. This can be mapped to associated components.
For details on how to configure the events retrieved, see the Splunk Events check configuration.
When the Splunk Metrics Agent check is configured, metrics will be retrieved from the configured Splunk saved search or searches. One metric can be retrieved from each saved search. Metrics retrieved from splunk are available in StackState as a metrics telemetry stream in the stackstate-metrics data source. This can be mapped to associated components.
For details on how to configure the metrics retrieved, see the Splunk Metrics check configuration.
When the Splunk StackPack is installed, and a Splunk Topology Agent check is configured, topology will be retrieved from the configured Splunk saved searches. The check that you should configure depends on the StackState Agent that you will use to retrieve topology data.
For details on how to configure the components and relations retrieved, see the Splunk Topology check configuration.
If you have an existing Splunk Topology integration configured to use StackState Agent V1 (legacy) and would like to upgrade to use StackState Agent V2, refer to the Agent migration instructions.
When the Splunk Health Agent check is configured, health check states will be retrieved from the configured Splunk saved searches. Retrieved health check states are mapped to the associated components and relations in StackState.
For details on how to configure the health retrieved, see the Splunk Health check configuration.
The StackState Splunk integration doesn't retrieve any trace data.
StackState Agent V2 connects to the Splunk API at the endpoints listed below. The same endpoints are used to retrieve events, metrics and topology data.
/services/auth/login?output_mode=json
Auth login
/services/authorization/tokens?output_mode=json
Create token
/services/saved/searches?output_mode=json&count=-1
List of saved searches
/servicesNS/<user>/<app>/saved/searches/<saved_search_name>/dispatch
Dispatch the saved search
/services/search/jobs/<saved_search_id>/control
Finalize the saved search
For further details, see the Splunk API documentation (docs.splunk.com).
The Splunk StackPack and the Agent checks for Splunk Events, metrics and topology are open source and available on GitHub at the links below:
Troubleshooting steps for any known issues can be found in the StackState support Knowledge base.
To uninstall the Splunk StackPack, go to the StackState UI StackPacks > Integrations > Splunk screen and click UNINSTALL. All Splunk topology specific configuration will be removed from StackState.
For instructions on how to disable the Splunk Agent checks, see:
The Splunk StackPack release notes are available on GitHub.
Configure the StackState Agent V2 Splunk checks:
Splunk Health check - to retrieve health data from Splunk
Splunk Topology check - to retrieve topology data from Splunk
Splunk Events check - to retrieve events data from Splunk
Splunk Metrics check - to retrieve metrics data from Splunk
Other resources:
