Splunk Search

Apply different calculation count/sum depending on value/index

martinmasif
Explorer

I have a "cost" for two different indexes that I want to calculate in one and the same SPL. As the "price" is different depending on index, I can't just use a "by" clause in my count/sum as I don't know how to apply the separate costs in that way.

Let's say...

idxCheap costs $10 per event.

idxExpensive costs $20 per event.

I've written this SPL that works, although the "cost" data ends up in a unique column for each index. The count is still in the same column.

index=idxCheap OR index=idxExpensive
| stats count by index
| eval idxCheapCost = case(index="idxCheap", count*10)
| eval idxExpensiveCost = case(index="idxExpensive", count*20)

 The results looks like this:

count idxCheapCost idxExpensiveCost index

44892448920 idxCheap
155 3100idxExpensive

 

Any pointers on how to most efficiently and dynamically achieve this?

Labels (2)
Tags (2)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

You're close.  Combine the case functions to produce a single expense field.

index=idxCheap OR index=idxExpensive
| stats count by index
| eval idxCost = case(index="idxCheap", count*10, index="idxExpensive", count*20)

 

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

You're close.  Combine the case functions to produce a single expense field.

index=idxCheap OR index=idxExpensive
| stats count by index
| eval idxCost = case(index="idxCheap", count*10, index="idxExpensive", count*20)

 

---
If this reply helps you, Karma would be appreciated.

martinmasif
Explorer

Haha why did I even split it up on two rows?!

Thanks!

 

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!

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...