<?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: Sudden spike in indexed data. How to narrow down in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45795#M8616</link>
    <description>&lt;P&gt;If you changed "group=per_host_thruput" to "group=per_source_thruput" you may be able to discern that from the indexer if the volume is high enough -- but it will be showing all sources. It may be easier to go to the forwarder in question and run this search from the CLI:   index=&lt;EM&gt;internal metrics kb series!=&lt;/EM&gt;* "group=per_source_thruput" earliest=-7d | eval mb = kb / 1024 | stats sum(mb) by series | sort -sum(mb)&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 09:17:28 GMT</pubDate>
    <dc:creator>bwooden</dc:creator>
    <dc:date>2020-09-28T09:17:28Z</dc:date>
    <item>
      <title>Sudden spike in indexed data. How to narrow down</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45790#M8611</link>
      <description>&lt;P&gt;The amount of data I index daily is pretty consistent for the most part. I suppose it's gradually increasing, but no big deal.&lt;/P&gt;

&lt;P&gt;But once in a while there is a day where there is a 100% increase in the amount of data indexed. &lt;/P&gt;

&lt;P&gt;I suspect it's one log/one forwarder that's doing it. And I have a hunch as to what log it is, but I can't demonstrate that in Splunk.&lt;/P&gt;

&lt;P&gt;This is supposed to be easy with Splunk, but I can't figure this out. What is the best way to track which forwarder is the source of the spike? How can I narrow down the log that is causing this? &lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2010 19:21:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45790#M8611</guid>
      <dc:creator>Branden</dc:creator>
      <dc:date>2010-09-08T19:21:04Z</dc:date>
    </item>
    <item>
      <title>Re: Sudden spike in indexed data. How to narrow down</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45791#M8612</link>
      <description>&lt;P&gt;You can take a look at one of the pre-built reports.  You can access it by going to the Search App, then selecting "Status" * "Index Activity" * "Index Volume". &lt;/P&gt;

&lt;P&gt;Then using the dropdowns, you can select "Source" for the the time frame.&lt;/P&gt;

&lt;P&gt;Hope this helps,
Brian&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2010 21:22:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45791#M8612</guid>
      <dc:creator>Brian_Osburn</dc:creator>
      <dc:date>2010-09-08T21:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: Sudden spike in indexed data. How to narrow down</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45792#M8613</link>
      <description>&lt;P&gt;One way to identify this is to look at the metrics collected by Splunk.  From the search app, you can click on menu option "Views" and select "Advanced Charting".&lt;/P&gt;

&lt;P&gt;In the &lt;EM&gt;Formatting options&lt;/EM&gt; choose &lt;EM&gt;Chart Type=line&lt;/EM&gt; and &lt;EM&gt;Multi-series mode=Combined&lt;/EM&gt; using the appropriate drop down boxes.  Finally, search for&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal metrics kb series!=_* "group=per_host_thruput" earliest=-7d | eval mb = kb / 1024 | timechart fixedrange=t span=1d sum(mb) by series
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 08 Sep 2010 21:24:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45792#M8613</guid>
      <dc:creator>bwooden</dc:creator>
      <dc:date>2010-09-08T21:24:04Z</dc:date>
    </item>
    <item>
      <title>Re: Sudden spike in indexed data. How to narrow down</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45793#M8614</link>
      <description>&lt;P&gt;Thank you for the response. I was able to narrow down the host that it's coming from (wasn't the host I was expecting!) but I can't tell WHAT on the host is causing it. I am wondering if one of the log files has spun out of control or something. Is there a way to get that information?&lt;BR /&gt;
Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2010 22:51:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45793#M8614</guid>
      <dc:creator>Branden</dc:creator>
      <dc:date>2010-09-08T22:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: Sudden spike in indexed data. How to narrow down</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45794#M8615</link>
      <description>&lt;P&gt;Thank you for the response. That procedure tells me how much as indexed in GB, but it doesn't give me much more granularity than that. I'll play with it though and see what I can come up with. Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 08 Sep 2010 22:52:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45794#M8615</guid>
      <dc:creator>Branden</dc:creator>
      <dc:date>2010-09-08T22:52:27Z</dc:date>
    </item>
    <item>
      <title>Re: Sudden spike in indexed data. How to narrow down</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45795#M8616</link>
      <description>&lt;P&gt;If you changed "group=per_host_thruput" to "group=per_source_thruput" you may be able to discern that from the indexer if the volume is high enough -- but it will be showing all sources. It may be easier to go to the forwarder in question and run this search from the CLI:   index=&lt;EM&gt;internal metrics kb series!=&lt;/EM&gt;* "group=per_source_thruput" earliest=-7d | eval mb = kb / 1024 | stats sum(mb) by series | sort -sum(mb)&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:17:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Sudden-spike-in-indexed-data-How-to-narrow-down/m-p/45795#M8616</guid>
      <dc:creator>bwooden</dc:creator>
      <dc:date>2020-09-28T09:17:28Z</dc:date>
    </item>
  </channel>
</rss>

