Grafana dashboard not showing gluster volumes about gcs HOT 9 OPEN

ping: @sidharthanup @cloudbehl

from gcs.

AFAIK this happens because of multiple port forwarding and stuff that happens from pod to inside cluster to outside cluster, all they way up to the host. Which is why maybe Grafana is not able to resolve it initially. @sidharthanup Correct me if I'm wrong.
However, If you create a new Datasource with exact same config from inside the Grafana UI, it works instantly. (This could be documented as a manual fix maybe??)
@cloudbehl Any thoughts on this?

from gcs.

@umangachapagain no clues why it is not working now? @sidharthanup any updates from your side?

from gcs.

@aravindavk @aruniiird @shtripat Problem seems to be in the gluster-prometheus side..Once GCS is deployed, gluster-prometheus is not exposing any of the gluster metrics, not even the ps ones. One of the latest refactoring PRs must have prevented this. Looking into it.

from gcs.

Disregard the previous comment. The metrics are available and exported properly...GCS was deployed incorrectly and hence the above issue. Now I did some debugging and as @JohnStrunk reports the grafana dashboard does not show any metrics:

This is the volume capacity utilization metrics:

It seems like volume='$Volume' is where the issue lies. Removing it displays the correct metrics:

Also specifying volume=<name of gluster volume> yields the correct metrics( as it should):

So it seems like the Volume variable is not being set by gluster mixin. Not just for this metric but the same issue for others as well. @cloudbehl @umangachapagain Could you guys check it out in the gluster mixins side?

from gcs.

@anmolsachan Can you verify this? As far as I remember, this wasn't the case when we tested against 0.5.

from gcs.

@umangachapagain @sidharthanup Ack, Will verify what's the issue here.

from gcs.

@sidharthanup i deployed the GCS setup, I cannot see any gluster_volume* metrics in in prometheus. The grafana dashboards need those metrics for displaying the info.

It seems like volume='$Volume' is where the issue lies. Removing it displays the correct metrics:

$Volume is intended and needs to be there to select different volumes.

Also specifying volume=<name of gluster volume> yields the correct metrics( as it should):

Thats translates to volume='$Volume where $Volume is the selector.

from gcs.

Are there any updates or associated issues/PRs?

from gcs.