From b3812a106262c043db362e6e067610ac8b64c926 Mon Sep 17 00:00:00 2001 From: Dragos Misca Date: Fri, 5 Jul 2024 10:57:22 -0700 Subject: [PATCH] Describe OpenTelemetry memory reuse mode in Pulsar --- docs/deploy-monitoring.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/deploy-monitoring.md b/docs/deploy-monitoring.md index a2cd6306efd7..677a2c7718a0 100644 --- a/docs/deploy-monitoring.md +++ b/docs/deploy-monitoring.md @@ -229,3 +229,11 @@ OpenTelemetry provides an experimental mechanism to control the maximum cardinal limiting the resource usage of the exporter. Pulsar sets the value to 10000 attributes by default. For brokers with a large number of topics, this can prove insufficient. The value is controlled by environment variable `OTEL_EXPERIMENTAL_METRICS_CARDINALITY_LIMIT`. + +#### Memory Reuse Configuration + +OpenTelemetry provides an experimental mechanism to control the reuse of metric attributes. This is particularly useful +for systems with high cardinality metrics, as it reduces the number of memory allocations caused by collector runs. The +mechanism is enabled by default in Pulsar, and can be overridden by environment variable +`OTEL_JAVA_EXPERIMENTAL_EXPORTER_MEMORY_MODE`. For further details and valid configuration values, refer to the +exporter configuration [documentation](https://opentelemetry.io/docs/languages/java/configuration/#exporters).