Getting Data In

How to group different ip in the input.conf and props.conf

kitkit321
Explorer

Hi All,

here is the question. 

I have some logs form 4 ips and received them at udp 514, for example is 1.1.1.1, 2.2.2.2, 3.3.3.3 and 4.4.4.4

1.1.1.1 and 2.2.2.2 are same sourcetype

3.3.3.3 and 4.4.4.4 are same sourcetype.

For now, my approach is 

input.conf

[udp://1.1.1.1:514]
index = test
sourcetype = pan:firewall

[udp://2.2.2.2:514]
index = test
sourcetype = pan:firewall


[udp://3.3.3.3:514]
index = test
sourcetype = cp_log


[udp://4.4.4.4:514]
index = test
sourcetype = cp_log

prof.conf

[host::1.1.1.1]
TRANSFORMS-throw_dns = throwdns

[host::2.2.2.2]
TRANSFORMS-throw_dns = throwdns

[host::3.3.3.3]
TRANSFORMS-throw_ntp = throwntp

[host::4.4.4.4]
TRANSFORMS-throw_ntp = throwntp

As you can see it in the input.conf and props.conf

1.1.1.1 and 2.2.2.2 share the same configuration.

3.3.3.3 and 4.4.4.4 share the same configuration.

Is there any method to group them up ?

Labels (2)
0 Karma

rsethre
Explorer

Hi

You could configure Splunk to listen on another port, under Data Inputs, UDP, for example port 10514,

and make host 3.3.3.3 and 4.4.4.4 to send syslog to port 10514.

[udp://3.3.3.3:10514]
index = test
sourcetype = cp_log

 

 

 

0 Karma

kitkit321
Explorer

is that possible listen in the same port?

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!

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)

Hello Splunkers,   So you searched, “what is the name of the usb key inserted by bob smith?”  Not gonna lie… ...

Automating Threat Operations and Threat Hunting with Recorded Future

    Automating Threat Operations and Threat Hunting with Recorded Future June 29, 2026 | Register   Is your ...