Splunk Dev

If statement with multiple tests?

msarro
Builder

Is it possible to do something like this? It would make my life a whole lot easier if this can be done, or at least something like it...

eval if(((TimeTaken>15) AND ((Termination_Cause=="016") OR (Termination_Cause=="017"))),1,0)

When I try it I get an error stating that the expression is malformed. Any advice is appreciated.

Tags (1)
2 Solutions

ayme
Splunk Employee
Splunk Employee

You're not far off

eval foo=if((TimeTaken>15) AND (Termination_Cause=="016" OR Termination_Cause=="017"),1,0)

View solution in original post

araitz
Splunk Employee
Splunk Employee

You should probably post your whole search, there are might be some extra parenthesis in there.

Note that eval takes the form:

eval <my_field> = <my_eval_expression>

Also, I think you can use searchmatch() here more efficiently:

eval case=searchmatch("TimeTaken>15 AND (Termination_Cause="16" OR Termination_Cause="17")")

If case=true, then the event matches the condition.

View solution in original post

araitz
Splunk Employee
Splunk Employee

You should probably post your whole search, there are might be some extra parenthesis in there.

Note that eval takes the form:

eval <my_field> = <my_eval_expression>

Also, I think you can use searchmatch() here more efficiently:

eval case=searchmatch("TimeTaken>15 AND (Termination_Cause="16" OR Termination_Cause="17")")

If case=true, then the event matches the condition.

araitz
Splunk Employee
Splunk Employee

Please comment when voting down an answer. My answer is perfectly valid.

0 Karma

ayme
Splunk Employee
Splunk Employee

You're not far off

eval foo=if((TimeTaken>15) AND (Termination_Cause=="016" OR Termination_Cause=="017"),1,0)

msarro
Builder

This worked, thanks!

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