Splunk Search

wrong results for case statement with AND

sam1010
Explorer

I used this eval statement with AND conditions but I'm only getting result as "Public" even when the condition satisfies for value "Private" i.e. I'm only getting default result. Any idea of what's wrong with this statement?

| eval perm=case(block_public_acls=true AND block_public_policy=true AND ignore_public_acls=true AND restrict_public_buckets=true,"Private",1=1,"Public")

sam1010_1-1634196686147.png

 

0 Karma
1 Solution

marilyncugal
Engager

Check the type of the fields. 
e.g.  | eval type_of_field = typeof(block_public_acls)

If it is "String", then you can wrap the right side of the condition with quotation marks.

| eval perm=case(block_public_acls="true" AND block_public_policy="true" AND ignore_public_acls="true" AND restrict_public_buckets="true","Private",1=1,"Public")

View solution in original post

marilyncugal
Engager

Check the type of the fields. 
e.g.  | eval type_of_field = typeof(block_public_acls)

If it is "String", then you can wrap the right side of the condition with quotation marks.

| eval perm=case(block_public_acls="true" AND block_public_policy="true" AND ignore_public_acls="true" AND restrict_public_buckets="true","Private",1=1,"Public")

gcusello
SplunkTrust
SplunkTrust

Hi @sam1010,

use double quotes in all the conditions:

| eval perm=case(block_public_acls="true" AND block_public_policy="true" AND ignore_public_acls="true" AND restrict_public_buckets="true","Private",1=1,"Public")

Ciao.

Giuseppe

ITWhisperer
SplunkTrust
SplunkTrust

Have you tried putting "true" in double quotes?

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