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 Jan 30, 2020. It is now read-only.
Etcdv2 seems to have preliminary support for Prometheus metrics (2.1alpha). Are you guys planning on adding support for Prometheus metrics as well? It would be fantastic to be able to monitor:
whether this fleet instance is the current engine leader
task completion broken down by:
outcome (success, failure)
failure reason code, e.g. machine_left_cluster
number of locally scheduled fleet tasks (on that instance)
number of machines in the cluster by tag string
If it's not on your roadmap anytime soon, can you provide pointers on how to start hacking on this?
The text was updated successfully, but these errors were encountered:
I'm planning to have a look at implementing Prometheus metrics - but I'd like to double-check first that I'm not duplicating any effort that he fleet team currently has under way.
Etcdv2 seems to have preliminary support for Prometheus metrics (2.1alpha). Are you guys planning on adding support for Prometheus metrics as well? It would be fantastic to be able to monitor:
machine_left_cluster
If it's not on your roadmap anytime soon, can you provide pointers on how to start hacking on this?
The text was updated successfully, but these errors were encountered: