Splunk Search

How to write case statement for below log?

Emyamy
Explorer

Hi Splunkers.

I have two level of logs (NOTICE,ERROR), for Error logs(json), method_name and message is automatically getting extracted but not for NOTICE logs, So i have written my case statement like below in UI  and its working fine but im not sure how to deploy this in props.conf

 

index=index_name sourcetype=sourctype_name  log_level=NOTICE
|eval message =case(method_name='protopayload.table.create'=="table created",method_name='protopayload.table.delete'=="table deleted")

i dont want to write case statement for error logs as its already getting extracted fine.

to be precise:- i want my fields extraction to happen automatically for error logs (as its getting extracted automatically) and want my case statement work only for notice logs.

 

Please assist on this

 

 

 

 

Labels (5)
Tags (1)
0 Karma
1 Solution

scelikok
SplunkTrust
SplunkTrust

Hi @Emyamy,

You can user below search for test and put EVAL setting in your sourcetype settings for extraction.

Search sample;
|eval message =case(log_level="NOTICE" AND method_name="protopayload.table.create","table created",log_level="NOTICE" AND method_name="protopayload.table.delete","table deleted")

props.conf
EVAL-message =case(log_level="NOTICE" AND method_name="protopayload.table.create","table created",log_level="NOTICE" AND method_name="protopayload.table.delete","table deleted")

 

If this reply helps you an upvote and "Accept as Solution" is appreciated.

View solution in original post

0 Karma

scelikok
SplunkTrust
SplunkTrust

Hi @Emyamy,

You can user below search for test and put EVAL setting in your sourcetype settings for extraction.

Search sample;
|eval message =case(log_level="NOTICE" AND method_name="protopayload.table.create","table created",log_level="NOTICE" AND method_name="protopayload.table.delete","table deleted")

props.conf
EVAL-message =case(log_level="NOTICE" AND method_name="protopayload.table.create","table created",log_level="NOTICE" AND method_name="protopayload.table.delete","table deleted")

 

If this reply helps you an upvote and "Accept as Solution" is appreciated.
0 Karma

yuanliu
SplunkTrust
SplunkTrust
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!

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...