Splunk Dev

Difference between 2 fields using the diff command does not yield the same result

New Member

I am comparing a user list field from an index that runs a collection every 30 minutes. I do a comparison of these 2 events and search for the + or - . If it is + user has been added and if it is a - the user has been deleted.

The problem I am having is that the somehow the events ( 15 mins apart) are not coming through in the "right order".

2019-11-22 15:00 John Doe User Removed
2019-11-22 15:00 Jane Doe User Added

Press the search button again maybe 2 times ( No changes to time... just basically search again) I get ..

2019-11-22 15:00 Jane Doe User Removed
2019-11-22 15:00 John Doe User Added

Names have changed around.

Is this a bug in Splunk? ( I can replicate this over and over...)

Tags (1)
0 Karma

Esteemed Legend

Open a support case and then come back here and tell us what you find out!

0 Karma

New Member

I opened a support case and it looks like when the events are returned the diff command, irrespective of when the events arrived, would compare the events. This lead to the difference in the comparison between the 2 events. To resolve this issue we forced the events to be sorted before we did the diff command. At the moment it is working for now.

0 Karma


What is your base search? We will be unable to determine the issue without looking at your query.

0 Karma

New Member

index= cn = ""

| diff pos1=1 pos2=2 attribute=member_name

I then extract the username and do an eval case on the + and - which then does the added or removed.

0 Karma
Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

 (view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...