Created attachment 1456251 [details] Volume dashboard Description of problem: When all cluster nodes are shut down then after a while there are `Invalid Number` values in Bricks panel next to Down and in Rebalance panel next to Size Version-Release number of selected component (if applicable): tendrl-ansible-1.6.3-5.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-7.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-5.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-5.el7rhgs.noarch tendrl-node-agent-1.6.3-7.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-4.el7rhgs.noarch How reproducible: 2/2 Steps to Reproduce: 1. Import cluster with distributed-replicated volume (I used 6x2). 2. Shut down all nodes in cluster. 3. Open Volume dashboard. 4. Wait for more than half an hour until there are no volume data shown in grafana. Actual results: There is `Invalid Number` written next to Down and Size in Bricks and Rebalance panels. Expected results: There should be no `Invalid Number` values. Additional info:
Asking for blocker evaluation as this is related to misleading data reported by WA.
@martin - This is default functioning of the Vonage plugin. If the number in Vonage is having validation and the data is not coming from time series database it shows "Invalid Number". We can't do much with this right now because the Issue that is written is with the plugin not with actual code.
(In reply to Ankush Behl from comment #2) > @martin - This is default functioning of the Vonage plugin. If the number in > Vonage is having validation and the data is not coming from time series > database it shows "Invalid Number". We can't do much with this right now > because the Issue that is written is with the plugin not with actual code. Understood. I think that it means that for 3.4, we need to describe this behavior clearly in: * WA docs: what does "invalid number" mean in general, explaining the plugin behavior * Description of the panel, what "invalid number" could mean here And for post 3.4, we may need to think about better ways of handling cases like this. Does it make sense? Linking the plugin for reference: https://grafana.com/plugins/vonage-status-panel
@Martin - Documenting in WA docs looks like a good idea. >> Description of the panel, what "invalid number" could mean here I think there are a lot of panels in grafana that uses Vonage plugin and adding the same description to all the panel will not make much sense. So let create a doc bz to document the "invalid number" scenario. @martin - can you please open a doc bz for this bug.
(In reply to Ankush Behl from comment #4) > I think there are a lot of panels in grafana that uses Vonage plugin and > adding the same description to all the panel will not make much sense. Ack. > @martin - can you please open a doc bz for this bug. Doc bug has been created: BZ 1605228
Based on comments 2,3, & 4, moving this bug out of 3.4.0
Shouldn't this be closed as now as doc BZ#1605228 is already closed?
(In reply to Shubhendu Tripathi from comment #8) > Shouldn't this be closed as now as doc BZ#1605228 is already closed? No, this behavior is not correct no matter how we document it.
The only way to solve this is we have to remove TTL form volume and brick, But we have to make sure volume delete is not affecting because of this Any suggestion?