Remove references to SpanMetrics Processor (#709)

## Which problem is this PR solving? - Resolves jaegertracing/jaeger#4736 Signed-off-by: Yuri Shkuro <[email protected]>
jaegertracing · Jun 14, 2024 · 097291d · 097291d
1 parent 0936851
commit 097291d
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 12 deletions.
diff --git 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
@@ -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