Splunk Search

How to Use IF or Case condition

alex5441
Explorer

Hi,

My logs are in following format:

{[-]

logger: .......

message: ..........

severity: Error

}

{[-]

exception: .........

logger: .......

message: ..........

severity: Error

}

my query is :

........| rex "\"exception\":\"(<ErrorMsg>.*?)\"" | table Application, ErrorMsg

 

The issue:

As some app logs have key "message" and some logs have both "exception" and "message".

How can I change my query that first it checks if there is key exception, if it does get the value of that key. If there is no Key exception check if there is key "message", if it does get the value of that.

My current query is able to get the value of exception (if I change exception to message, it gets the value of message. But trying to implement IF or CASE condition here) 

Labels (2)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Try something like:

| rex "(\"exception\":\"(?<ErrorMsg>.*?)\"|\"message\":\"(?<Message>.*?)\")"
0 Karma

alex5441
Explorer

Thank you ITWhisperer,

But I am getting error in compile:

error.PNGerror.PNG

 

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Try with different names as in my example

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!

At .conf26, Don’t Just See What’s Next. Help Shape It at Innovation Labs.

Long before a new capability reaches the keynote stage, it begins as an idea waiting to be tested. At ...

Forwarder Topology Guidance: Intermediate HF vs Intermediate UF

Why Universal Forwarders Should Not Be Used as Intermediate Forwarders A practical Splunk forwarding topology ...

Data Management Digest – August 2026

Data Management Digest   Welcome to the August 2026 edition of Data Management Digest! August was a big month ...