topic Re: How can we find the Heavy Forwarders data flow? in Getting Data In

How can we find the Heavy Forwarders data flow?

ddrillic — Wed, 11 Jul 2018 17:18:03 GMT

We have two Heavy Forwarders through which quite a bit of data is flowing through. We have access to the back end, such as to the metrics logs but not to the UI. How can we find out the daily amount of data which goes through these heavy forwarders?

Re: How can we find the Heavy Forwarders data flow?

somesoni2 — Wed, 11 Jul 2018 17:56:35 GMT

YOu can run CLI searches to those metrics logs to get the data you want (provided you've Splunk credentials with permission to view _internal index).
https://docs.splunk.com/Documentation/Splunk/7.1.1/Troubleshooting/Aboutmetricslog

Re: How can we find the Heavy Forwarders data flow?

ddrillic — Wed, 11 Jul 2018 18:17:47 GMT

Most cheerful @somesoni2 - thank you.

Re: How can we find the Heavy Forwarders data flow?

yannK — Thu, 12 Jul 2018 00:09:02 GMT

You can look in the metrics.log of the HWF how much they received.
And you can look on the next level indexer how much they received form the forwarders (and group them per type)

example for the volume received by the indexers per forwarder type. (full = heavy forwarder)

        index=_internal  host=*myindexer*  source=*metrics.log* group=tcpin_connections fwdType| stats sum(kb) by hostname fwdType

Re: How can we find the Heavy Forwarders data flow?

woodcock — Thu, 12 Jul 2018 03:24:28 GMT

Assuming that you named your HF tier differently than your Indexer tier, you can use a search like this:

index=_internal AND component=Metrics tcpout* | stats values(name) dc(name) AS options BY host | sort 0 options

Re: How can we find the Heavy Forwarders data flow?

Zane — Wed, 01 Mar 2023 09:08:37 GMT

Hi there，

i'm a new splunker

I'd like to know what's means of these search result, such as "management", "default-autolb-group:xxx.xxx.xxx.xxx:9997:3:1" i can understand there is my HF ip and port, but what's means of :3:1, I have seen :0:0, :0:1....

thanks in advance.

@woodcock