<?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: Splunk predict command period vs future_timespan? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320415#M95755</link>
    <description>&lt;P&gt;@kdimaria, period and future_timespan arguments are different for sure.&lt;/P&gt;

&lt;P&gt;In order to improve prediction you can add &lt;CODE&gt;period&lt;/CODE&gt; argument with data points after which your data pattern repeats. For example if you have a timechart with span=1d (1 day) and your weekly trends are similar i.e. Every Moday your events rise and every Thursday is your Peak, your events start declining from Friday and Sunday is no/minimal traffic. Then you would define &lt;CODE&gt;7&lt;/CODE&gt; as your period.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| timechart span=1d count as Traffic
| predict algorithm=LLP period=7
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The &lt;CODE&gt;future_timespan&lt;/CODE&gt; argument tells predict command how many future buckets to predict based on your time span selected. i.e. if you have set it to 5, and timechart span=1d it will predict upcoming 5 days.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| timechart span=1d count as Traffic
| predict algorithm=LLP period=7 future_timespan=5
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Please let us know if this is what you required or something else?&lt;/P&gt;</description>
    <pubDate>Thu, 07 Sep 2017 12:03:35 GMT</pubDate>
    <dc:creator>niketn</dc:creator>
    <dc:date>2017-09-07T12:03:35Z</dc:date>
    <item>
      <title>Splunk predict command period vs future_timespan?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320414#M95754</link>
      <description>&lt;P&gt;I am wondering if anyone has an explanation of exactly what period is and what future_timespan is? I already read the document &lt;A href="http://docs.splunk.com/Documentation/SplunkCloud/6.6.0/SearchReference/Predict"&gt;http://docs.splunk.com/Documentation/SplunkCloud/6.6.0/SearchReference/Predict&lt;/A&gt; which talks about both of the parameters but I am still really confused on what exactly they do and would like for someone to explain them to me in their own words. Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 11:47:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320414#M95754</guid>
      <dc:creator>kdimaria</dc:creator>
      <dc:date>2017-09-07T11:47:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk predict command period vs future_timespan?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320415#M95755</link>
      <description>&lt;P&gt;@kdimaria, period and future_timespan arguments are different for sure.&lt;/P&gt;

&lt;P&gt;In order to improve prediction you can add &lt;CODE&gt;period&lt;/CODE&gt; argument with data points after which your data pattern repeats. For example if you have a timechart with span=1d (1 day) and your weekly trends are similar i.e. Every Moday your events rise and every Thursday is your Peak, your events start declining from Friday and Sunday is no/minimal traffic. Then you would define &lt;CODE&gt;7&lt;/CODE&gt; as your period.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| timechart span=1d count as Traffic
| predict algorithm=LLP period=7
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The &lt;CODE&gt;future_timespan&lt;/CODE&gt; argument tells predict command how many future buckets to predict based on your time span selected. i.e. if you have set it to 5, and timechart span=1d it will predict upcoming 5 days.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| timechart span=1d count as Traffic
| predict algorithm=LLP period=7 future_timespan=5
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Please let us know if this is what you required or something else?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 12:03:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320415#M95755</guid>
      <dc:creator>niketn</dc:creator>
      <dc:date>2017-09-07T12:03:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk predict command period vs future_timespan?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320416#M95756</link>
      <description>&lt;P&gt;Period is the data that is crunched in order to determine the prediction.&lt;/P&gt;

&lt;P&gt;Lets say i have a single event every day at 1pm with a field that contains a number. The value of that field has decreased by 1 every day for the last 7 days.  If i specify a period of 7, the algorithm would see that over the last 7 days, the number has decreased by 1 every day... and therefore is likely to continue decreasing by 1 with very little margin for error in the prediction...&lt;/P&gt;

&lt;P&gt;If however the event was up by 10 every day for days 1-3, and down by one every day from days 4-10, and I specify a period of 10... then the algorithm is going to give a wider margin of predictions.&lt;/P&gt;

&lt;P&gt;future_timespan is how far into the future to predict results.  If you specify a future_timespan of 50 with the previous example, since the data comes in once per day, the predict command would produce 50 days of future predicted data points.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:40:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320416#M95756</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2020-09-29T15:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk predict command period vs future_timespan?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320417#M95757</link>
      <description>&lt;P&gt;Thank you I think I finally get it now&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 12:11:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320417#M95757</guid>
      <dc:creator>kdimaria</dc:creator>
      <dc:date>2017-09-07T12:11:51Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk predict command period vs future_timespan?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320418#M95758</link>
      <description>&lt;P&gt;Thank you! I think I understand now. the period was just very confusing.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2017 12:12:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-predict-command-period-vs-future-timespan/m-p/320418#M95758</guid>
      <dc:creator>kdimaria</dc:creator>
      <dc:date>2017-09-07T12:12:31Z</dc:date>
    </item>
  </channel>
</rss>

