From 066f07ed857311edc173acf34342c6710cb2428f Mon Sep 17 00:00:00 2001 From: Julien Jakubowski Date: Mon, 22 Jan 2024 18:06:38 +0100 Subject: [PATCH] Update blog/2024-01-12-pulsar-2023-year-in-review.md Co-authored-by: Kiryl Valkovich --- blog/2024-01-12-pulsar-2023-year-in-review.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2024-01-12-pulsar-2023-year-in-review.md b/blog/2024-01-12-pulsar-2023-year-in-review.md index eacea20472ce..312d9234611c 100644 --- a/blog/2024-01-12-pulsar-2023-year-in-review.md +++ b/blog/2024-01-12-pulsar-2023-year-in-review.md @@ -126,7 +126,7 @@ The Pulsar community seeks to further improve the project from different aspects As stated above, [PIP-264](https://github.com/apache/pulsar/blob/master/pip/pip-264.md) is designed to enhance observability in scenarios where a single cluster manages a large number of topics, ranging from 50k up to 1M topics. Currently, there are two major features under development to support this functionality: - [Near-zero memory allocations](https://github.com/open-telemetry/opentelemetry-java/issues/5105) -- [metric filtering upon collection](https://github.com/open-telemetry/opentelemetry-java/issues/6107), which was also added to [OpenTelemetry specifications](https://github.com/open-telemetry/opentelemetry-specification/issues/3324). +- [Metric filtering upon collection](https://github.com/open-telemetry/opentelemetry-java/issues/6107), which was also added to [OpenTelemetry specifications](https://github.com/open-telemetry/opentelemetry-specification/issues/3324). ## Pulsar Rate Limiting