<?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: Exposing sustained CPU and Memory spike in Perfmon data in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Exposing-sustained-CPU-and-Memory-spike-in-Perfmon-data/m-p/304589#M57445</link>
    <description>&lt;P&gt;Streamstats (&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Streamstats" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Streamstats&lt;/A&gt;) is your friend here. &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;source="perfmon:CPU" OR source="perfmon:memory" counter="% Processor Time" OR counter="% Committed Bytes In Use" |  streamstats min(_time) AS startTime, max(_time) AS endTime reset_before="(Value&amp;lt;75)" by host| eval timeSpan = endTime-startTime | search timeSpan&amp;gt;300&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;What we're doing here is taking the first appearance of an event over 75% and continuing to group subsequent events together until the CPU usage is less than 75%. At that point, we reset the start and end times. The eval then creates a timeSpan, so how long we were over 75% usage. Finally, the search then gives us our threshold, in this case 5 minutes (300 seconds).&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 13:25:46 GMT</pubDate>
    <dc:creator>beatus</dc:creator>
    <dc:date>2020-09-29T13:25:46Z</dc:date>
    <item>
      <title>Exposing sustained CPU and Memory spike in Perfmon data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Exposing-sustained-CPU-and-Memory-spike-in-Perfmon-data/m-p/304587#M57443</link>
      <description>&lt;P&gt;Hey guys - today, I have a simple query that returns hosts that have hit a max of 75% CPU or memory usage over a given time. This works great; however, I would like to change this so that the host only appears if it breached that 75% limit for several minutes.. How would I do that? &lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;source="perfmon:CPU" OR source="perfmon:memory" counter="% Processor Time" OR counter="% Committed Bytes In Use" Value&amp;gt;75 |    chart Max(Value)  by host counter |rename "% Committed Bytes In Use" as "Memory Usage", "% Processor Time" as "CPU Usage"&lt;/P&gt;</description>
      <pubDate>Wed, 29 Mar 2017 14:16:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Exposing-sustained-CPU-and-Memory-spike-in-Perfmon-data/m-p/304587#M57443</guid>
      <dc:creator>babecassisgenet</dc:creator>
      <dc:date>2017-03-29T14:16:52Z</dc:date>
    </item>
    <item>
      <title>Re: Exposing sustained CPU and Memory spike in Perfmon data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Exposing-sustained-CPU-and-Memory-spike-in-Perfmon-data/m-p/304588#M57444</link>
      <description>&lt;P&gt;maybe try the bin span=10m _time&lt;BR /&gt;
you can set the span to your preference and then use timechart command. something like this:&lt;BR /&gt;
    index = perfmon source="perfmon:CPU" OR source="perfmon:memory" counter="% Processor Time" OR counter="% Committed Bytes In Use" Value&amp;gt;75 | bin span=5m _time | timechart max(Value) by host&lt;BR /&gt;
hope it helps&lt;/P&gt;</description>
      <pubDate>Wed, 29 Mar 2017 16:01:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Exposing-sustained-CPU-and-Memory-spike-in-Perfmon-data/m-p/304588#M57444</guid>
      <dc:creator>adonio</dc:creator>
      <dc:date>2017-03-29T16:01:25Z</dc:date>
    </item>
    <item>
      <title>Re: Exposing sustained CPU and Memory spike in Perfmon data</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Exposing-sustained-CPU-and-Memory-spike-in-Perfmon-data/m-p/304589#M57445</link>
      <description>&lt;P&gt;Streamstats (&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Streamstats" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Streamstats&lt;/A&gt;) is your friend here. &lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;source="perfmon:CPU" OR source="perfmon:memory" counter="% Processor Time" OR counter="% Committed Bytes In Use" |  streamstats min(_time) AS startTime, max(_time) AS endTime reset_before="(Value&amp;lt;75)" by host| eval timeSpan = endTime-startTime | search timeSpan&amp;gt;300&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;What we're doing here is taking the first appearance of an event over 75% and continuing to group subsequent events together until the CPU usage is less than 75%. At that point, we reset the start and end times. The eval then creates a timeSpan, so how long we were over 75% usage. Finally, the search then gives us our threshold, in this case 5 minutes (300 seconds).&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 13:25:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Exposing-sustained-CPU-and-Memory-spike-in-Perfmon-data/m-p/304589#M57445</guid>
      <dc:creator>beatus</dc:creator>
      <dc:date>2020-09-29T13:25:46Z</dc:date>
    </item>
  </channel>
</rss>

