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.
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
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> ...
- 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.
When working in the SPL View, you can write the function by providing the arguments in this exact order.
This example keeps
owner fields unchanged but renames
... |select timestamp, id, owner, logGroup AS log_group, logStream AS log_stream | ...;
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