Splunk Search

Why won't If statement evaluate as true?

anjuliwyles
Engager

When I place event.code into an if statement, it will not evaluate as true

 

Currently I have this code:

index = windows-security event.code IN (4624)
| eval Success=if(event.code = "4624", 1, 0)
| stats count by Success

 

Success always evaluates to 0. I have tried using

match(event.code, "4624")

match(event.code, '4624')

match(event.code, ".+")

like(event.code, "4624")

like(event.code, '4624')

I even tried event.code = event.code

 

Always 0.

Labels (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Since event.code probably is an integer have you tried 

 

| eval Success=if(event.code = 4624, 1, 0)

 

It's possible Splunk is struggling with the field name.  Try renaming it before the conditional.

 

| rename event.* as *
| eval Success = if(code=4624, 1, 0)

 

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Since event.code probably is an integer have you tried 

 

| eval Success=if(event.code = 4624, 1, 0)

 

It's possible Splunk is struggling with the field name.  Try renaming it before the conditional.

 

| rename event.* as *
| eval Success = if(code=4624, 1, 0)

 

---
If this reply helps you, Karma would be appreciated.

anjuliwyles
Engager

Renaming the field worked! Thank you

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!

Mastering Threat Intelligence in ES 8.5, Splunk AI Assistant v2, and More from Splunk ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...