Splunk Search

Help with subsearch eval function with where clause

ND
Path Finder

Hi All,

I want help to use where clause in eval command:

below is lookup data:

ID  expense year

1     10          2021

2     20          2020

3     10          2021

4     30          2019

5     20          2020

eval a = sum(expense) by ID, year where ID IN(1,3)

eval b= sum(expense) by ID, year  where ID IN(2,4)

eval c= sum(expense) by ID, year where ID IN(1,2,3,4)  [excluding few ID's from the search]

 

can someone help me to get this. I tried join to have these values as a subsearch but not able to get it.

 

thanks.

 

Labels (4)
0 Karma
1 Solution

ND
Path Finder

@ITWhisperer  thanks for the solution. it solved my query.

View solution in original post

0 Karma

ND
Path Finder

@ITWhisperer  thanks for the solution. it solved my query.

0 Karma

mayurr98
Super Champion

Could you please paste the result of the output that you want?

The question doesn't make sense to me, when you say sum(expense) by ID, it means sum(expense) by distinct ID in splunk language and it will always be the value of expense as shown in the input table.

Please tell us the output result in tabular format that you want.

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust
| eval group_a=if(ID IN (1,3),expense,null())
| eval group_b=if(ID IN (2,4),expense,null())
| eval group_c=if(ID IN (1,2,3,4),expense,null())
| stats sum(group_a) as a sum(group_b) as b sum(group_c) as c by year
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!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

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