Getting Data In

SourceTypes Not Recognized

vragosta
Path Finder

We have some Cisco ASAs logging to Splunk over port 514/UDP, and they are being received fine. But, there is something odd that has been bothering me. The source of all of these logs is still recorded as udp:514 instead of cisco:asa as I would expect.

Can anyone enlighten me as to why this may be?

Thanks!

Tags (1)
0 Karma

vragosta
Path Finder

It looks like someone was fiddling with the transforms.conf file, which caused the asa logs to be classified incorrectly. After changing the regex back to it's original value, everything appears to be working as expected now.

Thanks!

0 Karma

yannK
Splunk Employee
Splunk Employee

Do not mistake source and sourcetype. The source is where the events come from, the sourcetype define the format and purpose.

with an input like

[udp://514]
sourcetype=cisco:asa

the source will be udp:514
if you need to change the source you can add, source=cicso:asa

0 Karma

vragosta
Path Finder

Yes, my mistake. I meant it is detecting the sourcetype improperly. We actually have pix, fwsm, and asa logs all being sent to 514/UDP. However, only the asa logs do not appear with an expected sourcetype. They are recorded with a sourcetype of udp:514 instead of cisco:asa.

Thanks!

0 Karma
Get Updates on the Splunk Community!

Splunk Enterprise Security: Your Command Center for PCI DSS Compliance

Every security professional knows the drill. The PCI DSS audit is approaching, and suddenly everyone's asking ...

Developer Spotlight with Guilhem Marchand

From Splunk Engineer to Founder: The Journey Behind TrackMe    After spending over 12 years working full time ...

Cisco Catalyst Center Meets Splunk ITSI: From 'Payments Are Down' to Root Cause in ...

The Problem: When Networks and Services Don't Talk Payment systems fail at a retail location. Customers are ...