Splunk® Data Stream Processor

Use the Data Stream Processor

DSP 1.2.1 is impacted by the CVE-2021-44228 and CVE-2021-45046 security vulnerabilities from Apache Log4j. To fix these vulnerabilities, you must upgrade to DSP 1.2.4. See Upgrade the Splunk Data Stream Processor to 1.2.4 for upgrade instructions.

On October 30, 2022, all 1.2.x versions of the Splunk Data Stream Processor will reach its end of support date. See the Splunk Software Support Policy for details.
This documentation does not apply to the most recent version of Splunk® Data Stream Processor. For documentation on the most recent version, go to the latest release.

Interpreting pipeline statuses

The pipeline statuses displayed in the indicate the condition of a pipeline and its components. The pipeline status is an overview of the pipeline state. If you want more information about a particular pipeline, contact Splunk Customer Support for assistance.

Pipeline statuses and what they mean

Use the table to learn more about the different statuses that a pipeline can have and what they mean.

Pipeline status in the UI Description
ACTIVATED The pipeline is activated and should be receiving and sending data. If your pipeline is newly activated and you are not seeing data flow through the pipeline, wait a few minutes and check again.
CREATED The pipeline is not currently activated.
FAILED The pipeline encountered an error and stopped working.
RESTARTING The pipeline encountered an error and is restarting to recover.

If a pipeline has the RESTARTING status, then the continues to retry the pipeline until it succeeds. If a pipeline is stuck in the RESTARTING status, cycling between RESTARTING and other statuses, or has the FAILED status, try the following remediation steps.

  1. Check to see if your functions are configured correctly. Your pipeline can be in a FAILED or RESTARTING state if one of your functions is misconfigured. For example, this issue can occur if an Amazon Kinesis Data Streams source function is misconfigured with the wrong Kinesis topic name.
  2. Check to see if your connection is configured correctly, and you have the right third-party permissions to connect the third-party service to the . See Getting started with DSP data connections in the Connect to Data Sources and Destinations with DSP manual for more information.
  3. Deactivate the pipeline with Skip Savepoint enabled. For instructions on how to enable Skip Savepoint, see Pipeline fails to deactivate with error "Failed to queue pipeline for deactivation". For information about checkpoints and savepoints, see Using activation checkpoints to activate your pipeline.

If the pipeline is still stuck with the RESTARTING or FAILED status, contact Splunk Customer Support for assistance.

Last modified on 30 November, 2021
Using activation checkpoints to activate your pipeline   About the Ingest service

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.0, 1.2.1-patch02, 1.2.1, 1.2.2-patch02, 1.2.4, 1.2.5

Acrobat logo Download manual
Acrobat logo Download this page

Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters