Splunk Search

Average command vs count and average command

ranjitbrhm1
Communicator

Maybe im just bad in mathematics. but why does splunk docs always take the count of events and then the avg of events (stats count(events) | stats avg(events) instead of stats avg events directly?

can someone please explain the logic to me?

0 Karma
1 Solution

TISKAR
Builder

Hello,

The avg function applie to number field avg(event) the event is number, you can apply avg directly to the field that have the number value without use stats count, and when you use | stats count | stats avg the avg look only to the result give by stats count
For example:

 stats count as a by field | stats avg(a) 

can you share the link of docs please

Regards

View solution in original post

TISKAR
Builder

Hello,

The avg function applie to number field avg(event) the event is number, you can apply avg directly to the field that have the number value without use stats count, and when you use | stats count | stats avg the avg look only to the result give by stats count
For example:

 stats count as a by field | stats avg(a) 

can you share the link of docs please

Regards

FrankVl
Ultra Champion

Can you provide a link to an example of that? The way you quoted it here it doesn’t make too much sense to me...

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!

Value Insights: Now Generally Available in the CMC

Organizations are under pressure to move faster, control cost, expand AI adoption, and prove value with more ...

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...