Getting Data In

Is it normal to have both sourcetype UDP:514 and sourcetype syslog?

jgorman_THG
Explorer

Hello,

My colleague configured 1 heavy forwarder and I configured the other 2. In my Splunk, I see both sourcetype UDP:514 and sourcetype syslog.

Is this normal, or did we set different sourcetypes when we set them up?

We used the CLI and when I check \splunk\home\etc\local\inputs.conf the file has almost nothing in it, except the host...

Can someone tell me where I can go to compare on the 2 systems if we have set different sourcetypes?

Thanks,

0 Karma

s2_splunk
Splunk Employee
Splunk Employee

Best practice for ingesting syslog data is to send it to a syslog/syslog-ng server, which writes to directories/files and have a universal forwarder monitor those files. Only this approach allows you to assign proper sourctypes to your log data. "syslog" is not a very meaningful sourcetype, when users want to try and find logs from firewalls, IPSs, switches, etc.

Having said that: You can run a search to identify which of your HFs is sending which sourcetype and then check your configuration on the relevant server.
You can also run

./splunk cmd btool inputs list --debug

to list out all configuration settings for inputs.conf and it will tell you which configuration file it was taken from.

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...