[
https://issues.apache.org/jira/browse/ZOOKEEPER-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340452#comment-17340452
]
Li Wang commented on ZOOKEEPER-4211:
------------------------------------
Hi [~ztzg]
I figure you must be busy with other things. :)I should have the patch/changes
for supporting the CounterSet ready soon. Hope you will have some time for it,
so we can discuss and address any pending points and merge the PR. If not,
please let me know and I will ping other committers.
Yes, totally agree. Using CounterSet instead of SummarySet for metrics such as
QuotaExceededCountPerNamespace will avoid unnecessary computation and memory
overhead. It helps even after we change the metrics gathering to async
operation.
> 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
> Time Spent: 5.5h
> 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)
