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