Getting Data In

How do I identify UDP source on Splunk Indexer?

congoland
Engager

I'm fairly new to Splunk and inherited a messy environment. I'm trying to dissect log sources. I have 3 indexers that are receiving UDP logs and placing them in an index named "firewall" and am trying to figure out the UDP source so I can turn off logging.

When I search against the firewall index, I get multiple hosts but the source is always the same:
source = udp:11514

I checked the data inputs but don't see this UDP port defined with the specific firewall index name. What's the best way to determine where these UDP logs are coming from? It's possible that there's a rogue heavy forwarder that's sending them. Assume nothing's documented and best practices were not followed during configuration. Thank you.

0 Karma

rg33
Explorer

Are you using the CLI to show inputs? Try:

splunk cmd btool inputs list --debug

or this search processing language (SPL) for each forwarder:

| rest https://<forwarder-ip-address>:8089 /services/data/inputs/monitor

Maybe one of these will help track it down.

Or, if you want you can check the indexer listening ports, and run tcpdump to listen for incoming traffic. Here are some commands to help that:

netstat -aln |grep LISTEN
tcpdump -lnn port 11514

Hope this helps.

/rg

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!

From Raw Data to Executive-Ready Stories, Faster

Build Data Stories for Every Audience  A dashboard is rarely just a dashboard. It might be the view an ...

Guided Onboarding with Auto-schema Is Now Generally Available

  We are excited to announce the General Availability of Guided Onboarding with Auto-Schematization ...

ATTENTION: We’re Moving! (AGAIN!)

The Splunk Community Slack is undergoing a system migration to keep our workspace secure and ...