Getting Data In

For UDP inputs, does the raw log priority factor into LINE_BREAKER?

twinspop
Influencer

If you watch the wire data via tcpdump, you will see syslog events contain the log priority at the beginning of an event:

<134>12/1/14 10:02:03.123 INFO some log info

When defining LINE_BREAKER for this log, do I need to factor in the priority, or is that stripped before that stage?

0 Karma
1 Solution

twinspop
Influencer

Based on my own experiments, no, do not account for the log priority identifier in angle brackets. Pretend like it's not there.

View solution in original post

0 Karma

twinspop
Influencer

Based on my own experiments, no, do not account for the log priority identifier in angle brackets. Pretend like it's not there.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...