Splunk Search

Where and or statement for multiple values

codedtech
Path Finder

Hello,

I'm building a search that tracks the use of memory allocated(mem_alloc), memory in use(mem_used), CPU in use(CPU_used) CPU allocated (CPU_alloc) along with the Cluster type (CT) for our vmware envrioment. My base query works perfect but when I try to build the logic behind it using where, and , or. I keep getting false positives, like the example below.

where CT=Tier_1 or CT=Tier_2 and CPU_used>=50 or mem_used>=50  or mem_alloc>=0.9 or CPU_alloc>=0.9 

I end up getting results that have different cluster tiers in them

|CT | |CPU_used| |mem_used| |mem_alloc| |CPU_alloc|
|Tier_2 |50.01| |25.35| |.82 | |.82 |
|Tier_1 |62.23| |72.33| |.90 | |.65 |
|Tier_2 |45.53| |32.55| |.97 | |.55 |
|Tier_4 |23.25| |36.58| |1.01| |3.25|
|Tier_5 |40.32| |85.15| |3.25| |1.11|
I need to find a way to be able to narrow it down to Tier_1 or Tier_2 clusters only, and alert if any of the values break the thresholds in the where statements.

0 Karma

mayurr98
Super Champion

try this?

where (CT=Tier_1 or CT=Tier_2) AND (CPU_used>=50 or mem_used>=50  or mem_alloc>=0.9 or CPU_alloc>=0.9) 
0 Karma

codedtech
Path Finder

That worked, how would I repeat the process for Tier_3 where the values are different from Tier_1 and Tier 2 in the same query?

0 Karma

mayurr98
Super Champion

try:

((CT=Tier_1 or CT=Tier_2) AND (CPU_used>=50 or mem_used>=50  or mem_alloc>=0.9 or CPU_alloc>=0.9)) OR (CT=Tier_3 AND ( cpu_used>50 OR mem_used>60...))

Please upvote/accept the answer if it works for you.

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

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...