Getting Data In

Multiple Source types from one host

godzilla74
New Member

Hi All,

New to Splunk> and trying to wrap my head around things... I have a host (it's a Linux Firewall/IDS) that is transmitting all syslog data to my Splunk server. I'm really only concerned about the iptables drops and snort alerts.

I've entered the following in inputs.conf:

[udp://192.168.1.1:514]
sourcetype = snort

[udp://192.168.2.1:514]
sourcetype = snort

*not sure if this is correct...

In my reading of the Splunk docs, it seems that I now need to do something with props.conf so that I can parse the incoming syslog data for snort and iptables logs.

Am I right or totally off? Any help would be great!

Thanks!
Justin

0 Karma

lukejadamec
Super Champion

If your logs are getting indexed and the fields are properly parsed with that config then you have done good so far.

If you want to now drop all but the iptables, drops, and alerts, then you will need to configure props.conf and transforms.conf to save only those events you want to keep. If you decide to drop data at index time then understand that the data will be lost, and will need to be reindexed if you find you need it in Splunk assuming it is also getting stored elsewhere.

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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...