Reporting

splunkdConnectionTimeout

isabelcarvajal
New Member

Hello.

I would like to ask what negative impact the following change in the folder can have?
/opt/splunk/etc/system/default/web.conf
for the splunkdConnectionTimeout parameter and leave it at 5000

0 Karma

solarboyz1
Builder

First, NEVER edit the files in the default folders. You would want to put any changes into /opt/splunk/etc/system/local/web.conf
If you edit the files in the default folders, you will loose those changes on the next upgrade/update.
Making the changes in local, means those changes will persist through upgrades/updates.

This setting in particular is the timeout when the front end web is connecting to the backend splunk process.

At a minimum, If there is an issue between the web front-end and the splunkd backend, the session will continue to try for 5000 seconds (1.3 hours) before timing out and informing the user (or whatever process was connecting via splunk web).

0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...