Dashboards & Visualizations

eval function help with if else statement

thaghost99
Path Finder

hi i would like some help doing an eval function where based on 3 values of fields will determine if the eval field value be either OK or BAD

 

example these are the 4 fields in total (hostname, "chassis ready", result, synchronize)

hostname= alpha        "chassis ready"=yes    result=pass   synchronize=no

hostname= beta          "chassis ready"=yes    result=pass   synchronize=yes

hostname= charlie        "chassis ready"=no   result=pass   synchronize=yes

 

i would like to do an eval for 'overallpass' where if   ("chassis ready"=yes    result=pass   synchronize=yes) will make 'overallpass' = OK and everything else will be overallpass = 'Not Okay" by hostname

 

so based on the top table, 

here is the final output.

*************************************

Hostname         overallpass

alpha                   Not Okay

bravo                   OK

charlie                 Not Okay

 

0 Karma
1 Solution

bowesmana
SplunkTrust
SplunkTrust

Use this

| eval overallpass=if('chassis ready'="yes" AND result="pass" AND synchronize="yes", "OK", "Not Okay")
| stats values(overallpass) as overallpass by hostname

NB: The chassis ready must be surrounded by SINGLE quotes as eval needs to understand the space is part of the field name. The values must be double quoted.

 

View solution in original post

bowesmana
SplunkTrust
SplunkTrust

Use this

| eval overallpass=if('chassis ready'="yes" AND result="pass" AND synchronize="yes", "OK", "Not Okay")
| stats values(overallpass) as overallpass by hostname

NB: The chassis ready must be surrounded by SINGLE quotes as eval needs to understand the space is part of the field name. The values must be double quoted.

 

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