Splunk Search

Using a stats avg function after an eval case command to categorise

ebs
Communicator

Hi,

I have a requirement where we need to categorise events based on the url into 4 separate categories, then calculate the average response time for each category. Finally we want to display all the averages by category together in a stats table, is there an easy way to do this?

Labels (3)
0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi @ebs,

the problem is to find a rule to categorize urls, if e.g. you have this rule:

in the uri field you have

localhost/* --> Cat. A

community/* --> Cat. B

splunk.com/ --> Cat. C

others--> Cat. D

you can try something like this:

index=your_index
| eventstats count As total
| eval type="D"
| eval type=case(match(uri,"localhost"),"A",match(uri,"community"),"B", match(uri,"splunk.com"),"C")
| stats avg(response_time) AS response_time count values(total) AS total BY type
| eval perc=round(count/total*100,2)
| table type response_time perc

Ciao.

Giuseppe

 

View solution in original post

gcusello
SplunkTrust
SplunkTrust

Hi @ebs,

the problem is to find a rule to categorize urls, if e.g. you have this rule:

in the uri field you have

localhost/* --> Cat. A

community/* --> Cat. B

splunk.com/ --> Cat. C

others--> Cat. D

you can try something like this:

index=your_index
| eventstats count As total
| eval type="D"
| eval type=case(match(uri,"localhost"),"A",match(uri,"community"),"B", match(uri,"splunk.com"),"C")
| stats avg(response_time) AS response_time count values(total) AS total BY type
| eval perc=round(count/total*100,2)
| table type response_time perc

Ciao.

Giuseppe

 

gcusello
SplunkTrust
SplunkTrust

Hi @ebs,

good for you, see next time!
Ciao and happy splunking.

Giuseppe

P.S.: Karma Points are appreciated 😉

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...