Splunk Search

multiple case statement not working

samneo
Path Finder

Im working with JSON data and the structure is as per the below

 

data: { [-]
     application: { [+]
     }
     completedAt: 1636133794444
     environments: [ [-]
       { [-]
         id: XNu1-l8oROOOSM5gpoSR0g
       }
       { [-]
         id: _LY0B7VpRq64tHXq7Uy55A
       }
       { [-]
         id: 7KbvgSBMSUSUyAn2hMXSQA
       }
       { [-]
         id: dJ7EuItjSG2M47-zvIvimQ
       }
     ]

 

Now when i use a case function for this like the below:

|eval env = case('data.environments{}.id'=="7KbvgSBMSUSUyAn2hMXSQA", "prd-au", 'data.environments{}.id'=="_LY0B7VpRq64tHXq7Uy55A", "prd-gb")

It only ever brings me back 1 result and thats whatever is placed first in the case function so the above returns prd-au and if i swap the values around then it will return prd-gb. I presume this is something to do with how the JSON data is working with splunk causing it to error out but unsure how to resolve?

any ideas? 

Tags (1)
0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust

You would need to expand the event into multiple events, try something like this

| mvexapnd 'data.environments{}.id'

 

View solution in original post

0 Karma

samneo
Path Finder

thanks @ITWhisperer is there a way round this so i can get all values?

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

You would need to expand the event into multiple events, try something like this

| mvexapnd 'data.environments{}.id'

 

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Splunk is working with a pipeline of events - the events in the pipeline include multivalue fields such as data.environments{}.id - the eval case finds a match among the multivalues for the first test hence you get the results you are getting

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...