You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have ZFS zpools then the "ZFS Pools" node under "Sections and Charts" will list only a single zpool name.
Also, the chart itself will be named after a single zpool.
The chart lists all zpools but they are easily missed because the default is to sort by Dimension and the expected state is that they are all present/true (bool) and so we get a single line.
a. The zpools should either all be listed under the ZFS Pools nodes or none of them should be and just shown in the chart.
b. Suggest that perhaps changing the default chart type being 'Stacked' might make it a little more intuitive?
c. Strongly suggest taking the opportunity of merging the "ZFS Pools" and "ZFS Cache" under a parent node (i.e. "ZFS")
Steps to reproduce
Should be easy to repro as it occurs whether selecting the metrics of a single node with multiple zpools and or multiple hosts with single/multiple zpools.
Let me know if you need to see a live system with the behaviour.
Bug description
See this Netdata forum link for a visual:
https://community.netdata.cloud/t/how-to-show-multiple-zfs-pools/5170/2?u=luis_johnstone
Expected behavior
a. The zpools should either all be listed under the ZFS Pools nodes or none of them should be and just shown in the chart.
b. Suggest that perhaps changing the default chart type being 'Stacked' might make it a little more intuitive?
c. Strongly suggest taking the opportunity of merging the "ZFS Pools" and "ZFS Cache" under a parent node (i.e. "ZFS")
Steps to reproduce
Should be easy to repro as it occurs whether selecting the metrics of a single node with multiple zpools and or multiple hosts with single/multiple zpools.
Let me know if you need to see a live system with the behaviour.
Installation method
kickstart.sh
System info
Netdata build info
Additional info
No response
The text was updated successfully, but these errors were encountered: