Splunk Search

Is there any way of taking the field name in an event and using the lookup renaming it to what is found in the lookup?

jwhughes58
Contributor

I'm working with the "Jira Issue Input Add-on" and in Jira we have created custom fields.  Splunk ingests issues and the custom field data looks like this

 

customfield_10101: SA-1017
customfield_10107: 3
customfield_25402: [ [+]
]
customfield_25426: [ [+]
]
customfield_25427: { [+]
} 

 

There are 1,049 custom fields.  I would like to use the names for the custom fields and have created a csv file with this

 

customfield_custom_field_number,custom_field_name
customfield_10000,Request participants
...
customfield_27904,Target Date

 

I'm trying to avoid having all the renames in props.conf.  Is there any way of taking the field name in an event and using the lookup renaming it to what is found in the lookup?

Labels (1)
Tags (3)
0 Karma
1 Solution

yuanliu
SplunkTrust
SplunkTrust

You don't have. to rename; in fact better avoid renaming in props.conf.  The answer is keyword AS.  Excerpt from lookup:

The required syntax is in bold.

lookup
[local=<bool>] [update=<bool>]
<lookup-table-name> ( <lookup-field> [AS <event-field>] )...
[ OUTPUT | OUTPUTNEW (<lookup-destfield> [AS <event-destfield>] )... ]

Note: The lookup command can accept multiple lookup and event fields and destfields. For example:

...| lookup <lookup-table-name> <lookup-field1> AS <event-field1>, <lookup-field2> AS <event-field2> OUTPUTNEW <lookup-destfield1> AS <event-destfield1>, <lookup-destfield2> AS <event-destfield2>

 

View solution in original post

yuanliu
SplunkTrust
SplunkTrust

You don't have. to rename; in fact better avoid renaming in props.conf.  The answer is keyword AS.  Excerpt from lookup:

The required syntax is in bold.

lookup
[local=<bool>] [update=<bool>]
<lookup-table-name> ( <lookup-field> [AS <event-field>] )...
[ OUTPUT | OUTPUTNEW (<lookup-destfield> [AS <event-destfield>] )... ]

Note: The lookup command can accept multiple lookup and event fields and destfields. For example:

...| lookup <lookup-table-name> <lookup-field1> AS <event-field1>, <lookup-field2> AS <event-field2> OUTPUTNEW <lookup-destfield1> AS <event-destfield1>, <lookup-destfield2> AS <event-destfield2>

 

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...