Splunk Search

splunk where condition

rakeshreddy123
Engager

I have a sample query that i need to apply a where condition to:

index="web" host="blah*" sourcetype="jboss:serverLog" "want 0 out of number from CaCHE "

I need to apply a where condition to see the number greater than 100 in the above query

something like this, from below, i need to apply a where clause to show only those transactions where that number (20,40,60,120) is greater than 100

index="web" host="wjb2*ksc14*" sourcetype="jboss:serverLog" "Fetched 0 Browse Offers out of 20"
index="web" host="wjb2*ksc14*" sourcetype="jboss:serverLog" "Fetched 0 Browse Offers out of 40"
index="web" host="wjb2*ksc14*" sourcetype="jboss:serverLog" "Fetched 0 Browse Offers out of 60"
index="web" host="wjb2*ksc14*" sourcetype="jboss:serverLog" "Fetched 0 Browse Offers out of 120"

Tags (2)
0 Karma

somesoni2
Revered Legend

You would need to extract that number as a field and then apply a filter based on that. Try something like this

index="web" host="wjb2*ksc14*" sourcetype="jboss:serverLog" "Fetched 0 Browse Offers out of" | rex "Fetched 0 Browse Offers out of (?<fetchcount>\d+)" | where fetchcount>100

A better option would be save this field extraction in the props.conf so that you directly filter in the base search.

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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...