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
Grafana dashboard shows issues with instances that are uniquely part of multiple clusters sharing a common VIP for ReST queries via cb-exporter.
Let's say 7 instances with two clusters, one with 5 CB-VMs & other with 2 CB-VMs sharing common VIP.
Or Let's say 5 instances with one cluster only, one with 4 CB-VMs & one removed out CB-VM instance again sharing some common VIP.
The Couchbase stats are appearing on Grafana dashboard in a flickering manner. For example, server count will alter b/w two values if two clusters are there i.e. it keeps on flickering b/w "5" or "2" as per first case.
or it will shift b/w value ''1'' and ''4' for the other case with one cluster.
Similar behavior goes for other metrics that are related to cluster level stats. It seems CB-exporter client does scrape from each VM & puts data into Prometheus which might not be a desirable behavior as per above scenarios. Here, I have used instance & CB-VMs interchangeably.
The text was updated successfully, but these errors were encountered:
Grafana dashboard shows issues with instances that are uniquely part of multiple clusters sharing a common VIP for ReST queries via cb-exporter.
Let's say 7 instances with two clusters, one with 5 CB-VMs & other with 2 CB-VMs sharing common VIP.
Or Let's say 5 instances with one cluster only, one with 4 CB-VMs & one removed out CB-VM instance again sharing some common VIP.
The Couchbase stats are appearing on Grafana dashboard in a flickering manner. For example, server count will alter b/w two values if two clusters are there i.e. it keeps on flickering b/w "5" or "2" as per first case.
or it will shift b/w value ''1'' and ''4' for the other case with one cluster.
Similar behavior goes for other metrics that are related to cluster level stats. It seems CB-exporter client does scrape from each VM & puts data into Prometheus which might not be a desirable behavior as per above scenarios. Here, I have used instance & CB-VMs interchangeably.
The text was updated successfully, but these errors were encountered: