<?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: Trending a calculation in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104556#M27105</link>
    <description>&lt;P&gt;A summary index will solve this problem.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.1/Knowledge/Usesummaryindexing"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.1/Knowledge/Usesummaryindexing&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Lp&lt;/P&gt;</description>
    <pubDate>Thu, 29 Mar 2012 17:36:00 GMT</pubDate>
    <dc:creator>lpolo</dc:creator>
    <dc:date>2012-03-29T17:36:00Z</dc:date>
    <item>
      <title>Trending a calculation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104552#M27101</link>
      <description>&lt;P&gt;I am currently using this search string to determine the number of defects based but I would like to expand it so I can trend it over multiple weeks.    &lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;sourcetype="qualys" OSgroup=APPLE | stats count(eval(severity="4" or severity="5")) AS total_severity, dc(Hostname) AS total_devices | eval defects=(total_severity/total_devices)&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;The above string provides me the data for the time selected (which is generally the past 7 days).&lt;/P&gt;

&lt;P&gt;What I would like to do it provide the defects for the current week, prior week, prior prior week, etc.&lt;/P&gt;

&lt;P&gt;Thoughts?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 11:35:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104552#M27101</guid>
      <dc:creator>jgolovich</dc:creator>
      <dc:date>2020-09-28T11:35:51Z</dc:date>
    </item>
    <item>
      <title>Re: Trending a calculation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104553#M27102</link>
      <description>&lt;P&gt;&lt;CODE&gt;timechart&lt;/CODE&gt; is your friend.  You may want to rewrite your search some however.  Something like this may get close:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype="qualys" OSgroup=APPLE ( severity=4 OR severity=5 )
| timechart span=1w count(severity),dc(Hostname) AS total_devices 
| eval defects=(total_severity/total_devices)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 29 Mar 2012 16:30:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104553#M27102</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-03-29T16:30:14Z</dc:date>
    </item>
    <item>
      <title>Re: Trending a calculation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104554#M27103</link>
      <description>&lt;P&gt;Try&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sourcetype="qualys" OSgroup=APPLE | 
bucket _time span=7d |
stats count(eval(severity="4" or severity="5")) AS total_severity, dc(Hostname) AS total_devices by _time | 
eval defects=(total_severity/total_devices)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and search over the past 28 days or whatever. This will bucket in 7-day periods, not Sun-Sat. &lt;/P&gt;</description>
      <pubDate>Thu, 29 Mar 2012 16:32:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104554#M27103</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2012-03-29T16:32:31Z</dc:date>
    </item>
    <item>
      <title>Re: Trending a calculation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104555#M27104</link>
      <description>&lt;P&gt;I also like dwaddle's answer, although I don't think that is the search that you want.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Mar 2012 16:33:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104555#M27104</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2012-03-29T16:33:18Z</dc:date>
    </item>
    <item>
      <title>Re: Trending a calculation</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104556#M27105</link>
      <description>&lt;P&gt;A summary index will solve this problem.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.1/Knowledge/Usesummaryindexing"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.1/Knowledge/Usesummaryindexing&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Lp&lt;/P&gt;</description>
      <pubDate>Thu, 29 Mar 2012 17:36:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Trending-a-calculation/m-p/104556#M27105</guid>
      <dc:creator>lpolo</dc:creator>
      <dc:date>2012-03-29T17:36:00Z</dc:date>
    </item>
  </channel>
</rss>

