Splunk Search

Help with Eval

a212830
Champion

Hi,

I'm trying to do an eval, but it's not working, and could use another set of eyes.

I extract my data in the props.conf on the SH:

EXTRACT-action  = \<ACTION\>(?<actionTESTA>[^\<]+)\<\/ACTION\>

That part works - it returns values of Discard, Refuse or Allow.

I then have an eval function in my props. right under the extract statement.

EVAL-action=case(actionTESTA="Allow","allowed",actionTESTA="Permit","allowed",actionTESTA="Discard","teardown",actionTESTA="Refuse","blocked",eventTESTA="Connection closed","teardown",eventTESTA="Incomplete connection closed","teardown")

I would expect the eval statement to change values, but it's not.

Anyone?

0 Karma

jnudell_2
Builder

Try:

EVAL-action = case( match(actionTESTA, "Allow|Permit"), "allowed", actionTESTA=="Discard", "teardown", actionTESTA=="Refuse", "blocked", match(eventTESTA, "Connection closed|Incomplete connection closed"), "teardown")

sloshburch
Ultra Champion

As @jnudell_2 is pointing out is that the operators of where and eval isn't like search. See Eval Operators for specifics.

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!

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Splunk Auto Ingestion Parallel Pipeline Scaling

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