All DSP releases prior to DSP 1.4.0 use Gravity, a Kubernetes orchestrator, which has been announced end-of-life. We have replaced Gravity with an alternative component in DSP 1.4.0. Therefore, we will no longer provide support for versions of DSP prior to DSP 1.4.0 after July 1, 2023. We advise all of our customers to upgrade to DSP 1.4.0 before July 1, 2023 in order to continue to receive full product support from Splunk.
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.|
|ACTIVATING||The pipeline is in the activation queue.|
|CREATED||The pipeline is not currently activated.|
|DEACTIVATING||The pipeline is in the deactivation queue.|
|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.
- 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.
- 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 data connections in the Connect to Data Sources and Destinations with the manual for more information.
- 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 in the User Manual.
If the pipeline is still stuck with the RESTARTING or FAILED status, contact Splunk Customer Support for assistance.
Using activation checkpoints to activate your pipeline
About the Ingest service
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.3.0, 1.3.1, 1.4.0, 1.4.1
Feedback submitted, thanks!