Splunk Enterprise

Issue with Sequence of Operation

bharathkumarnec
Contributor

Hello Everyone,

Today i observed a weird behavior while using eval and kvstore lookup file, below is my case:

My query is :

| eval fieldname2=if(fieldname1="abc","Starting",fieldname2) | lookup local=true mylookup Key as fieldname2 OUTPUT fieldname3

When i run this search i am getting quite less number of matches and when i run below i get more matches

 | eval fieldname2=if(fieldname1="abc","Starting",fieldname2) | lookup local=true mylookup.csv Key as fieldname2 OUTPUT fieldname3

mylookup & mylookup.csv both have same set of data and the only difference is first one is a kv store and the next one is a lookup file.

Till we upgrade to 7.3.5 from 7.1.6 it was working without any issues, but post upgrade observed this weird behavior.

May be someone can help me to find out what i am missing here??

Thanks in advance!!

Regards,

BK

Tags (2)
0 Karma

anilchaithu
Builder

@bharathkumarnec 

It might be due to case variance in the field names. kvstore lookups are case sensitive to field names while csv lookups are not.

Can you please verify that?

 

0 Karma

bharathkumarnec
Contributor

Thanks for your input @anilchaithu , but when we use below it is working without any issues:

| eval fieldname2=if(fieldname1="abc","Starting",fieldname2)

| eventstats values(fieldname2) as fieldname2 by host

| lookup local=true mylookup Key as fieldname2 OUTPUT fieldname3

So placing | eventstats between working fine...and we are using the same cases as it is in the kv store..

0 Karma
Get Updates on the Splunk Community!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...