Splunk Search

Comparing results from 2 days?

pbabos
Explorer

Hello, I'm struggling with a task and would like to ask for your opinion about it. Goal is to set up an alert, which would fire an event in case the last 24h results differ from the one from 24h-48h before, and to also show the difference.

I was trying to have something like:

 

 

 

| set diff [search message="Connected to system:*" earliest=-24h  | rex field=connectedSystemName message="Connected to system: (?<systemName>.+)" | stats values(connectedSystemName) as system_names] [search message="Connected to system:*" earliest=-48h latest=-24h | rex field=connectedSystemName message="Connected to system: (?<systemName>.+)" | stats values(connectedSystemName) as system_names]

 

 

 


My results from this search is one coloumn of a list of the names of the connected systems. How could I reach such comparisment to also show the differences?

Thanks a lot in advance!
Peter

0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust

Try something like this

<first search last 24 hours>
| eval period = 1
| append [search <second search previous 24 hours>
  | eval period = 2]
| stats sum(period) as periods by systemName

If periods = 1, it is only in the first search

If periods = 2, it is only in the second search

If periods = 3, it is in both periods

View solution in original post

ITWhisperer
SplunkTrust
SplunkTrust

Try something like this

<first search last 24 hours>
| eval period = 1
| append [search <second search previous 24 hours>
  | eval period = 2]
| stats sum(period) as periods by systemName

If periods = 1, it is only in the first search

If periods = 2, it is only in the second search

If periods = 3, it is in both periods

pbabos
Explorer

wow nice, thanks, this is something I can work with! 🙂

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 ...