Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add gauge metric for master of leader election. #71731
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
@cheftako is this a per local node metric ? How will i know using this metric which node has the lock ? Today i can do
@krmayankk the metric will show up in an individual servers /metrics endpoint. So prometheus or whichever system is collecting the metrics should be associating that with the server from which it gathered the metric. This is common to all the metrics coming out of the /metrics endpoint. (Eg. "daemonset_queue_latency_count 104") Presumably you will have something periodically scraping this endpoint and creating a graph for your HA cluster.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: caesarxuchao, cheftako, deads2k, mikedanese
If they are not already assigned, you can assign the PR to them by writing
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing