<?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 Graphing scheduled saved search results in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Graphing-scheduled-saved-search-results/m-p/77080#M1761</link>
    <description>&lt;P&gt;Hello fellow splunkers,&lt;/P&gt;

&lt;P&gt;I have a large dataset that I am searching through, and I want to create a historical timechart which goes back for several months. Because of the size of the dataset, having a search which goes that far back is impracticable (or at least impractical). &lt;/P&gt;

&lt;P&gt;My solution was to schedule a daily search which would save the results from the last 24 hours. After 3 months, for example, I would have 90 saved results which each only contain a simple count of the number of events, and my chart could therefore simply graph the counts from each saved result, with each one being a datapoint. I'd just set the TTL for the saved results to be 90 days.&lt;/P&gt;

&lt;P&gt;I'm fairly new to Splunk, but this seems like it would be a pretty basic feature, so I feel like I'm missing something. The closest I've gotten is using something like &lt;EM&gt;| append loadjob savedsearch=foo&lt;/EM&gt;, but that will only add a single saved result, unless &lt;EM&gt;foo&lt;/EM&gt; is somehow a "living" result which always has the results from the past 90 days.&lt;/P&gt;

&lt;P&gt;I've heard of summary indexes for dealing with large datasets, and I'll research them to see if it's what I need, but I was hoping for a relatively simple solution which could be carried out within the Splunk web interface.&lt;/P&gt;

&lt;P&gt;Thanks in advance, and sorry if this has been answered before.&lt;/P&gt;</description>
    <pubDate>Fri, 15 Jun 2012 20:19:07 GMT</pubDate>
    <dc:creator>rereeser</dc:creator>
    <dc:date>2012-06-15T20:19:07Z</dc:date>
    <item>
      <title>Graphing scheduled saved search results</title>
      <link>https://community.splunk.com/t5/Reporting/Graphing-scheduled-saved-search-results/m-p/77080#M1761</link>
      <description>&lt;P&gt;Hello fellow splunkers,&lt;/P&gt;

&lt;P&gt;I have a large dataset that I am searching through, and I want to create a historical timechart which goes back for several months. Because of the size of the dataset, having a search which goes that far back is impracticable (or at least impractical). &lt;/P&gt;

&lt;P&gt;My solution was to schedule a daily search which would save the results from the last 24 hours. After 3 months, for example, I would have 90 saved results which each only contain a simple count of the number of events, and my chart could therefore simply graph the counts from each saved result, with each one being a datapoint. I'd just set the TTL for the saved results to be 90 days.&lt;/P&gt;

&lt;P&gt;I'm fairly new to Splunk, but this seems like it would be a pretty basic feature, so I feel like I'm missing something. The closest I've gotten is using something like &lt;EM&gt;| append loadjob savedsearch=foo&lt;/EM&gt;, but that will only add a single saved result, unless &lt;EM&gt;foo&lt;/EM&gt; is somehow a "living" result which always has the results from the past 90 days.&lt;/P&gt;

&lt;P&gt;I've heard of summary indexes for dealing with large datasets, and I'll research them to see if it's what I need, but I was hoping for a relatively simple solution which could be carried out within the Splunk web interface.&lt;/P&gt;

&lt;P&gt;Thanks in advance, and sorry if this has been answered before.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jun 2012 20:19:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Graphing-scheduled-saved-search-results/m-p/77080#M1761</guid>
      <dc:creator>rereeser</dc:creator>
      <dc:date>2012-06-15T20:19:07Z</dc:date>
    </item>
    <item>
      <title>Re: Graphing scheduled saved search results</title>
      <link>https://community.splunk.com/t5/Reporting/Graphing-scheduled-saved-search-results/m-p/77081#M1762</link>
      <description>&lt;P&gt;What you're trying to do is essentially summary indexing. Basically, you take your daily scheduled search and instead of sending the output to display, you send it to a separate index.  Then in three months, you run your output search against the summary index so it only has to deal with 90 datapoints.  &lt;/P&gt;

&lt;P&gt;This is all configurable in the UI. &lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Knowledge/Usesummaryindexing"&gt;Details are here&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jun 2012 20:56:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Graphing-scheduled-saved-search-results/m-p/77081#M1762</guid>
      <dc:creator>emiller42</dc:creator>
      <dc:date>2012-06-15T20:56:02Z</dc:date>
    </item>
    <item>
      <title>Re: Graphing scheduled saved search results</title>
      <link>https://community.splunk.com/t5/Reporting/Graphing-scheduled-saved-search-results/m-p/77082#M1763</link>
      <description>&lt;P&gt;Great, thanks. I guess I initially misunderstood how summary indexing worked.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jun 2012 16:22:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Graphing-scheduled-saved-search-results/m-p/77082#M1763</guid>
      <dc:creator>rereeser</dc:creator>
      <dc:date>2012-06-18T16:22:40Z</dc:date>
    </item>
  </channel>
</rss>

