Splunk Search

Determine frequency over time

chrisj
Engager

I am attempting to work out the frequency of events over the selected timespan in weeks.  Basically: count of events in current timespan divided by weeks in timespan.

I can get a count of events for the selected timespan using:

 

index=mydata
| stats count(eval(ishotfix= "false")) as hfx
| fields hfx

 

I can get the timepicker span weeks using (im sure this is terrible):

 

| makeresults
| addinfo
| eval timepickerSpanWeeks=round(((info_max_time - info_min_time)/60/60/24/7),0)
| fields timepickerSpanWeeks

 

and if I combine I am getting no results

 

| makeresults
| addinfo
| eval timepickerSpanWeeks=round(((info_max_time - info_min_time)/60/60/24/7),0)
| map search="search index=mydata"
| stats count(eval(ishotfix= "false")) as hfx
| eval rate=round((hfx/timepickerSpanWeeks), 2)
| fields rate

 

thanks in advance!

Labels (1)
0 Karma
1 Solution

chrisj
Engager
index=mydata
| addinfo | eval timepickerSpanWeeks=round(((info_max_time - info_min_time)/60/60/24/7),0)
| where ishotfix= "false"
| eventstats count(timepickerSpanWeeks) as counter
| eval rate = round(counter / timepickerSpanWeeks,2)
| top rate
| fields rate

This is what got me the result, it seems like a poor way of getting it but the number of results isn't large.  Happy for someone to revise! 🙂  Thanks for your help @ITWhisperer 

View solution in original post

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Try this

index=mydata
| addinfo
| eval timepickerSpanWeeks=round(((info_max_time - info_min_time)/60/60/24/7),0)
| stats count(eval(ishotfix= "false")) as hfx
| eval rate=round((hfx/timepickerSpanWeeks), 2)

chrisj
Engager
index=mydata
| addinfo | eval timepickerSpanWeeks=round(((info_max_time - info_min_time)/60/60/24/7),0)
| where ishotfix= "false"
| eventstats count(timepickerSpanWeeks) as counter
| eval rate = round(counter / timepickerSpanWeeks,2)
| top rate
| fields rate

This is what got me the result, it seems like a poor way of getting it but the number of results isn't large.  Happy for someone to revise! 🙂  Thanks for your help @ITWhisperer 

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...