visortelle commented on code in PR #21635: URL: https://github.com/apache/pulsar/pull/21635#discussion_r1417609104
########## pip/pip-320.md: ########## @@ -0,0 +1,241 @@ +# PIP-320 OpenTelemetry Scaffolding + +# Background knowledge + +## PIP-264 - parent PIP titled "Enhanced OTel-based metric system" +[PIP-264](https://github.com/apache/pulsar/pull/21080), which can also be viewed [here](pip-264.md), describes in high +level a plan to greatly enhance Pulsar metric system by replacing it with [OpenTelemetry](https://opentelemetry.io/). +You can read in the PIP the numerous existing problems PIP-264 solves. Among them are: +- Control which metrics to export per topic/group/namespace via the introduction of a metric filter configuration +- Reduce the immense metrics cardinality due to high topic count (One of Pulsar great features), by introducing Review Comment: It would be useful to have some best practices/recipes/recommendations in the documentation on which cases I should use groups, and in which not. With the attached benchmark results. In other words, it would be nice to have some kind of algorithm for when and how to group metrics. Maybe not related to the PIP itself. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
