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!

Supercharging Windows Security Detection Performance: Introducing Hybrid Field ...

Windows event logs—from Security auditing and Sysmon to PowerShell script blocks—form the operational backbone ...

Enriching Signals with the OTel Lookup Processor

Introduction Raw telemetry is often incomplete. A log line might record an IP address, but what you really ...

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...