11.3 - Netdata Plugin and network chart

[MikeyG]

I'm thrilled to see that a community plugin for Netdata has been created for use in 11.3! Installed it and it works great. However, it appears that the network charts won't work because it's monitoring the jail interface and not the lagg or other interfaces on the FreeNAS server itself. Is there any way for me to fix that? Is this something that might be fixed in a future update?

Thank for whomever created this!

 

[Dreded]

Same question, I just installed using the default NAT option as I assumed the default would be correct.

 

[MikeyG]

Same question, I just installed using the default NAT option as I assumed the default would be correct.

I tried both options. Neither helped.

 

[darkcloud784]

I'd like to bump this as I'd like to know as well

 

[_Alchemist_]

I have the same Problem, its just showing "epair0b" in the network interfaces
So I always get 0 Kbps with net inbound and outbound in the System Overview

 

[Samuel Tai]

It's not possible for the jail to monitor the host interfaces.

 

[_Alchemist_]

weird, for some reason it still worked a couple of months ago, then I played around with LACP and it stopped working

 

[MikeyG]

@_Alchemist_ Are you sure you were on 11.3 a couple of months ago? I've never had the network charts work on the plugin on 11.3.

 

[_Alchemist_]

Yes, but I think it only worked because I installed it when I was still using FreeNAS 11.2 before I upgraded to 11.3, but I could be wrong ... (cant remember)

 

[NeoSlugman]

Same problem for me. I'm looking for a solution.
I've seen that the plugin renamed the interface each time I tried to reinstall it :

Code:

Sep  6 01:22:38 truenas kernel: epair0a: link state changed to UP
Sep  6 01:22:38 truenas kernel: epair0b: link state changed to UP
Sep  6 01:22:38 truenas kernel: epair0a: changing name to 'vnet0.7'
Sep  6 01:22:41 truenas kernel: lo0: link state changed to UP
Sep  6 01:23:33 truenas kernel: vnet0.7: link state changed to DOWN
Sep  6 01:23:33 truenas kernel: epair0b: link state changed to DOWN
Sep  6 01:23:47 truenas kernel: epair0a: Ethernet address: xx:xx:xx:xx:xx:xa
Sep  6 01:23:47 truenas kernel: epair0b: Ethernet address: xx:xx:xx:xx:xx:xb
Sep  6 01:23:47 truenas kernel: epair0a: link state changed to UP
Sep  6 01:23:47 truenas kernel: epair0b: link state changed to UP
Sep  6 01:23:47 truenas kernel: epair0a: changing name to 'vnet0.8'
Sep  6 01:23:49 truenas kernel: lo0: link state changed to UP

 

[Frikkie]

If you use the VNET option a virtualised network stack is created and the jail can't see the physical interfaces.
Set it up as I have in the screenshot and let me know if it works for you.

Changed settings: VNET off, Berkeley Packet Filter off, choose the correct network adapter (ex. mlxen0) and set a static IP. The rest is left at the Netdata community plugin default values.

Result:

 

[MikeyG]

@Frikkie Thanks for the tip! I'm not too familiar with jails, but when I try to install as you suggest, I get the following:

Any suggestions? Did you have to create a dataset for netdata first?

 

[Frikkie]

No I did not. The dataset creation is usually taken care of when first installing the plugin.
On your VM/Jail storage pool under "iocage".
Did you set a static IP and the (in most cases) correct /24 subnet?

 

[MikeyG]

Yes, set the correct IP info. I am running 12-U2 now though. Maybe something is different there.

 

[Frikkie]

I don't think it is release specific as I am running 12-U2 and just set up Netdata today.
You could try starting from a clean slate if that is a possibility.

 

[MikeyG]

Interesting. I deleted the entire iocage dataset since I have no other jails, did the reinstall and it went through. I can now ping the IP that I assigned to it, but at port 19999 netdata doesn't come up.

 

[Frikkie]

Here are my other settings in case you want to do a 1:1 comparison.

Ignore the "IPv4 Default Router" value. The option is not available (greyed out) and irrelevant because VNET is disabled.

 

[MikeyG]

Hmm, pretty much all the same settings here. Not sure why it doesn't work. I wonder if it's because I'm using a lagg. Thank you for sharing though.

 

[Frikkie]

My pleasure. :)

Hmm, pretty much all the same settings here. Not sure why it doesn't work. I wonder if it's because I'm using a lagg. Thank you for sharing though.

Thaaaaaaaat could very well be the case... Don't use LAGG myself but I could try it out on my TrueNAS Scale test vm to see what happens.
I'll get back to you.

 

[MikeyG]

Turns out that it now works after a full system reboot. LAGG (multiple LAGGs) included. Thanks again!