Getting Data In

remove prefix on every events using SEDCMD

roopeshetty
Path Finder

Hi Guys

 

We are getting logs through syslog with its priority / facility data “ <14>1” prepended with every events as below;

 

 

<14>1 2024-01-18T13:45:06.621+0000 756565656565701b-cd27-475e-bab4-3e0e0893d273

<14>1 2024-01-18T13:39:47.014+0000 565gt5t54t-cd27-475e-bab4-565656565gh

 

roopeshetty_1-1705586279086.jpeg

 

 

We are trying to remove this prefix texts “<14>1” using SEDCMD  on props.conf as below;

 

[source::tcp:7514]

SEDCMD-strip-tcp-priority=s/^<\d+>//

 

This is doing almost very close help by removing “<14>” but still “1” is coming up in events. Can some one please help us how to remove this prefix “ <14>1” on every events using SEDCMD ?

 

 

Regards.

Labels (1)
0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust
SEDCMD-strip-tcp-priority=s/^<\d+>\d//

View solution in original post

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust
SEDCMD-strip-tcp-priority=s/^<\d+>\d//
0 Karma

roopeshetty
Path Finder

Hi ITWhisperer,

 

Thanks, its almost done, but i see a space (gap) before the timestamp, how can we delete this space?

roopeshetty_1-1705587291332.png

 

 

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust
SEDCMD-strip-tcp-priority=s/^<\d+>\d\s//

PickleRick
SplunkTrust
SplunkTrust

If you need to tweak your regexes, that's a great interactive tool to test them.

https://regex101.com/

0 Karma
Get Updates on the Splunk Community!

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...

Purpose in Action: How Splunk Is Helping Power an Inclusive Future for All

At Cisco, purpose isn’t a tagline—it’s a commitment. Cisco’s FY25 Purpose Report outlines how the company is ...

[Upcoming Webinar] Demo Day: Transforming IT Operations with Splunk

Join us for a live Demo Day at the Cisco Store on January 21st 10:00am - 11:00am PST In the fast-paced world ...