Splunk Dev

Running search calculation

smanojkumar
Contributor

smanojkumar_1-1626444269426.png

The calculation has to be made on Team Availability, taking a value of 96000 reduces the current Time Required  value and display in the next row in Team Availability, the recent Team Availability value must be taken for next subtraction with Time Required can be displayed  in the next row in Team Availability, so it continues for all Time Required valued.

The last image is the expected one,

Help me to rectify my doubt and share the query

smanojkumar_2-1626444735557.png

 

0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust
| streamstats last(TimeRequired) as previousTimeUsed window=2 current=f
| streamstats sum(previousTimeUsed) as cumulativeUsage
| fillnull value=0 cumulativeUsage
| eval TeamAvailability=96000-cumulativeUsage

View solution in original post

ITWhisperer
SplunkTrust
SplunkTrust
| streamstats last(TimeRequired) as previousTimeUsed window=2 current=f
| streamstats sum(previousTimeUsed) as cumulativeUsage
| fillnull value=0 cumulativeUsage
| eval TeamAvailability=96000-cumulativeUsage

smanojkumar
Contributor

It works, Thanks

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!

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...

SplunkTrust Application Period is Officially OPEN!

It's that time, folks! The application/nomination period for the 2026-2027 SplunkTrust is officially open. If ...