https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248199#M47827 <P>That's correct. If you were using Splunk Enterprise instance(not universal forwarder) and your script was simple enough to be developed using standard python library that ships with Splunk, then it would've worked. So many if's so I think you're fine. (its easiness vs best practices).</P> Fri, 20 Jan 2017 20:44:24 GMT somesoni2 2017-01-20T20:44:24Z https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248196#M47824 <P>I have two scripted inputs, one bash script for Linux and one batch script for Windows. Both scripts are written to read a static configuration file and output the data for Splunk to ingest. Both scripts work without issue.</P> <P>Should I deploy both script inputs in the same app? As you know the bash script will not run on Windows and batch script will not run on LInux. Besides the error I get in the splunkd.log, is there anything I should worry about with the scripts executing on the wrong OS architecture?</P> Fri, 20 Jan 2017 20:05:52 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248196#M47824 sjaworski 2017-01-20T20:05:52Z https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248197#M47825 <P>Beside the error, I don't think there is any other issue doing that. It's basically that error message vs maintenance overhead of 2 apps. Have you considered developing the script using some common language like python or perl?</P> Fri, 20 Jan 2017 20:21:32 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248197#M47825 somesoni2 2017-01-20T20:21:32Z https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248198#M47826 <P>There's no guarantee there will be a perl or python interpreter on the destination systems.</P> Fri, 20 Jan 2017 20:37:48 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248198#M47826 sjaworski 2017-01-20T20:37:48Z https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248199#M47827 <P>That's correct. If you were using Splunk Enterprise instance(not universal forwarder) and your script was simple enough to be developed using standard python library that ships with Splunk, then it would've worked. So many if's so I think you're fine. (its easiness vs best practices).</P> Fri, 20 Jan 2017 20:44:24 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248199#M47827 somesoni2 2017-01-20T20:44:24Z https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248200#M47828 <P>Thanks for the thoughts. Always good to double check. </P> Fri, 20 Jan 2017 21:01:09 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248200#M47828 sjaworski 2017-01-20T21:01:09Z https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248201#M47829 <P>I hate errors and would create an app for each OS. You should already have the host discrimination part of <CODE>serverclass.conf</CODE> done for the various TAs that you need to deploy differently depending on OS. But there is nothing that will be broken if you deploy both to both.</P> Fri, 20 Jan 2017 21:53:59 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-deploy-scripted-inputs-on-different-OS-architectures/m-p/248201#M47829 woodcock 2017-01-20T21:53:59Z