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!

Casting Call: Compete in Cyber Games

Lights, Camera, SecOps: Apply to Compete in Cyber Games     Think you have what it takes to beat the clock? ...

Data Management Digest – June 2026

Welcome to the June 2026 edition of Data Management Digest! This month’s update is short and sweet, with a ...

Think Like an Architect: Introducing the Splunk Certified Cybersecurity Defense ...

In cybersecurity, defenders respond to threats. Architects design the systems that stop them.    As ...