<?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: *nix addon doesn't index CPU number in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289110#M2701</link>
    <description>&lt;P&gt;@encoretickets, If your problem is resolved, please accept the answer to help future readers.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jan 2018 13:02:16 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2018-01-08T13:02:16Z</dc:date>
    <item>
      <title>*nix addon doesn't index CPU number</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289103#M2694</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I've installed the Splunk_TA_nix addon on my indexer. &lt;BR /&gt;
It brings in the cpu statistics but only as a dump.&lt;BR /&gt;
The raw data looks like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2.13       0.00       1.51       0.00       0.00      96.36
0.00       0.00       1.00       0.00       0.00      99.00
2.02       0.00       3.03       0.00       0.00      94.95
5.00       0.00       3.00       0.00       0.00      92.00
0.00       0.00       0.00       0.00       0.00     100.00
8.00       0.00       4.00       0.00       0.00      88.00
1.00       0.00       1.00       0.00       0.00      98.00
1.00       0.00       0.00       0.00       0.00      99.00
0.00       0.00       0.00       0.00       0.00     100.00
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But when I run /opt/splunk/etc/apps/Splunk_TA_nix/bin/cpu.sh I get this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;CPU    pctUser    pctNice  pctSystem  pctIowait    pctIdle
all       4.01       0.00       1.25       0.00      94.74
0         1.00       0.00       2.00       0.00      97.00
1         2.00       0.00       0.00       0.00      98.00
2         3.03       0.00       0.00       0.00      96.97
3         0.00       0.00       0.00       0.00     100.00
4         1.00       0.00       1.00       0.00      98.00
5        20.79       0.00       1.98       0.00      77.23
6         2.00       0.00       4.00       0.00      94.00
7         0.00       0.00       1.00       0.00      99.00
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Where is the CPU number (and "all") has gone? &lt;BR /&gt;
I haven't changed anything in the files, only enabled cpu monitoring.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 17:29:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289103#M2694</guid>
      <dc:creator>encoretickets</dc:creator>
      <dc:date>2020-09-29T17:29:56Z</dc:date>
    </item>
    <item>
      <title>Re: *nix addon doesn't index CPU number</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289104#M2695</link>
      <description>&lt;P&gt;What is your issue exactly ? Are you able to see logs with the appropriate sourcetype? Search for sourcetype=cpu if you are getting logs then the app is working fine&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 12:54:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289104#M2695</guid>
      <dc:creator>mayurr98</dc:creator>
      <dc:date>2018-01-05T12:54:27Z</dc:date>
    </item>
    <item>
      <title>Re: *nix addon doesn't index CPU number</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289105#M2696</link>
      <description>&lt;P&gt;I can't search for the "all" CPU metrics. Or in fact for any given core because the core id is missing from the index.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 13:03:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289105#M2696</guid>
      <dc:creator>encoretickets</dc:creator>
      <dc:date>2018-01-05T13:03:22Z</dc:date>
    </item>
    <item>
      <title>Re: *nix addon doesn't index CPU number</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289106#M2697</link>
      <description>&lt;PRE&gt;&lt;CODE&gt; index=os sourcetype=cpu CPU=all
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Are you getting results for this search?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 16:51:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289106#M2697</guid>
      <dc:creator>mayurr98</dc:creator>
      <dc:date>2018-01-05T16:51:17Z</dc:date>
    </item>
    <item>
      <title>Re: *nix addon doesn't index CPU number</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289107#M2698</link>
      <description>&lt;P&gt;Nope, nothing.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 16:59:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289107#M2698</guid>
      <dc:creator>encoretickets</dc:creator>
      <dc:date>2018-01-05T16:59:59Z</dc:date>
    </item>
    <item>
      <title>Re: *nix addon doesn't index CPU number</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289108#M2699</link>
      <description>&lt;P&gt;refer this link&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/152670/why-is-cpu-sh-script-being-indexed-incorrectly-in-splunk-app-for-unix-and-linux-splunk-ta-nix.html"&gt;https://answers.splunk.com/answers/152670/why-is-cpu-sh-script-being-indexed-incorrectly-in-splunk-app-for-unix-and-linux-splunk-ta-nix.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Also for enabling the input you should use best practices i.e. refer below link&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/UnixAddOn/5.2.4/User/Enabledataandscriptedinputs#Enable_the_data_and_scripted_inputs_with_configuration_files"&gt;https://docs.splunk.com/Documentation/UnixAddOn/5.2.4/User/Enabledataandscriptedinputs#Enable_the_data_and_scripted_inputs_with_configuration_files&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 18:09:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289108#M2699</guid>
      <dc:creator>mayurr98</dc:creator>
      <dc:date>2018-01-05T18:09:19Z</dc:date>
    </item>
    <item>
      <title>Re: *nix addon doesn't index CPU number</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289109#M2700</link>
      <description>&lt;P&gt;Here is the solution: &lt;A href="http://docs.splunk.com/Documentation/UnixAddOn/5.2.4/User/Releasenotes"&gt;http://docs.splunk.com/Documentation/UnixAddOn/5.2.4/User/Releasenotes&lt;/A&gt;&lt;BR /&gt;
Thanks for the help mayurr98!&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 10:29:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289109#M2700</guid>
      <dc:creator>encoretickets</dc:creator>
      <dc:date>2018-01-08T10:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: *nix addon doesn't index CPU number</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289110#M2701</link>
      <description>&lt;P&gt;@encoretickets, If your problem is resolved, please accept the answer to help future readers.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jan 2018 13:02:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/nix-addon-doesn-t-index-CPU-number/m-p/289110#M2701</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2018-01-08T13:02:16Z</dc:date>
    </item>
  </channel>
</rss>

