Splunk Search

Events per second without hitting limitations

aohls
Contributor

I am looking to calculate per second transactions but when doing so through either stats or a timechart I am hitting the limits of these functions. This is in a dashboard with a time selector so it can be variable. Is there any way to protect against running over the limits in a search? I was using the per_second function in timechart. Has anyone found a better way to handle getting average, min/max at a per second interval?

 

 

timechart span=5m per_second(count) as TPS

 

  

Labels (3)
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!

Best Practices: Splunk auto adjust pipeline queue

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

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...