Getting Data In

Can't see my Syslog Source

microbyte
Engager

Real simple one this I'm sure.

I want to monitor syslog of my router. I have gone to Manager->Data inputs->TCP Did port 514, host=IP, source type: Manual, syslog, Index: deafault

This is literally all I have done. If I load up a simple syslog monitor tool then this gets logs from the server.

I can't seem to view these logs anywhere though, it does show me any sources if I use the search app.

Where have I gone wrong?

Tags (1)
0 Karma

Genti
Splunk Employee
Splunk Employee

it CAN be TCP as well. You just need to make sure that you are sending the data as TCP though.

0 Karma

microbyte
Engager

Fixed, needs to be UDP!

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