<?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: Example of how to measure server CPU usage? in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Example-of-how-to-measure-server-CPU-usage/m-p/494085#M8360</link>
    <description>&lt;P&gt;&lt;EM&gt;The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the &lt;A href="https://docs.splunk.com/Documentation/UseCases" target="_blank"&gt;Splunk Platform Use Cases&lt;/A&gt; manual.&lt;/EM&gt;&lt;/P&gt;

&lt;H2&gt;&lt;EM&gt;For more information about this example see &lt;A href="https://docs.splunk.com/Documentation/ITSI/latest/IModules/OSModuleKPIsandthresholds" target="_blank"&gt;Operating System Module KPIs and thresholds&lt;/A&gt; in the &lt;EM&gt;Splunk IT Service Intelligence Modules&lt;/EM&gt; manual.&lt;/EM&gt;&lt;/H2&gt;

&lt;P&gt;System Administration teams need to know when servers are running out of CPU space to avoid potential issues. Set up server and operating system (OS) monitoring for your environment and leverage the searches in this example use case to pinpoint errors, prevent business outages through the monitoring of CPU, memory, disk, and network metrics.&lt;/P&gt;

&lt;H1&gt;Load data&lt;/H1&gt;

&lt;P&gt;&lt;STRONG&gt;How to implement:&lt;/STRONG&gt; This example use case depends on data from operating system events.&lt;/P&gt;

&lt;P&gt;Complete the following steps to set up this example use case:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Install and configure the &lt;A href="https://splunkbase.splunk.com/app/742/" target="_blank"&gt;Splunk Add-on for Microsoft Windows &lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Install and configure the &lt;A href="https://splunkbase.splunk.com/app/833/" target="_blank"&gt;Splunk Add-on Unix and Linux&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Enable the basic data collection for storage usage with the &lt;CODE&gt;[script://./bin/df.sh]&lt;/CODE&gt; input of the Splunk Add-on for Unix and Linux and/or the &lt;CODE&gt;[perfmon://LogicalDisk]&lt;/CODE&gt; input of the Splunk Add-on for Microsoft Windows.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Review the following resources for more details:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://answers.splunk.com/answers/770120" target="_blank"&gt;Best Practices for implementing Unix and Linux OS monitoring?&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://answers.splunk.com/answers/770117" target="_blank"&gt;Best Practices for implementing Windows OS monitoring?&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;&lt;STRONG&gt;Best practic&lt;/STRONG&gt; For more granular results with scripted inputs, you can increase the frequency at which the input runs using the &lt;CODE&gt;interval&lt;/CODE&gt; setting in inputs.conf. Running the input more frequently consumes more storage, and running it less frequently uses less, which can affect license consumption. The default interval is 60 seconds. See &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf#Scripted_Input:" target="_blank"&gt;Scripted Input&lt;/A&gt; in the &lt;EM&gt;input.conf&lt;/EM&gt; topic of the &lt;EM&gt;Splunk Enterprise Admin&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; For all of the data inputs, specify a desired target index to provide a more sustainable practice for data access controls and retention models. By default, Splunk collects the data in the default index named &lt;CODE&gt;main&lt;/CODE&gt;.&lt;/P&gt;

&lt;H1&gt;Get insights&lt;/H1&gt;

&lt;P&gt;Run the following search.&lt;BR /&gt;
&lt;PRE&gt;index=* tag=oshost tag=performance tag=cpu&lt;BR /&gt;
| timechart span=1min avg(cpu_load_percent) BY host&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; In searches, replace the asterisk in &lt;CODE&gt;index=*&lt;/CODE&gt; with the name of the &lt;A href="https://docs.splunk.com/Splexicon:Index" target="_blank"&gt;index&lt;/A&gt; that contains the data. By default, Splunk stores data in the &lt;CODE&gt;main&lt;/CODE&gt; index. Therefore, &lt;CODE&gt;index=*&lt;/CODE&gt; becomes &lt;CODE&gt;index=main&lt;/CODE&gt;. Use the &lt;CODE&gt;OR&lt;/CODE&gt; operator to &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Search/Searchindexes#Specify_one_or_multiple_indexes_to_search" target="_blank"&gt;specify one or multiple indexes to search&lt;/A&gt;. For example, &lt;CODE&gt;index=main OR index=security&lt;/CODE&gt;. See &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Aboutmanagingindexes" target="_blank"&gt;About managing indexes&lt;/A&gt; and &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Howindexingworks" target="_blank"&gt;How indexing works&lt;/A&gt; in Splunk docs for details.&lt;/P&gt;

&lt;H1&gt;Help&lt;/H1&gt;

&lt;P&gt;The &lt;A href="https://docs.splunk.com/Documentation/ITSI/latest/IModules/OSModuletroubleshooting" target="_blank"&gt;Operating System Module troubleshooting&lt;/A&gt; section in the Splunk IT Service Intelligence &lt;EM&gt;Modules&lt;/EM&gt; manual lists troubleshooting resources that you can apply to this example use case.&lt;/P&gt;

&lt;P&gt;If no results appear, it may be because the add-ons were not deployed to the search heads, so the needed tags and fields are not defined. Deploy the add-ons to the search heads to access the needed tags and fields. See &lt;A href="https://docs.splunk.com/Documentation/AddOns/released/Overview/Installingadd-ons" target="_blank"&gt;About installing Splunk add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For troubleshooting tips that you can apply to all add-ons, see &lt;A href="http://docs.splunk.com/Documentation/AddOns/released/Overview/Troubleshootadd-ons" target="_blank"&gt;Troubleshoot add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For more support, &lt;A href="https://answers.splunk.com/answers/ask.html?topics=usecase" target="_blank"&gt;post a question to the Splunk Answers community&lt;/A&gt;.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2020 03:53:09 GMT</pubDate>
    <dc:creator>sloshburch</dc:creator>
    <dc:date>2020-09-30T03:53:09Z</dc:date>
    <item>
      <title>Example of how to measure server CPU usage?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Example-of-how-to-measure-server-CPU-usage/m-p/494084#M8359</link>
      <description>&lt;P&gt;Does anyone have examples of how to use Splunk to measure server CPU usage?     &lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2020 18:34:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Example-of-how-to-measure-server-CPU-usage/m-p/494084#M8359</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2020-01-29T18:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: Example of how to measure server CPU usage?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Example-of-how-to-measure-server-CPU-usage/m-p/494085#M8360</link>
      <description>&lt;P&gt;&lt;EM&gt;The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the &lt;A href="https://docs.splunk.com/Documentation/UseCases" target="_blank"&gt;Splunk Platform Use Cases&lt;/A&gt; manual.&lt;/EM&gt;&lt;/P&gt;

&lt;H2&gt;&lt;EM&gt;For more information about this example see &lt;A href="https://docs.splunk.com/Documentation/ITSI/latest/IModules/OSModuleKPIsandthresholds" target="_blank"&gt;Operating System Module KPIs and thresholds&lt;/A&gt; in the &lt;EM&gt;Splunk IT Service Intelligence Modules&lt;/EM&gt; manual.&lt;/EM&gt;&lt;/H2&gt;

&lt;P&gt;System Administration teams need to know when servers are running out of CPU space to avoid potential issues. Set up server and operating system (OS) monitoring for your environment and leverage the searches in this example use case to pinpoint errors, prevent business outages through the monitoring of CPU, memory, disk, and network metrics.&lt;/P&gt;

&lt;H1&gt;Load data&lt;/H1&gt;

&lt;P&gt;&lt;STRONG&gt;How to implement:&lt;/STRONG&gt; This example use case depends on data from operating system events.&lt;/P&gt;

&lt;P&gt;Complete the following steps to set up this example use case:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Install and configure the &lt;A href="https://splunkbase.splunk.com/app/742/" target="_blank"&gt;Splunk Add-on for Microsoft Windows &lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Install and configure the &lt;A href="https://splunkbase.splunk.com/app/833/" target="_blank"&gt;Splunk Add-on Unix and Linux&lt;/A&gt;.&lt;/LI&gt;
&lt;LI&gt;Enable the basic data collection for storage usage with the &lt;CODE&gt;[script://./bin/df.sh]&lt;/CODE&gt; input of the Splunk Add-on for Unix and Linux and/or the &lt;CODE&gt;[perfmon://LogicalDisk]&lt;/CODE&gt; input of the Splunk Add-on for Microsoft Windows.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Review the following resources for more details:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;&lt;A href="https://answers.splunk.com/answers/770120" target="_blank"&gt;Best Practices for implementing Unix and Linux OS monitoring?&lt;/A&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;A href="https://answers.splunk.com/answers/770117" target="_blank"&gt;Best Practices for implementing Windows OS monitoring?&lt;/A&gt;&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;&lt;STRONG&gt;Best practic&lt;/STRONG&gt; For more granular results with scripted inputs, you can increase the frequency at which the input runs using the &lt;CODE&gt;interval&lt;/CODE&gt; setting in inputs.conf. Running the input more frequently consumes more storage, and running it less frequently uses less, which can affect license consumption. The default interval is 60 seconds. See &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf#Scripted_Input:" target="_blank"&gt;Scripted Input&lt;/A&gt; in the &lt;EM&gt;input.conf&lt;/EM&gt; topic of the &lt;EM&gt;Splunk Enterprise Admin&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; For all of the data inputs, specify a desired target index to provide a more sustainable practice for data access controls and retention models. By default, Splunk collects the data in the default index named &lt;CODE&gt;main&lt;/CODE&gt;.&lt;/P&gt;

&lt;H1&gt;Get insights&lt;/H1&gt;

&lt;P&gt;Run the following search.&lt;BR /&gt;
&lt;PRE&gt;index=* tag=oshost tag=performance tag=cpu&lt;BR /&gt;
| timechart span=1min avg(cpu_load_percent) BY host&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Best practice:&lt;/STRONG&gt; In searches, replace the asterisk in &lt;CODE&gt;index=*&lt;/CODE&gt; with the name of the &lt;A href="https://docs.splunk.com/Splexicon:Index" target="_blank"&gt;index&lt;/A&gt; that contains the data. By default, Splunk stores data in the &lt;CODE&gt;main&lt;/CODE&gt; index. Therefore, &lt;CODE&gt;index=*&lt;/CODE&gt; becomes &lt;CODE&gt;index=main&lt;/CODE&gt;. Use the &lt;CODE&gt;OR&lt;/CODE&gt; operator to &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Search/Searchindexes#Specify_one_or_multiple_indexes_to_search" target="_blank"&gt;specify one or multiple indexes to search&lt;/A&gt;. For example, &lt;CODE&gt;index=main OR index=security&lt;/CODE&gt;. See &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Aboutmanagingindexes" target="_blank"&gt;About managing indexes&lt;/A&gt; and &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Howindexingworks" target="_blank"&gt;How indexing works&lt;/A&gt; in Splunk docs for details.&lt;/P&gt;

&lt;H1&gt;Help&lt;/H1&gt;

&lt;P&gt;The &lt;A href="https://docs.splunk.com/Documentation/ITSI/latest/IModules/OSModuletroubleshooting" target="_blank"&gt;Operating System Module troubleshooting&lt;/A&gt; section in the Splunk IT Service Intelligence &lt;EM&gt;Modules&lt;/EM&gt; manual lists troubleshooting resources that you can apply to this example use case.&lt;/P&gt;

&lt;P&gt;If no results appear, it may be because the add-ons were not deployed to the search heads, so the needed tags and fields are not defined. Deploy the add-ons to the search heads to access the needed tags and fields. See &lt;A href="https://docs.splunk.com/Documentation/AddOns/released/Overview/Installingadd-ons" target="_blank"&gt;About installing Splunk add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For troubleshooting tips that you can apply to all add-ons, see &lt;A href="http://docs.splunk.com/Documentation/AddOns/released/Overview/Troubleshootadd-ons" target="_blank"&gt;Troubleshoot add-ons&lt;/A&gt; in the &lt;EM&gt;Splunk Add-ons&lt;/EM&gt; manual.&lt;/P&gt;

&lt;P&gt;For more support, &lt;A href="https://answers.splunk.com/answers/ask.html?topics=usecase" target="_blank"&gt;post a question to the Splunk Answers community&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 03:53:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Example-of-how-to-measure-server-CPU-usage/m-p/494085#M8360</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2020-09-30T03:53:09Z</dc:date>
    </item>
  </channel>
</rss>

