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!

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...