<?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: Report scheduling/acceleration question... in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310932#M5713</link>
    <description>&lt;P&gt;You could enable report acceleration for your report to avoid re-running over old days again and again.&lt;BR /&gt;
You could use the existing license usage data model or a custom one, accelerate that, and build your 30-day reports off that accelerated data model.&lt;BR /&gt;
You could run a summary search every day to build the report for yesterday, and run your 30-day reports off that summary index.&lt;/P&gt;</description>
    <pubDate>Sun, 19 Feb 2017 19:25:40 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2017-02-19T19:25:40Z</dc:date>
    <item>
      <title>Report scheduling/acceleration question...</title>
      <link>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310931#M5712</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I need to generate a number of reports about license utilization for different customers, over the past 30 days.  Do  I need to re-run the past 30 days search every day, or is there a way to run it for one day, and have a history that keeps building?  Running it every day for 30 days seems like a waste of resources...&lt;/P&gt;</description>
      <pubDate>Sun, 19 Feb 2017 14:44:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310931#M5712</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2017-02-19T14:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: Report scheduling/acceleration question...</title>
      <link>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310932#M5713</link>
      <description>&lt;P&gt;You could enable report acceleration for your report to avoid re-running over old days again and again.&lt;BR /&gt;
You could use the existing license usage data model or a custom one, accelerate that, and build your 30-day reports off that accelerated data model.&lt;BR /&gt;
You could run a summary search every day to build the report for yesterday, and run your 30-day reports off that summary index.&lt;/P&gt;</description>
      <pubDate>Sun, 19 Feb 2017 19:25:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310932#M5713</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2017-02-19T19:25:40Z</dc:date>
    </item>
    <item>
      <title>Re: Report scheduling/acceleration question...</title>
      <link>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310933#M5714</link>
      <description>&lt;P&gt;For the first one, how does that work in practice?  I want to report on 30 days, but not have my search query the past 30 days every time.  &lt;/P&gt;</description>
      <pubDate>Sun, 19 Feb 2017 22:22:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310933#M5714</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2017-02-19T22:22:24Z</dc:date>
    </item>
    <item>
      <title>Re: Report scheduling/acceleration question...</title>
      <link>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310934#M5715</link>
      <description>&lt;P&gt;The first one is the easiest to build - save the report with a time range of 30 days, check the "accelerate" box, select 30 days, save, done. Splunk does the rest underneath.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.5.2/Report/Acceleratereports"&gt;http://docs.splunk.com/Documentation/Splunk/6.5.2/Report/Acceleratereports&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 19 Feb 2017 22:32:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310934#M5715</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2017-02-19T22:32:15Z</dc:date>
    </item>
    <item>
      <title>Re: Report scheduling/acceleration question...</title>
      <link>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310935#M5716</link>
      <description>&lt;P&gt;Do you need to schedule report as well?&lt;/P&gt;</description>
      <pubDate>Mon, 25 Sep 2017 17:50:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310935#M5716</guid>
      <dc:creator>kiril123</dc:creator>
      <dc:date>2017-09-25T17:50:33Z</dc:date>
    </item>
    <item>
      <title>Re: Report scheduling/acceleration question...</title>
      <link>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310936#M5717</link>
      <description>&lt;P&gt;No, its like a rolling 30 day window.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Feb 2018 16:40:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Report-scheduling-acceleration-question/m-p/310936#M5717</guid>
      <dc:creator>leonphelps_s</dc:creator>
      <dc:date>2018-02-26T16:40:54Z</dc:date>
    </item>
  </channel>
</rss>

