Splunk Search

How to Remove dynamic part from error log and group by common error

raghavendrasred
New Member

I want to Remove dynamic part from error log and group by common error
below is the message which will be generated dynamic for each event.
WFFaultCode: 1010 and WFFaultReasonText: (CORE,9v7QgtZ4_pvny0yWx0=)<-10040106> An unhandled exception occurred in CommandExecutor or GroovyExecutor. Error: "(CORE,9v7QgZ4_pvny0yWx0=)<-11130016> To record, the transaction must be active.".

i want to group the above message with common message as shown below and display.
WFFaultCode: An unhandled exception occurred in CommandExecutor or GroovyExecutor. Error: To record, the transaction must be active.".

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

I've done something similar this way.

<your search> | eval message=if(like(message,"WFFaultCode: % An unhandled exception occurred in CommandExecutor or GroovyExecutor. Error: % To record, the transaction must be active."),"WFFaultCode: An unhandled exception occurred in CommandExecutor or GroovyExecutor. Error: To record, the transaction must be active.",message) | ...
---
If this reply helps you, Karma would be appreciated.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

I've done something similar this way.

<your search> | eval message=if(like(message,"WFFaultCode: % An unhandled exception occurred in CommandExecutor or GroovyExecutor. Error: % To record, the transaction must be active."),"WFFaultCode: An unhandled exception occurred in CommandExecutor or GroovyExecutor. Error: To record, the transaction must be active.",message) | ...
---
If this reply helps you, Karma would be appreciated.
0 Karma

raghavendrasred
New Member

Thanks for the quick response.
with full message search as given by you in query it is default going for "message" and displaying message only.

when i tried below one it worked.
| eval message=if(like(message,"WFFaultCode:%"),"WFFaultCode: An unhandled exception occurred in CommandExecutor or GroovyExecutor. Error: To record, the transaction must be active.",message) | ...

Thanks. i got the idea. i will check it may be space or other issue.

0 Karma

yuanliu
SplunkTrust
SplunkTrust

I use case when dealing with such needs. It allows more varieties, although the basic idea is the same. Also, if you are familiar with regex, it can be more powerful if need be. E.g.,

| eval message=case(like(message,"WFFaultCode:%"),"WFFaultCode: An unhandled exception occurred in CommandExecutor or GroovyExecutor. Error: To record, the transaction must be active.",
  match(message,"^AnotherFaultCode: [1-5]\d{2} "),"AnotherFault (1xx - 5xx)..",
  1==1, message) | ...
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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...