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.
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
- Amazon CloudWatch
- Amazon S3
- Amazon Web Services (AWS) metadata
- Google Cloud Monitoring
- Microsoft 365
- Microsoft Azure Monitor
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
This function outputs data pipeline events using the event schema for events or metrics schema for metrics.
Optional arguments
- initial_position
- 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"
SPL2 example
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.2.0, 1.2.1-patch02, 1.2.1, 1.2.2-patch02, 1.2.4, 1.2.5, 1.3.0, 1.3.1
Feedback submitted, thanks!