Skip to content
This repository has been archived by the owner on Apr 30, 2020. It is now read-only.

Prometheus monitoring #25

Open
4 tasks
JohnStrunk opened this issue Jun 28, 2018 · 0 comments
Open
4 tasks

Prometheus monitoring #25

JohnStrunk opened this issue Jun 28, 2018 · 0 comments
Labels
epic Large, multi-issue feature set needs-subtasks Issue needs to be sub-divided into smaller items

Comments

@JohnStrunk
Copy link
Member

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.

@JohnStrunk JohnStrunk added epic Large, multi-issue feature set needs-subtasks Issue needs to be sub-divided into smaller items labels Jun 28, 2018
@JohnStrunk JohnStrunk added this to the future milestone Jun 28, 2018
@JohnStrunk JohnStrunk modified the milestones: future, GCS-1.0 Sep 24, 2018
@JohnStrunk JohnStrunk removed this from the GCS-1.0 milestone Oct 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
epic Large, multi-issue feature set needs-subtasks Issue needs to be sub-divided into smaller items
Projects
None yet
Development

No branches or pull requests

1 participant