Getting Data In

Syslog vs TA apps to parse network traffic sourcetypes

sdintino_splunk
Splunk Employee
Splunk Employee

We are trying to ingest some logs for events from different network appliances such as F5 load balancers.  Can you please tell us whether we should be logging them to a syslog and ingesting them from there or if we should be collecting them with splunk listening on a UDP port?

Labels (1)
0 Karma

sdintino_splunk
Splunk Employee
Splunk Employee

Thank you @richgalloway and @isoutamo ! This confirms what I'd thought. Much appreciated!

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Best Practice is to NOT log UDP/TCP directly to Splunk.  Doing so can lead to data loss.  Syslog events should go to a syslog server.

---
If this reply helps you, Karma would be appreciated.

isoutamo
SplunkTrust
SplunkTrust

Hi

just like @richgalloway said. If you are logging UDP directly to splunk it’s not if you lost events, it’s how often and how much you will be lost them.

r. Ismo

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 ...