You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Damien Diederen (Jira)" <ji...@apache.org> on 2021/07/29 09:38:00 UTC
[jira] [Resolved] (ZOOKEEPER-4211) Expose Quota Metrics to
Prometheus
[ https://issues.apache.org/jira/browse/ZOOKEEPER-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damien Diederen resolved ZOOKEEPER-4211.
----------------------------------------
Fix Version/s: 3.8.0
Resolution: Fixed
Issue resolved by pull request 1644
[https://github.com/apache/zookeeper/pull/1644]
> Expose Quota Metrics to Prometheus
> ----------------------------------
>
> Key: ZOOKEEPER-4211
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4211
> Project: ZooKeeper
> Issue Type: New Feature
> Components: metric system
> Affects Versions: 3.7.0, 3.7
> Reporter: Li Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.8.0
>
> Time Spent: 11h
> Remaining Estimate: 0h
>
> In 3.7, Quota limit can be enforced and the quota related stats are captured in the StatsTrack. From the "listquota" CLI command, we can the quota limit and usage info.
> As an addition to that, we would like to collect the quota metrics and expose them to the Prometheus for the following:
> 1. Monitoring per namespace (Chroot) quota usage via the Grafana dashboard
> 2. Creating alert based on the quota levels (e.g. 90% used)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)