<?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 License Usage - Month over Month in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369917#M5233</link>
    <description>&lt;P&gt;Get the search from the &lt;CODE&gt;Monitoring Console&lt;/CODE&gt;:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/6.6.1/DMC/DMCoverview"&gt;https://docs.splunk.com/Documentation/Splunk/6.6.1/DMC/DMCoverview&lt;/A&gt;&lt;BR /&gt;
Then use the &lt;CODE&gt;timewrap&lt;/CODE&gt; command:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/6.6.0/SearchReference/Timewrap"&gt;https://docs.splunk.com/Documentation/SplunkCloud/6.6.0/SearchReference/Timewrap&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 23 Jun 2017 13:17:22 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2017-06-23T13:17:22Z</dc:date>
    <item>
      <title>Splunk License Usage - Month over Month</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369916#M5232</link>
      <description>&lt;P&gt;We upgraded to 6.5.2 recently and was under the impression that 6.5 keeps license usage history over 30 days (unlike the older 6.2, etc..)&lt;/P&gt;

&lt;P&gt;When I check out LURV or try to run a few searches, I can still only see 30 days worth of license usage data.&lt;/P&gt;

&lt;P&gt;Has anyone been able to identify a way to generate a report of license usage over, say, the past 6 months to try to determine growth projections and whether additional license will need to be purchased over X months etc.. ?&lt;/P&gt;

&lt;P&gt;Any help is appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jun 2017 13:02:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369916#M5232</guid>
      <dc:creator>moesaidi</dc:creator>
      <dc:date>2017-06-23T13:02:45Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk License Usage - Month over Month</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369917#M5233</link>
      <description>&lt;P&gt;Get the search from the &lt;CODE&gt;Monitoring Console&lt;/CODE&gt;:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/6.6.1/DMC/DMCoverview"&gt;https://docs.splunk.com/Documentation/Splunk/6.6.1/DMC/DMCoverview&lt;/A&gt;&lt;BR /&gt;
Then use the &lt;CODE&gt;timewrap&lt;/CODE&gt; command:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/SplunkCloud/6.6.0/SearchReference/Timewrap"&gt;https://docs.splunk.com/Documentation/SplunkCloud/6.6.0/SearchReference/Timewrap&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jun 2017 13:17:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369917#M5233</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-06-23T13:17:22Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk License Usage - Month over Month</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369918#M5234</link>
      <description>&lt;P&gt;In addition to this, you can adjust the retention time of the _internal index. This is where the metrics and license usage data is stored. Extend that to 6 /9 / 12 months etc. &lt;BR /&gt;
Just be aware of the implications this would have on disk space on your indexers. &lt;/P&gt;</description>
      <pubDate>Fri, 23 Jun 2017 13:23:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369918#M5234</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2017-06-23T13:23:00Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk License Usage - Month over Month</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369919#M5235</link>
      <description>&lt;P&gt;I've tried this before and now again, even after adjusting the 'earliest' value or using timewrap it only shows me the last 30 days. &lt;BR /&gt;
It seems to use the _internal index which is only retained for 30 days, but I thought 6.5.x and higher was using _telemetry index for licensing which is stored for 6 months. &lt;/P&gt;

&lt;P&gt;Any other ideas? &lt;/P&gt;</description>
      <pubDate>Fri, 23 Jun 2017 13:41:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369919#M5235</guid>
      <dc:creator>moesaidi</dc:creator>
      <dc:date>2017-06-23T13:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk License Usage - Month over Month</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369920#M5236</link>
      <description>&lt;P&gt;I wish I could set _index to over 30 days though like you said, that would use up a lot of disk space.&lt;BR /&gt;
I was under the impression _telemetry would save licensing data and that by default is kept for 6 months.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jun 2017 13:42:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369920#M5236</guid>
      <dc:creator>moesaidi</dc:creator>
      <dc:date>2017-06-23T13:42:01Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk License Usage - Month over Month</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369921#M5237</link>
      <description>&lt;P&gt;If the problem is that events are expiring out of &lt;CODE&gt;_internal&lt;/CODE&gt; or &lt;CODE&gt;_telemetry&lt;/CODE&gt; while you still need them and you cannot extend the retention, you can create a summary index (which will be TINY) and schedule a saved search to run nightly that dumps a daily summary and you can search from that.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jun 2017 13:55:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-License-Usage-Month-over-Month/m-p/369921#M5237</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-06-23T13:55:31Z</dc:date>
    </item>
  </channel>
</rss>

