https://community.splunk.com/t5/Getting-Data-In/Can-you-group-configuration-files-to-simplify-each-app-in-Splunk/m-p/341227#M62893 <P>Hi deodion,<BR /> I usually use one TA for outputs.conf and many TAs for different inputs.conf.<BR /> Bye.<BR /> Giuseppe</P> Mon, 18 Sep 2017 11:30:09 GMT gcusello 2017-09-18T11:30:09Z https://community.splunk.com/t5/Getting-Data-In/Can-you-group-configuration-files-to-simplify-each-app-in-Splunk/m-p/341226#M62892 <P>Is there any guideline or best practice what .conf to put in gui/indexer/forwarder level?</P> <P>I mean each .conf has its purpose and a lot of settings, but maybe in practice we can somehow isolate its complexity by grouping the .conf for each level?</P> <P>Or at least minimize complexity.</P> <P>Like for example, forwarder usually boils down to at minimum app.conf, inputs.conf, outputs.conf</P> Mon, 18 Sep 2017 11:25:51 GMT https://community.splunk.com/t5/Getting-Data-In/Can-you-group-configuration-files-to-simplify-each-app-in-Splunk/m-p/341226#M62892 deodion 2017-09-18T11:25:51Z https://community.splunk.com/t5/Getting-Data-In/Can-you-group-configuration-files-to-simplify-each-app-in-Splunk/m-p/341227#M62893 <P>Hi deodion,<BR /> I usually use one TA for outputs.conf and many TAs for different inputs.conf.<BR /> Bye.<BR /> Giuseppe</P> Mon, 18 Sep 2017 11:30:09 GMT https://community.splunk.com/t5/Getting-Data-In/Can-you-group-configuration-files-to-simplify-each-app-in-Splunk/m-p/341227#M62893 gcusello 2017-09-18T11:30:09Z