https://community.splunk.com/t5/Reporting/splunkdConnectionTimeout/m-p/410844#M6828 <P>Hello.</P> <P>I would like to ask what negative impact the following change in the folder can have?<BR /> /opt/splunk/etc/system/default/web.conf<BR /> for the splunkdConnectionTimeout parameter and leave it at 5000</P> Fri, 25 May 2018 12:12:29 GMT isabelcarvajal 2018-05-25T12:12:29Z https://community.splunk.com/t5/Reporting/splunkdConnectionTimeout/m-p/410844#M6828 <P>Hello.</P> <P>I would like to ask what negative impact the following change in the folder can have?<BR /> /opt/splunk/etc/system/default/web.conf<BR /> for the splunkdConnectionTimeout parameter and leave it at 5000</P> Fri, 25 May 2018 12:12:29 GMT https://community.splunk.com/t5/Reporting/splunkdConnectionTimeout/m-p/410844#M6828 isabelcarvajal 2018-05-25T12:12:29Z https://community.splunk.com/t5/Reporting/splunkdConnectionTimeout/m-p/410845#M6829 <P>First, NEVER edit the files in the <STRONG>default</STRONG> folders. You would want to put any changes into /opt/splunk/etc/system/<STRONG>local</STRONG>/web.conf<BR /> If you edit the files in the default folders, you will loose those changes on the next upgrade/update.<BR /> Making the changes in local, means those changes will persist through upgrades/updates.</P> <P>This setting in particular is the timeout when the front end web is connecting to the backend splunk process. </P> <P>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). </P> Fri, 25 May 2018 17:24:58 GMT https://community.splunk.com/t5/Reporting/splunkdConnectionTimeout/m-p/410845#M6829 solarboyz1 2018-05-25T17:24:58Z