Dashboards & Visualizations

Graph of peak traffic measured by hour

karthy
Explorer

I have an apache-like access log and would like to graph the traffic by hour. However, the graph I want is a graph of the number of requests pr. hour divided by 60*60 so that it is easy to identify the busy hour expressed in requests pr. seconds.

I assume I have to use bins or span, but I have been unsuccessful so far. Any hints?

Tags (1)
1 Solution

David
Splunk Employee
Splunk Employee

If you're looking for the average per hour, I'd go this route:

YourSearch | timechart span=1h count as TotalRequests 
           | eval RequestsPerSecond = TotalRequests/3600

If you wanted to look at the actual busiest second, you could go for:

YourSearch | bucket _time span=1s 
           | stats count as RequestsPerSec by _time 
           | timechart span=1h avg(RequestsPerSec) Max(RequestsPerSec)

View solution in original post

David
Splunk Employee
Splunk Employee

If you're looking for the average per hour, I'd go this route:

YourSearch | timechart span=1h count as TotalRequests 
           | eval RequestsPerSecond = TotalRequests/3600

If you wanted to look at the actual busiest second, you could go for:

YourSearch | bucket _time span=1s 
           | stats count as RequestsPerSec by _time 
           | timechart span=1h avg(RequestsPerSec) Max(RequestsPerSec)

David
Splunk Employee
Splunk Employee

Excellent! I'm glad to hear it.

0 Karma

karthy
Explorer

Thanks - works just right!

0 Karma
Get Updates on the Splunk Community!

Splunk at Cisco Live 2025: Learning, Innovation, and a Little Bit of Mr. Brightside

Pack your bags (and maybe your dancing shoes)—Cisco Live is heading to San Diego, June 8–12, 2025, and Splunk ...

Splunk App Dev Community Updates – What’s New and What’s Next

Welcome to your go-to roundup of everything happening in the Splunk App Dev Community! Whether you're building ...

The Latest Cisco Integrations With Splunk Platform!

Join us for an exciting tech talk where we’ll explore the latest integrations in Cisco + Splunk! We’ve ...