From 6dd908a826452253bf6bd28f3e2c3f7cb7549540 Mon Sep 17 00:00:00 2001 From: Dragos Misca Date: Fri, 5 Jul 2024 10:44:14 -0700 Subject: [PATCH] Clarify OpenTelemetry resource attributes to Prometheus labels relationship --- docs/deploy-monitoring.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/docs/deploy-monitoring.md b/docs/deploy-monitoring.md index ded3d9c3a783..a2cd6306efd7 100644 --- a/docs/deploy-monitoring.md +++ b/docs/deploy-monitoring.md @@ -195,12 +195,7 @@ OTEL_EXPORTER_PROMETHEUS_PORT This endpoint must be accessible by the remote Prometheus scrape server. Note that the exporter is less resource efficient than the OTLP exporter. -Prometheus currently exports the resource attributes in metric `target_info`. In practice, if you have more than one -cluster, it forces you to use PromQL joins to obtain the cluster ID label. - -The Pulsar community has added the option to the OpenTelemetry Java SDK Prometheus Exporter to embed (copy) the cluster -ID label (`pulsar.cluster`) to each outgoing time series labels. Once this is finalized it will be added by default into -Pulsar. +All OpenTelemetry resource attributes are automatically copied to Prometheus labels on each time series. For further configuration details, refer to the exporter [documentation](https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md#prometheus-exporter).