Splunk Search

Difference between per_second and span=1s in timechart?

Mattjj
Explorer

Hi all,

We are trying to show the bytes/s, averaged over 15 mins.  I'm getting far lower results if I use per_second than a live timechart with a span of 1s, so:

index="datafeed" | where isnotnull(bytes) | timechart span=15m per_second(bytes)

Gives an average of 10mb/s

Whereas:

index="datafeed" | where isnotnull(bytes) | timechart span=1s sum(bytes)

Shows the data constantly hovering around the 100mb/s mark, so the 15 min average must be up at that level.  Am I missing something obvious?  

Thanks for any pointers!

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

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Rounding off the Splunk Dashboard Contest

What does a contest-winning Splunk dashboard look like? In this case, it isn't in a browser tab at all. It ...

A Four Part Event Series: AI + Observability: AI Agents, LLMs, Apps, & Infrastructure

AI + Observability: AI Agents, LLMs, Apps, & Infrastructure The rapid evolution of artificial intelligence ...