https://community.splunk.com/t5/Deployment-Architecture/Using-DeploymentServer-to-deploy-Splunk-Tech-Add-On-for-NIX/m-p/79138#M2771 <P>Since your requirements are to have different configs on a per-server basis, then I would advise that you ship the Splunk_TA_nix with the inputs disabled and then use your separate/existing server classes to enable the inputs selectively.</P> Mon, 28 Sep 2020 12:33:18 GMT araitz 2020-09-28T12:33:18Z https://community.splunk.com/t5/Deployment-Architecture/Using-DeploymentServer-to-deploy-Splunk-Tech-Add-On-for-NIX/m-p/79137#M2770 <P>I have a deploymentServer and a couple dozen DeploymentClients. All deploymentClients are universal forwarders.</P> <P>There are several server classes defined within the deploymentServer. Examples are: linux_servers, production_servers, test_servers, application_A_servers, application_B_servers, etc.</P> <P>Using the Tech AddOn for Unix, I want to collect server level details, but not all the same details for all Forwarders. I want to collect more data from prod servers than test servers for example. I may need memory data for application A but not application B. We're running up against our indexing limit so I want to be precise about what I collect and what I don't.</P> <P>I have TA for UNIX working on every host, but it's configured separately on each host which is a pain, so I thought of using the deployment server for this.</P> <P>I removed the TA for UNIX on a test host, created a new server class on the deployment server ("Splunk_TA_nix") and have successfully gotten the results I configured from the test host. So I know this is a possibility. However, this doesn't allow me to vary the data I collect based on other server classes.</P> <P>Splunk_TA_nix has a bin directory with many scripts referenced in its inputs.conf file. The format is as such: <BR /> [script://./bin/hardware.sh]</P> <P>SHOULD I . . . </P> <P>Delete the new server class Splunk_TA_nix. Make all changes to existing inputs.conf files for already-defined server classes. [[ I would either make copies of the Splunk_TA_nix/bin directory in all the server class directories (making the script references accurate) or change the script references to point to a single bin source.]]</P> <P>???</P> <P>This seems a little messy to me but I haven't come up with any other ideas.</P> <P>Thoughts?</P> Wed, 03 Oct 2012 21:54:49 GMT https://community.splunk.com/t5/Deployment-Architecture/Using-DeploymentServer-to-deploy-Splunk-Tech-Add-On-for-NIX/m-p/79137#M2770 krussell101 2012-10-03T21:54:49Z https://community.splunk.com/t5/Deployment-Architecture/Using-DeploymentServer-to-deploy-Splunk-Tech-Add-On-for-NIX/m-p/79138#M2771 <P>Since your requirements are to have different configs on a per-server basis, then I would advise that you ship the Splunk_TA_nix with the inputs disabled and then use your separate/existing server classes to enable the inputs selectively.</P> Mon, 28 Sep 2020 12:33:18 GMT https://community.splunk.com/t5/Deployment-Architecture/Using-DeploymentServer-to-deploy-Splunk-Tech-Add-On-for-NIX/m-p/79138#M2771 araitz 2020-09-28T12:33:18Z