<?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 How to get volume by indexer? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-get-volume-by-indexer/m-p/412091#M72942</link>
    <description>&lt;P&gt;all, &lt;/P&gt;

&lt;P&gt;Is there a better way to get data by indexer than this search from the search head without access to the internal indexes/&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=* 
| fields _raw, volume, splunk_server
| eval volume=len(_raw) 
| stats sum(volume) by splunk_server
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Sat, 18 Aug 2018 00:14:29 GMT</pubDate>
    <dc:creator>daniel333</dc:creator>
    <dc:date>2018-08-18T00:14:29Z</dc:date>
    <item>
      <title>How to get volume by indexer?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-get-volume-by-indexer/m-p/412091#M72942</link>
      <description>&lt;P&gt;all, &lt;/P&gt;

&lt;P&gt;Is there a better way to get data by indexer than this search from the search head without access to the internal indexes/&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=* 
| fields _raw, volume, splunk_server
| eval volume=len(_raw) 
| stats sum(volume) by splunk_server
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 18 Aug 2018 00:14:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-get-volume-by-indexer/m-p/412091#M72942</guid>
      <dc:creator>daniel333</dc:creator>
      <dc:date>2018-08-18T00:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: How to get volume by indexer?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-get-volume-by-indexer/m-p/412092#M72943</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/19813"&gt;@daniel333&lt;/a&gt; &lt;/P&gt;

&lt;P&gt;unfortunately I don't think it is possible to get a exact understanding how much data is on your actual indexers if you don't have access to the _internal index.&lt;/P&gt;

&lt;P&gt;However... I tried to come up with a rough estimate on how it could be done with your solution.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=* 
| fields _raw, volume, splunk_server
| eval volume=len(_raw) 
| stats sum(volume) AS volume by splunk_server 
| eval total_size_in_GB=round((volume*8/(1024*1024*1024)),4), total_size_on_disk_in_GB=round(total_size_in_GB*0.5,4)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I added a &lt;STRONG&gt;total_size_in_GB&lt;/STRONG&gt; field by multiplying the "volume" by 8 (Bit). For a lot of the standard characters you will need 8 Bit or 1 Byte to store it in memory. (If you have a lot of Chinese sign language in there this is a whole other story.)&lt;/P&gt;

&lt;P&gt;Then I basically divide it by 1024^3 which gives me the size in GB.&lt;/P&gt;

&lt;P&gt;I also added the &lt;STRONG&gt;total_size_on_disk_in_GB&lt;/STRONG&gt; field that multiplies the &lt;STRONG&gt;total_size_in_GB&lt;/STRONG&gt; field by 0.5&lt;BR /&gt;
&lt;EM&gt;Why 0.5 you might ask?&lt;/EM&gt;&lt;BR /&gt;
There is a sizing calculator out there which uses a default value of (Raw Compression Factor (0.15) + Metadata Size Factor (0.35)) = 0.15 + 0.35 = 0.5&lt;/P&gt;

&lt;P&gt;&lt;A href="https://splunk-sizing.appspot.com/" target="_blank"&gt;https://splunk-sizing.appspot.com/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;So the actual size of the data on your disk is the originally calculated size multiplied by 0.5.&lt;/P&gt;

&lt;P&gt;Another approach is you can do a &lt;BR /&gt;
&lt;CODE&gt;| tstats count WHERE index=*&lt;/CODE&gt; (last 24 hours)&lt;BR /&gt;
counting the amount of events on your system. &lt;/P&gt;

&lt;P&gt;The Splunk Sizing Calculator has an option to get you a estimate on the amount of storage you need for your indexers to store all your data. There is also an option to input a "count of events per second".&lt;/P&gt;

&lt;P&gt;&lt;A href="https://splunk-sizing.appspot.com/#st=eps" target="_blank"&gt;https://splunk-sizing.appspot.com/#st=eps&lt;/A&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| tstats count WHERE index=* | eval events_per_second=count/(3600*24)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You are then able to input the &lt;STRONG&gt;events_per_second&lt;/STRONG&gt; value into the sizing calculator and calculate the size of your data that goes in and out per day. &lt;/P&gt;

&lt;P&gt;With that information you are easily able to calculate the total size of your data. (Still... this is only a rough estimate, keep that in mind)&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 20:56:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-get-volume-by-indexer/m-p/412092#M72943</guid>
      <dc:creator>horsefez</dc:creator>
      <dc:date>2020-09-29T20:56:17Z</dc:date>
    </item>
  </channel>
</rss>

