I can't seem to find anything on this, forgive me if a duplicate, I've been checking. My company is deploying a newer tool and the developer somehow managed to build a functioning forwarder that only works on port 8089? Does this make any sense? Is there anyone who can explain what use case this is under? The same forwarder does not work on 9997 in it's default input mode.
I can literally "send a test record" from the tool to the splunk server and on 8089 it accepts and we get a fully formed alert in splunk which works with their app and is in the search DB. On any other port including 9997 with splunkd it refused (the comms are tcp on 8089, is that the problem?)
I'm not sure what to do. Can we somehow set up this type of server on 9997 for our cloud instance? Is there any use case for this? I'm trying to use some sort of middle man to convert this but I could use some help/insight. Thank you.
Hi @krisblouch,
to change the default ports in Splunk see at https://docs.splunk.com/Documentation/Splunk/8.0.0/Admin/Changedefaultvalues
Ciao.
Giuseppe