Splunk Enterprise

Help on eval if from eval case

jip31
Motivator

Hi

As you can see, I use a first eval in order to rename the field "site"

From the site renamed, I need to create a new field called "toto" in order to add new information for the field site.

So I create an eval if command like below but it doesn't work.

What is wrong please and is there another simple way to do this?

 

| eval site=case(site=="BR", "Espace Br", site=="PERI THEATRE", "Espace Périg", 1==1,site)
| stats last(site) as "Espace BP" by s
| eval toto=if("Espace BP"=="Espace Br", "4G") 
| table "Espace BPE" toto 

 

 

Tags (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

The if function is comparing two different strings and setting a value only if they are equal.  Therefore, toto is always null.

Use single quotes around a field name containing spaces.

| eval site=case(site=="BR", "Espace Br", site=="PERI THEATRE", "Espace Périg", 1==1,site)
| stats last(site) as "Espace BP" by s
| eval toto=if('Espace BP'=="Espace Br", "4G") 
| table "Espace BPE" toto 

Better yet, don't use spaces in field names at all.  Add a final rename command in the query to make the names "pretty".

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

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

The if function is comparing two different strings and setting a value only if they are equal.  Therefore, toto is always null.

Use single quotes around a field name containing spaces.

| eval site=case(site=="BR", "Espace Br", site=="PERI THEATRE", "Espace Périg", 1==1,site)
| stats last(site) as "Espace BP" by s
| eval toto=if('Espace BP'=="Espace Br", "4G") 
| table "Espace BPE" toto 

Better yet, don't use spaces in field names at all.  Add a final rename command in the query to make the names "pretty".

---
If this reply helps you, Karma would be appreciated.
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 ...