<?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: How to predict event increase/license usage by sourcetype in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-predict-event-increase-license-usage-by-sourcetype/m-p/452488#M78403</link>
    <description>&lt;P&gt;@adam_dixon95 - The math is easy , the historical data is very difficult,&lt;BR /&gt;
Youcan use MLTK or the inbuilt time series forecasting using the predict command&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.1/SearchReference/Predict"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.1/SearchReference/Predict&lt;/A&gt;&lt;BR /&gt;
BUT&lt;BR /&gt;
you need a big chunk of historical data, based on the time range you are looking to predict for.&lt;BR /&gt;
For example if you are looking at every hour , you would probably need an hourly historical data set for the last 1 year at a bare minimum to make a good prediction.&lt;BR /&gt;
If you are looking at every 5 minutes, maybe you need a 5 minutes based data set for the last 3 months.&lt;BR /&gt;
Thumb rule - more data is not necessarily better, but coverage is. If your data is cyclical (typically all businesses have some cycles - eg more sales in new year/Christmas) and you do not include the historical data for that while making a prediction, chances are that your model will fail for 2019 Christmas&lt;/P&gt;</description>
    <pubDate>Fri, 16 Aug 2019 15:53:32 GMT</pubDate>
    <dc:creator>Sukisen1981</dc:creator>
    <dc:date>2019-08-16T15:53:32Z</dc:date>
    <item>
      <title>How to predict event increase/license usage by sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-predict-event-increase-license-usage-by-sourcetype/m-p/452487#M78402</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm currently ingesting Sysmon logs from 100 hosts, event are currently stable. Though I'm looking to be sending 10x more Sysmon hosts to Splunk. &lt;/P&gt;

&lt;P&gt;These are quite busy log sources and so I'd like to find a way, within Splunk to estimate the license usage per the Sysmon SourceType and potentially provide a graph to show predicted growth/usage in license usage AND/OR event count.&lt;/P&gt;

&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2019 15:40:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-predict-event-increase-license-usage-by-sourcetype/m-p/452487#M78402</guid>
      <dc:creator>adam_dixon95</dc:creator>
      <dc:date>2019-08-16T15:40:59Z</dc:date>
    </item>
    <item>
      <title>Re: How to predict event increase/license usage by sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-predict-event-increase-license-usage-by-sourcetype/m-p/452488#M78403</link>
      <description>&lt;P&gt;@adam_dixon95 - The math is easy , the historical data is very difficult,&lt;BR /&gt;
Youcan use MLTK or the inbuilt time series forecasting using the predict command&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.1/SearchReference/Predict"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.1/SearchReference/Predict&lt;/A&gt;&lt;BR /&gt;
BUT&lt;BR /&gt;
you need a big chunk of historical data, based on the time range you are looking to predict for.&lt;BR /&gt;
For example if you are looking at every hour , you would probably need an hourly historical data set for the last 1 year at a bare minimum to make a good prediction.&lt;BR /&gt;
If you are looking at every 5 minutes, maybe you need a 5 minutes based data set for the last 3 months.&lt;BR /&gt;
Thumb rule - more data is not necessarily better, but coverage is. If your data is cyclical (typically all businesses have some cycles - eg more sales in new year/Christmas) and you do not include the historical data for that while making a prediction, chances are that your model will fail for 2019 Christmas&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2019 15:53:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-predict-event-increase-license-usage-by-sourcetype/m-p/452488#M78403</guid>
      <dc:creator>Sukisen1981</dc:creator>
      <dc:date>2019-08-16T15:53:32Z</dc:date>
    </item>
    <item>
      <title>Re: How to predict event increase/license usage by sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-predict-event-increase-license-usage-by-sourcetype/m-p/452489#M78404</link>
      <description>&lt;PRE&gt;&lt;CODE&gt; index=_internal source="*license_usage.log*" type=Usage  | eval yearmonthday=strftime(_time, "%Y%m%d") | stats sum(eval(b/1024/1024)) AS volume_mb by idx st yearmonthday
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 19 Aug 2019 02:03:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-predict-event-increase-license-usage-by-sourcetype/m-p/452489#M78404</guid>
      <dc:creator>nareshinsvu</dc:creator>
      <dc:date>2019-08-19T02:03:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to predict event increase/license usage by sourcetype</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-predict-event-increase-license-usage-by-sourcetype/m-p/452490#M78405</link>
      <description>&lt;P&gt;hi @adam_dixon95 &lt;BR /&gt;
Were you able to make some progress on this question?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2019 14:58:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-predict-event-increase-license-usage-by-sourcetype/m-p/452490#M78405</guid>
      <dc:creator>Sukisen1981</dc:creator>
      <dc:date>2019-08-19T14:58:25Z</dc:date>
    </item>
  </channel>
</rss>

