Splunk Search

Subsearch calculating average of hits and showing list of values higher than the average?

changwoo
Communicator

I am trying to make a subsearch which calculates the avg of the hits .
And showing the list of higher value than the avg.

i tried the search like this :
index= temp sourcetype = searchlog [search index = temp sourcetype = searchlog |stats avg(searchKeyword.hits) as avg | fields avg] | table avg

What's the problem ?

Tags (3)
1 Solution

Suda
Communicator

Hello,

Could you try to use "eventstats"?

I think the "Example 3" of eventstats would be the same as your requirement.

http://docs.splunk.com/Documentation/Splunk/6.1.2/SearchReference/Eventstats

index=temp sourcetype=searchlog | eventstats avg(searchKeyword.hits) AS avg | where searchkeyword.hits > avg

I hope it helps you. Happy splunking!

View solution in original post

Suda
Communicator

Hello,

Could you try to use "eventstats"?

I think the "Example 3" of eventstats would be the same as your requirement.

http://docs.splunk.com/Documentation/Splunk/6.1.2/SearchReference/Eventstats

index=temp sourcetype=searchlog | eventstats avg(searchKeyword.hits) AS avg | where searchkeyword.hits > avg

I hope it helps you. Happy splunking!

changwoo
Communicator

Thanks!!! it works perfect!!!

martin_mueller
SplunkTrust
SplunkTrust

Note, you need to enclose searchKeyword.hits in single quotes for the where (and the RHS of eval) commands:

... | where 'searchKeyword.hits' > avg

Else the command will interpret the dot as the string concatenation operator.

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 ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...