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.


This topic describes how to use the function in the .


Assigns alternative names to fields or applies scalar functions to a group of fields. Returns a new record with only the provided fields.

When using this function in the UI, you can view the record's input and output schema. For example, if you are selecting data to be normalized from the Ingest service, then clicking the View Configurations tab in the select function displays the default fields in the event schema. You can normalize fields using field aliases or with an eval expression.

Function Input/Output Schema

Function Input
This function takes in collections of records with schema R.
Function Output
This function outputs the same collection of records but with a different schema S.


<expression> AS <field> ...

Required arguments

Syntax: collection<expression<any>>
Description: The <expression> can be either a field name or a scalar function.


This section contains additional usage information about the Select function.

Difference between Select and Eval

Both functions are used to change the fields in the record. However, while the eval function keeps existing fields and adds new fields for the aliases in the eval, select only includes the fields explicitly specified in the select function.

SPL2 example

When working in the SPL View, you can write the function by providing the arguments in this exact order.

This example keeps timestamp, id, and owner fields unchanged but renames logGroup and logStream fields.

... |select timestamp, id, owner, logGroup AS log_group, logStream AS log_stream | ...;
Last modified on 20 April, 2021
Rename   Stats

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.1.0, 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

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