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.
Get data from Splunk DSP Firehose
Use the Splunk DSP Firehose to get data sent from the Forwarder, Collect, Ingest, DSP HEC, and Syslog (through SC4S) API services. These services support data ingest for the following data sources:
- Splunk forwarders
- HTTP clients
- Syslog data
- The Ingest REST API
The Splunk DSP Firehose collects data from all of the supported services concurrently and outputs the combined data in a single stream, allowing you to ingest data from multiple data sources at the same time with minimal pipeline configuration. See Connecting multiple data sources to your DSP pipeline in the Connect to Data Sources and Destinations with DSP manual for more information.
Function output schema
- Syntax: LATEST | TRIM_HORIZON
- Description: The position in the data stream where you want to start reading data. Defaults to LATEST.
- LATEST: Start reading data from the latest position on the data stream.
- TRIM_HORIZON: Start reading data from the very beginning of the data stream.
- Example: "LATEST"
When working in the SPL View, you can write the function using the following syntax.
| from splunk_firehose("TRIM_HORIZON") |...;
Alternatively, you can use the named argument syntax to write this function.
| from splunk_firehose(initial_position: "TRIM_HORIZON") |...;
Limitations of the Splunk DSP Firehose
The maximum supported event or metric record size is 5 MB.
Write thru KV Store
Get data from Forwarders service
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.4.0, 1.4.1, 1.4.2