Splunk® Data Stream Processor

Function Reference

On April 3, 2023, Splunk Data Stream Processor reached its end of sale, and will reach its end of life on February 28, 2025. If you are an existing DSP customer, please reach out to your account team for more information.

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 in order to continue to receive full product support from Splunk.

Get data from Forwarders service

Use the Forwarders Service source function to get data from a Splunk universal or heavy forwarder. This is a source function that filters your data to only ingest data from the Splunk Forwarders Service. See also Process data from a universal forwarder.

Function output schema

This function outputs data pipeline events using the event schema for events or metrics schema for metrics.

Required arguments

connection_id
Syntax: string
Description: The ID of your Splunk Forwarders connection. Must be set to "forwarders:all".
Example: "forwarders:all"

SPL2 example

When working in the SPL View, you can write the function using the following syntax.

| from forwarders("forwarders:all") |....;

Alternatively, you can use the named argument syntax to write this function.

| from forwarders(connection_id: "forwarders:all") |....;

Limitations of the Forwarders Service

The maximum supported size for a record is 5MB. If any records exceed that size, the Forwarders service returns an error.

Last modified on 19 February, 2021
Get data from Splunk DSP Firehose   Get data from 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, 1.3.0, 1.3.1, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6


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