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
{{ message }}
This repository has been archived by the owner on Apr 30, 2020. It is now read-only.
Describe the feature you'd like to have.
It should be possible to monitor the Gluster cluster via prometheus
What is the value to the end user? (why is it a priority?)
Prometheus is the monitoring solution for Kubernetes, and as such, admins expect it to be the place to go for metrics about the services running in their infra. By providing statistics about the cluster, admins can be assured things are working well, or they know that they need to dig deeper.
How will we know we have a good solution? (acceptance criteria)
Statistics about the Gluster cluster are available in Prometheus
Work items
Create Prometheus endpoint
Instrument operator actions and provide counts to prometheus endpoint
Provide node uptime metrics
Provide stats on storage assigned to Gluster
Additional context
We need to consider what data should come from the operator and what should come from the Gluster pods themselves or the CSI driver.
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like to have.
It should be possible to monitor the Gluster cluster via prometheus
What is the value to the end user? (why is it a priority?)
Prometheus is the monitoring solution for Kubernetes, and as such, admins expect it to be the place to go for metrics about the services running in their infra. By providing statistics about the cluster, admins can be assured things are working well, or they know that they need to dig deeper.
How will we know we have a good solution? (acceptance criteria)
Work items
Additional context
We need to consider what data should come from the operator and what should come from the Gluster pods themselves or the CSI driver.
The text was updated successfully, but these errors were encountered: