Shubhendu

@aravindavk @vpandey-RH @aspandey ^^^

@atinmu I tried with bigger timeout but no help. There is another finding, if I create a pure disperse volume the heal-info works in gd2 but for a distribute-disperse (which...

@aruniiird makes sense and later this interface can expose a channel as explained in https://github.com/gluster/gluster-prometheus/issues/125 which would get details like local peer id, volume info, leader info etc. @aravindavk does...

May be useful ones - device iops - device throughput - device latency - brick process status - device count - bricks count on the device where the brick is...

The disk specific metrics like `iops`, `thorughput`, `latency` would be exposed by k8s. Regarding brick process status, there a metric `gluster_brick_up` is exposed. device count can be achieved using recording...

@cloudbehl I feel the one named `gluster_promethues_up` should rather be called `gluster_exporter_up`

IIUC we can do the below things for marking the running status of services - gluster_exporter - when exporterstarts, it will set the value of gluster_exporter_up = 1 in prometheus...

Few additional metrics at volume level required - brick count - IOPS - throughput

@labazza I tried importing this dashboards in this PR in my grafana setup but it fails with error `Template variables could not be initialized: Cannot read property indexOf of undefined`....

I tried this scenario with minio version RELEASE.2023-01-20T02-05-44Z and mc version RELEASE.2023-01-11T03-14-16Z. The source/bucket had 150 GiB of data with few 10s of objects only (approx of sizes 10GiB and...