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!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...