https://community.splunk.com/t5/Deployment-Architecture/Forwarding-Linux-command-outputs-to-dashboard/m-p/137961#M5179 <P>You need a <CODE>scripted input</CODE>:</P> <P><A href="http://docs.splunk.com/Documentation/Splunk/latest/AdvancedDev/ScriptedInputsIntro">http://docs.splunk.com/Documentation/Splunk/latest/AdvancedDev/ScriptedInputsIntro</A><BR /> <A href="http://docs.splunk.com/Documentation/Splunk/latest/AdvancedDev/ScriptSetup">http://docs.splunk.com/Documentation/Splunk/latest/AdvancedDev/ScriptSetup</A></P> Sun, 07 Jun 2015 17:24:26 GMT woodcock 2015-06-07T17:24:26Z https://community.splunk.com/t5/Deployment-Architecture/Forwarding-Linux-command-outputs-to-dashboard/m-p/137960#M5178 <P>I'm struggling to understand how I would get the output of a linux command such as vmstat or iostat into splunk where i can use the output to create a time graph.</P> <P>Can someone point me in the right direction at all?</P> <P>Thanks Steve.</P> Sun, 07 Jun 2015 16:30:48 GMT https://community.splunk.com/t5/Deployment-Architecture/Forwarding-Linux-command-outputs-to-dashboard/m-p/137960#M5178 qazwsxedc994 2015-06-07T16:30:48Z https://community.splunk.com/t5/Deployment-Architecture/Forwarding-Linux-command-outputs-to-dashboard/m-p/137961#M5179 <P>You need a <CODE>scripted input</CODE>:</P> <P><A href="http://docs.splunk.com/Documentation/Splunk/latest/AdvancedDev/ScriptedInputsIntro">http://docs.splunk.com/Documentation/Splunk/latest/AdvancedDev/ScriptedInputsIntro</A><BR /> <A href="http://docs.splunk.com/Documentation/Splunk/latest/AdvancedDev/ScriptSetup">http://docs.splunk.com/Documentation/Splunk/latest/AdvancedDev/ScriptSetup</A></P> Sun, 07 Jun 2015 17:24:26 GMT https://community.splunk.com/t5/Deployment-Architecture/Forwarding-Linux-command-outputs-to-dashboard/m-p/137961#M5179 woodcock 2015-06-07T17:24:26Z https://community.splunk.com/t5/Deployment-Architecture/Forwarding-Linux-command-outputs-to-dashboard/m-p/137962#M5180 <P>If you're interested in specifically in the output of <CODE>vmstat</CODE> and <CODE>iostat</CODE> and other standard *nix monitoring scripts, maybe you would want to look into leveraging the work already done in the <A href="https://splunkbase.splunk.com/app/273/">Splunk App for Unix and Linux</A>. There's an <A href="https://splunkbase.splunk.com/app/833/">Add-on that you deploy and configure on your forwarders</A> to gather data on those remote systems, and there's docs about <A href="http://docs.splunk.com/Documentation/UnixApp">the App</A> and the <A href="http://docs.splunk.com/Documentation/UnixAddOn">AddOn</A> on docs.splunk.com</P> Sun, 07 Jun 2015 17:52:28 GMT https://community.splunk.com/t5/Deployment-Architecture/Forwarding-Linux-command-outputs-to-dashboard/m-p/137962#M5180 acharlieh 2015-06-07T17:52:28Z