From 37af6895aabe7573a20ee4a538ecd58baccc288a Mon Sep 17 00:00:00 2001 From: Max Leonov Date: Mon, 4 Mar 2024 11:45:55 +0100 Subject: [PATCH] OBSDOCS-882: Tweak the DT 3.1 RN --- distr_tracing/distr_tracing_rn/distr-tracing-rn-3-1.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/distr_tracing/distr_tracing_rn/distr-tracing-rn-3-1.adoc b/distr_tracing/distr_tracing_rn/distr-tracing-rn-3-1.adoc index 7d340d57fc..df68573526 100644 --- a/distr_tracing/distr_tracing_rn/distr-tracing-rn-3-1.adoc +++ b/distr_tracing/distr_tracing_rn/distr-tracing-rn-3-1.adoc @@ -83,7 +83,7 @@ There are currently known issues: [id="distributed-tracing-rn_3-1_jaeger-release-notes_deprecated-functionality"] === Deprecated functionality -In the {DTProductName} 3.1, Jaeger and support for Elasticsearch are deprecated, and both are planned to be removed in a future release. Red Hat will provide critical and above CVE bug fixes and support for these components during the current release lifecycle, but these components will no longer receive feature enhancements. +In the {DTProductName} 3.1, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release. Red Hat will provide critical and above CVE bug fixes and support for these components during the current release lifecycle, but these components will no longer receive feature enhancements. In the {DTProductName} 3.1, Tempo provided by the {TempoOperator} and the OpenTelemetry Collector provided by the {OTELName} are the preferred Operators for distributed tracing collection and storage. The OpenTelemetry and Tempo distributed tracing stack is to be adopted by all users because this will be the stack that will be enhanced going forward.