#dashboard issue NABox

1 messages · Page 1 of 1 (latest)

peak otter
#

@quartz lichen What do you mean by Systems ? Do you mean this variable is not visible in dashboards? Or is it an NABox related issue

#

?

quartz lichen
peak otter
#

got it thanks @waxen jay

waxen jay
#

Maybe you didn't wait long enough ? As long as the system is collecting it should populate de menu.

#

That's a dynamic value and as long as collection is working it will be presented to the user.

quartz lichen
#

No. We dont touch the nabox settings never.
We only switched off-on because the 2 filer were not present in the variable.
After we did that the two systems were there.

The data was collected, but the query of Cluster variable in Grafana would not show the 2 filer.

#

Next time it happens i will report before i switch the systems in nabox. Maybe this helps.

#

We had this multiple times already and we believe that this happens only on the Volume Dashboard.
But as for now we are not sure 100% if other Dashboards were affected as well

peak otter
#

@quartz lichen I think this could be happening due to volume zapi timeout. Volume dashboard uses volume_labels to populate cluster while most other dashboard uses node_labels .When it happens next time, could you check the logs of that missing cluster and see if there are any timeouts. One solution would be to increase Zapi timeout in template if that is the case.

quartz lichen
peak otter
#

dc logs nabox-harvest2 > nabox-harvest2.log