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!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...