<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Can the S.o.S app use data from the Windows and *nix TA instead of the S.o.S TAs? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Can-the-S-o-S-app-use-data-from-the-Windows-and-nix-TA-instead/m-p/28292#M960</link>
    <description>&lt;P&gt;Scripted inputs 'lsof.sh' and 'ps.sh' from the *nix TA &lt;EM&gt;should&lt;/EM&gt; be compatible with the S.o.S usage resource dashboards, as long as you change the 'set_sos_index' macro in &lt;CODE&gt;$SPLUNK_HOME/etc/apps/sos/local/macros.conf&lt;/CODE&gt; and point it to the index where those scripted inputs are writing events - typically, the 'os' index. Do note, however, that some fixes and improvements we did to the &lt;A href="http://splunk-base.splunk.com/apps/36662/splunk-on-splunk-sos-technology-add-on-for-unix-and-linux"&gt;S.o.S TA for *nix&lt;/A&gt; scripted inputs will not be incorporated to the equivalent inputs in the *nix TA.&lt;/P&gt;

&lt;P&gt;The &lt;A href="http://splunk-base.splunk.com/apps/57188/splunk-on-splunk-sos-technology-add-on-for-windows"&gt;S.o.S TA for Windows&lt;/A&gt; provides a custom-made scripted input ('ps_sos.ps1') that gathers per-process resource usage with a format identical to that of 'ps.sh'. The Windows TA does &lt;STRONG&gt;not&lt;/STRONG&gt; offer such a scripted input.&lt;/P&gt;</description>
    <pubDate>Wed, 08 May 2013 22:35:04 GMT</pubDate>
    <dc:creator>hexx</dc:creator>
    <dc:date>2013-05-08T22:35:04Z</dc:date>
    <item>
      <title>Can the S.o.S app use data from the Windows and *nix TA instead of the S.o.S TAs?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Can-the-S-o-S-app-use-data-from-the-Windows-and-nix-TA-instead/m-p/28291#M959</link>
      <description>&lt;P&gt;I already have the standard Windows TA and Unix TA why do I need to install the SOA TAs? Are they not compatible and if not why can't they be?&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2013 20:36:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Can-the-S-o-S-app-use-data-from-the-Windows-and-nix-TA-instead/m-p/28291#M959</guid>
      <dc:creator>hvandenb</dc:creator>
      <dc:date>2013-05-08T20:36:42Z</dc:date>
    </item>
    <item>
      <title>Re: Can the S.o.S app use data from the Windows and *nix TA instead of the S.o.S TAs?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Can-the-S-o-S-app-use-data-from-the-Windows-and-nix-TA-instead/m-p/28292#M960</link>
      <description>&lt;P&gt;Scripted inputs 'lsof.sh' and 'ps.sh' from the *nix TA &lt;EM&gt;should&lt;/EM&gt; be compatible with the S.o.S usage resource dashboards, as long as you change the 'set_sos_index' macro in &lt;CODE&gt;$SPLUNK_HOME/etc/apps/sos/local/macros.conf&lt;/CODE&gt; and point it to the index where those scripted inputs are writing events - typically, the 'os' index. Do note, however, that some fixes and improvements we did to the &lt;A href="http://splunk-base.splunk.com/apps/36662/splunk-on-splunk-sos-technology-add-on-for-unix-and-linux"&gt;S.o.S TA for *nix&lt;/A&gt; scripted inputs will not be incorporated to the equivalent inputs in the *nix TA.&lt;/P&gt;

&lt;P&gt;The &lt;A href="http://splunk-base.splunk.com/apps/57188/splunk-on-splunk-sos-technology-add-on-for-windows"&gt;S.o.S TA for Windows&lt;/A&gt; provides a custom-made scripted input ('ps_sos.ps1') that gathers per-process resource usage with a format identical to that of 'ps.sh'. The Windows TA does &lt;STRONG&gt;not&lt;/STRONG&gt; offer such a scripted input.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2013 22:35:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Can-the-S-o-S-app-use-data-from-the-Windows-and-nix-TA-instead/m-p/28292#M960</guid>
      <dc:creator>hexx</dc:creator>
      <dc:date>2013-05-08T22:35:04Z</dc:date>
    </item>
  </channel>
</rss>

