Splunk Search

count by response time range

jibiuthaman
Explorer

source aaa| eval Description=case(rt_sec>10, "G10", rt_sec>20, "G20", rt_sec>30, "G30", rt_sec>40, "G40") | stats count by Description

this seems to only give me results for G10 even though I have many cases with response times greater then 10 sec... if i just do source aaa rt_sec > 20, I get results. Please help me find the issue here.

Tags (2)
0 Karma
1 Solution

somesoni2
Revered Legend

Try this.

source=aaa | eval Description=case(rt_sec>10 AND rt_sec<=20,"G10", rt_sec>20 AND rt_sec<=30,"G20",rt_sec>30 AND rt_sec<=40,"G40",rt_sec>40,"G10")| stats count by Description

View solution in original post

somesoni2
Revered Legend

Try this.

source=aaa | eval Description=case(rt_sec>10 AND rt_sec<=20,"G10", rt_sec>20 AND rt_sec<=30,"G20",rt_sec>30 AND rt_sec<=40,"G40",rt_sec>40,"G10")| stats count by Description

ksuyash
Explorer

I'm having similar query but when using the below case .. onlt <=500 and >=1500 are getting counted in stats 
duration =6000's are also getting counted in >1500ms case not sure why

index=*
| rex "TxDurationInMillis=(?<TxDurationInMillis>\d+)"
| eval ResponseTime = tonumber(TxDurationInMillis)
| eval ResponseTimeCase=case(
ResponseTime <= 500, "<=500ms",
ResponseTime > 500 AND ResponseTime <= 1000, ">500ms and <=1000ms",
ResponseTime > 1000 AND ResponseTime <= 1400, ">1000ms and <=1400ms",
ResponseTime > 1400 AND ResponseTime < 1500, ">1400ms and <1500ms",
ResponseTime >= 1500, ">=1500ms"
)
| table TxDurationInMillis ResponseTime ResponseTimeCase
0 Karma

jibiuthaman
Explorer

Work and thanks again..

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!

[Puzzles] Solve, Learn, Repeat: Classic British Rock Bands

This puzzle series (first published here) is based on extracting information from statements about well-known ...

New to the Community? Join Us for an Exclusive Post .conf26 Welcome Session (Plus a ...

Keep the .conf26 Energy Going: Welcome to the Splunk Community! Whether we scanned your badge at the Community ...

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Register to Attend   Join our Tech Talk ...