All Apps and Add-ons

Question about the ports used for both Splunk and Forwarder

ansred
Explorer

Greetings,

I have Synology as host for Docker containers environment.

I have Splunk installed and running fine. (Host Network)

I have installed the Splunk forwarder App and docker container. (Bridge Network)

    Local port TCP <<<<<>>>>> Container Port TCP
    1088  <<<<<>>>>> 8088
    1089 <<<<<>>>>> 8089
     1997 <<<<<>>>>> 9997

The question, about the ports being using for both Splunk and Forwarder

It says per the wiki that I need to open port 9997 on both containers, which is you can since they are going to be conflicted

Links:
https://splunk.github.io/docker-splunk/SETUP.html#install

I got already the Pi-hole log file ready and good to go

/volume1/docker/Pi-hole/var/log/pihole.log

And I got the forwarder input conf file ready as well
/volume1/docker/Splunk/Splunk-FWD/opt/splunkforwarder/etc/system/local/inputs.conf

And here is its content:

[splunktcp://9997]
disabled = 0

[monitor:/volume1/docker/Pi-hole/var/log/pihole.log]
whitelist = pihole\.lo.+
disabled = false
sourcetype = pihole:log

Her as you see the port for Splunk is listening

root@Synology:~# netstat -plnt | grep ':9997'
tcp        0      0 0.0.0.0:9997            0.0.0.0:*               LISTEN      29533/splunkd       

Any idea how to get it working or what if I missing something?

Thanks
Anas

Labels (2)
0 Karma
Get Updates on the Splunk Community!

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...