<?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 check traffic volume per heavy forawrder in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/345342#M63462</link>
    <description>&lt;P&gt;If you are looking for total volume sent (including _internal) and not just license usage here is a good search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal sourcetype=splunkd group=tcpin_connections (connectionType=cooked OR connectionType=cookedSSL) fwdType=* guid=* 
| eval dest_uri = host.":".destPort 
| stats values(fwdType) as forwarder_type, latest(version) as version, values(arch) as arch, dc(dest_uri) as dest_count, values(os) as os, max(_time) as last_connected, sum(kb) as new_sum_kb, sparkline(avg(tcp_KBps), 1m) as avg_tcp_kbps_sparkline, avg(tcp_KBps) as avg_tcp_kbps, avg(tcp_eps) as avg_tcp_eps by guid, hostname 
| eval hostname = upper(hostname)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This provides quite a bit of extra info. You can convert kb to GB as needed.&lt;/P&gt;</description>
    <pubDate>Mon, 09 Oct 2017 19:48:00 GMT</pubDate>
    <dc:creator>mdsnmss</dc:creator>
    <dc:date>2017-10-09T19:48:00Z</dc:date>
    <item>
      <title>How to check traffic volume per heavy forwarder?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/345339#M63459</link>
      <description>&lt;P&gt;I plan to calculate the traffic volume in GB across all our HFs. Need this to ensure check which HF is getting max traffic as this is affecting. I was able to get memory, cpu and bandwidth utilization from index= _interospection and index=_internal&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jul 2022 16:04:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/345339#M63459</guid>
      <dc:creator>hkumar26</dc:creator>
      <dc:date>2022-07-05T16:04:17Z</dc:date>
    </item>
    <item>
      <title>Re: how to check traffic volume per heavy forawrder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/345340#M63460</link>
      <description>&lt;P&gt;do you mean license usage? e.g. raw data received by indexers through Heavy Forwarders?&lt;/P&gt;</description>
      <pubDate>Fri, 04 Aug 2017 09:50:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/345340#M63460</guid>
      <dc:creator>adonio</dc:creator>
      <dc:date>2017-08-04T09:50:03Z</dc:date>
    </item>
    <item>
      <title>Re: how to check traffic volume per heavy forawrder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/345341#M63461</link>
      <description>&lt;P&gt;Hi hkumar26,&lt;BR /&gt;
see Splunk Distributed Monitoring Console App and you can find your searches.&lt;BR /&gt;
Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 04 Aug 2017 11:03:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/345341#M63461</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2017-08-04T11:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: how to check traffic volume per heavy forawrder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/345342#M63462</link>
      <description>&lt;P&gt;If you are looking for total volume sent (including _internal) and not just license usage here is a good search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal sourcetype=splunkd group=tcpin_connections (connectionType=cooked OR connectionType=cookedSSL) fwdType=* guid=* 
| eval dest_uri = host.":".destPort 
| stats values(fwdType) as forwarder_type, latest(version) as version, values(arch) as arch, dc(dest_uri) as dest_count, values(os) as os, max(_time) as last_connected, sum(kb) as new_sum_kb, sparkline(avg(tcp_KBps), 1m) as avg_tcp_kbps_sparkline, avg(tcp_KBps) as avg_tcp_kbps, avg(tcp_eps) as avg_tcp_eps by guid, hostname 
| eval hostname = upper(hostname)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This provides quite a bit of extra info. You can convert kb to GB as needed.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Oct 2017 19:48:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/345342#M63462</guid>
      <dc:creator>mdsnmss</dc:creator>
      <dc:date>2017-10-09T19:48:00Z</dc:date>
    </item>
    <item>
      <title>Re: how to check traffic volume per heavy forawrder</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/604428#M105108</link>
      <description>&lt;LI-CODE lang="markup"&gt;index=_internal host IN ("yourheavyforwarders") group=per_index_thruput | stats sum(kb) as kb by host
| eval GB=round(kb/1024/1024,2) | fields - kb&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Note: if you want to exclude internal indexes which are starting with _(underscore), you can use below search&lt;/STRONG&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=_internal host IN ("yourheavyforwarders") group=per_index_thruput series!=_* | stats sum(kb) as kb by host
| eval GB=round(kb/1024/1024,2) | fields - kb&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jul 2022 11:20:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-check-traffic-volume-per-heavy-forwarder/m-p/604428#M105108</guid>
      <dc:creator>thambisetty</dc:creator>
      <dc:date>2022-07-05T11:20:20Z</dc:date>
    </item>
  </channel>
</rss>

