Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose alarms as metrics #14234

Closed
stek29 opened this issue Jul 19, 2022 · 4 comments · Fixed by #14276
Closed

Expose alarms as metrics #14234

stek29 opened this issue Jul 19, 2022 · 4 comments · Fixed by #14276
Assignees

Comments

@stek29
Copy link

stek29 commented Jul 19, 2022

Currently the only way to know about alarms is to issue an maitenance/alarm grpc call to list currently active alarms (by using etcdctl alarm list, for example).

It would be great to have expose etcd alarms in prometheus metrics so they're easier to monitor and know about.

@yuzhiquan
Copy link
Contributor

yuzhiquan commented Jul 26, 2022

/assign @yuzhiquan

@stek29
Copy link
Author

stek29 commented Aug 9, 2022

@ahrtr @serathius is there any chance to get this in next 3.5.x release?
I'm not familiar with etcd release process and backporting, and I haven't been able to find any docs on it.

@ahrtr
Copy link
Member

ahrtr commented Aug 9, 2022

@stek29 FYI. https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/release.md#patch-version-release

Usually we only cherry pick bug fixes and security patches. So normally we shouldn't backport the PR #14276 to 3.5.

@stek29
Copy link
Author

stek29 commented Aug 10, 2022

@ahrtr got it, we'll stick to custom exporter until 3.6 is mature enough for us to use in production then

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

4 participants