From 097291d6dc05e53c3041b291f603ff16f0ef7f1b Mon Sep 17 00:00:00 2001 From: Yuri Shkuro Date: Fri, 14 Jun 2024 00:17:35 -0400 Subject: [PATCH] Remove references to SpanMetrics Processor (#709) ## Which problem is this PR solving? - Resolves https://github.com/jaegertracing/jaeger/issues/4736 Signed-off-by: Yuri Shkuro --- content/docs/1.58/spm.md | 6 ------ content/docs/next-release/spm.md | 6 ------ 2 files changed, 12 deletions(-) diff --git a/content/docs/1.58/spm.md b/content/docs/1.58/spm.md index b336f0bb..b1b8fb93 100644 --- a/content/docs/1.58/spm.md +++ b/content/docs/1.58/spm.md @@ -56,12 +56,6 @@ can be started via docker. Be sure to include `--net monitor_backend` in the `do ## Architecture -{{< info >}} -Starting with v1.46.0, Jaeger supports the OpenTelemetry [SpanMetrics Connector](https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/connector/spanmetricsconnector#section-readme), which is replacing the deprecated [SpanMetrics Processor](https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/processor/). Please refer to the [migration guide](https://github.com/jaegertracing/jaeger/blob/main/docker-compose/monitor/README.md#migrating-to-span-metrics-connector). - -NB: Use `--prometheus.query.support-spanmetrics-connector=true` to explicitly enable the SpanMetrics Connector. This will become the default behavior in the future. -{{< /info >}} - The RED metrics queried by Jaeger for the Monitor tab are the result of span data collected by the [OpenTelemetry Collector][opentelemetry-collector] which is then aggregated by the [SpanMetrics Connector][spanmetrics-conn] component configured diff --git a/content/docs/next-release/spm.md b/content/docs/next-release/spm.md index b336f0bb..b1b8fb93 100644 --- a/content/docs/next-release/spm.md +++ b/content/docs/next-release/spm.md @@ -56,12 +56,6 @@ can be started via docker. Be sure to include `--net monitor_backend` in the `do ## Architecture -{{< info >}} -Starting with v1.46.0, Jaeger supports the OpenTelemetry [SpanMetrics Connector](https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/connector/spanmetricsconnector#section-readme), which is replacing the deprecated [SpanMetrics Processor](https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/processor/). Please refer to the [migration guide](https://github.com/jaegertracing/jaeger/blob/main/docker-compose/monitor/README.md#migrating-to-span-metrics-connector). - -NB: Use `--prometheus.query.support-spanmetrics-connector=true` to explicitly enable the SpanMetrics Connector. This will become the default behavior in the future. -{{< /info >}} - The RED metrics queried by Jaeger for the Monitor tab are the result of span data collected by the [OpenTelemetry Collector][opentelemetry-collector] which is then aggregated by the [SpanMetrics Connector][spanmetrics-conn] component configured