Splunk Search

Where can we rename the src field?

danielbb
Motivator

We have the following working query -

(index=wineventlog sourcetype=WinEventLog NOT ("xxxx" OR "yyyy") 
src_ip IN (<mulitple IPs>)) OR (index=checkpoint 
dst IN (<mulitple IPs>) action=Accept ) 
| eval destination_ip = coalesce(<one name>,<second name>) 
| transaction destination_ip maxpause=60s

Both index=wineventlog and index=checkpoint have a src field.

Where can we rename it? because we end up after the transaction command with two srcfields.

Tags (1)
1 Solution

richgalloway
SplunkTrust
SplunkTrust

You can rename the field any time after the first pipe. Of course, that will rename the field from both indexes. To rename only one index, you'll need to split the base query, do the rename, then combine them with append.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

You can rename the field any time after the first pipe. Of course, that will rename the field from both indexes. To rename only one index, you'll need to split the base query, do the rename, then combine them with append.

---
If this reply helps you, Karma would be appreciated.

danielbb
Motivator

Thank you @richgalloway.

The developer did | eval src-{index} = src which generated the src-wineventlog and src-checkpoint fields. She is happy ; -)

0 Karma

richgalloway
SplunkTrust
SplunkTrust

If your problem is resolved, please accept the answer to help future readers.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...