OBSDOCS-868: Release notes for Distributed Tracing 3.2

Author: max-cx

_topic_maps/_topic_map.yml

@@ -2805,8 +2805,8 @@ Topics:
   - Name: Release notes
     Dir: distr_tracing_rn
     Topics:
-    - Name: Distributed tracing 3.1.1
-      File: distr-tracing-rn-3-1-1
+    - Name: Distributed tracing 3.2
+      File: distr-tracing-rn-3-2
     - Name: Past releases
       File: distr-tracing-rn-past-releases
   - Name: Distributed tracing architecture
@@ -2843,8 +2843,8 @@ Topics:
   - Name: Release notes
     Dir: otel_rn
     Topics:
-    - Name: Red Hat build of OpenTelemetry 3.1.1
-      File: otel-rn-3-1-1
+    - Name: Red Hat build of OpenTelemetry 3.2
+      File: otel-rn-3-2
     - Name: Past releases
       File: otel-rn-past-releases
   - Name: Installing

modules/otel-product-overview.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * observability/otel/otel_rn/otel-rn-3-1.adoc
+// * observability/otel/otel_rn/otel-rn-3-2.adoc
 // * observability/otel/otel_rn/otel-rn-past-releases.adoc
 
 :_mod-docs-content-type: CONCEPT

observability/distr_tracing/distr_tracing_rn/distr-tracing-rn-3-1-1.adoc

@@ -0,0 +1,129 @@
+:_mod-docs-content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
+[id="distributed-tracing-rn-3-2"]
+= Release notes for {DTProductName} 3.2
+:context: distributed-tracing-rn-3-2
+
+toc::[]
+
+include::modules/distr-tracing-product-overview.adoc[leveloffset=+1]
+
+You can use the {DTShortName} xref:../../otel/otel-forwarding.adoc#otel-forwarding-traces[in combination with] the xref:../../otel/otel-installing.adoc#install-otel[{OTELName}].
+
+This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
+
+////
+[id="distributed-tracing-rn_3-2_cves"]
+== CVEs
+
+This release fixes link:https://access.redhat.com/security/cve/cve-202?-?????[CVE-202?-?????].
+////
+
+[id="distributed-tracing-rn_3-2_tempo-release-notes"]
+== {TempoName}
+
+The {TempoName} is provided through the {TempoOperator}.
+
+[id="distributed-tracing-rn_3-2_tempo-release-notes_technology-preview-features"]
+=== Technology Preview features
+
+This update introduces the following Technology Preview feature:
+
+* Support for the Tempo monolithic deployment.
+
+:FeatureName: The Tempo monolithic deployment
+include::snippets/technology-preview.adoc[leveloffset=+1]
+
+[id="distributed-tracing-rn_3-2_tempo-release-notes_new-features-and-enhancements"]
+=== New features and enhancements
+
+This update introduces the following enhancements:
+
+* {TempoName} 3.2 is based on the open source link:https://grafana.com/oss/tempo/[Grafana Tempo] 2.4.1.
+* Allowing the overriding of resources per component.
+
+////
+[id="distributed-tracing-rn_3-2_tempo-release-notes_deprecated-functionality"]
+=== Deprecated functionality
+
+In the {TempoName} 3.2, ???
+////
+
+////
+[id="distributed-tracing-rn_3-2_tempo-release-notes_removal-notice"]
+=== Removal notice
+
+In {TempoName} 3.2, the FEATURE has been removed. Bug fixes and support are provided only through the end of the 3.? lifecycle. As an alternative to the FEATURE for USE CASE, you can use the ALTERNATIVE instead.
+////
+
+[id="distributed-tracing-rn_3-2_tempo-release-notes_bug-fixes"]
+=== Bug fixes
+
+This update introduces the following bug fixes:
+
+* Before this update, the Jaeger UI only displayed services that sent traces in the previous 15 minutes. With this update, the availability of the service and operation names can be configured by using the following field: `spec.template.queryFrontend.jaegerQuery.servicesQueryDuration`. (link:https://issues.redhat.com/browse/TRACING-3139[TRACING-3139])
+* Before this update, the `query-frontend` pod might get stopped when out-of-memory (OOM) as a result of searching a large trace. With this update, resource limits can be set to prevent this issue. (link:https://issues.redhat.com/browse/TRACING-4009[TRACING-4009])
+
+[id="distributed-tracing-rn_3-2_tempo-release-notes_known-issues"]
+=== Known issues
+
+There is currently a known issue:
+
+* Currently, the {TempoShortName} fails on the IBM Z (`s390x`) architecture. (link:https://issues.redhat.com/browse/TRACING-3545[TRACING-3545])
+
+[id="distributed-tracing-rn_3-2_jaeger-release-notes"]
+== {JaegerName}
+
+The {JaegerName} is provided through the {JaegerOperator} Operator.
+
+[IMPORTANT]
+====
+Jaeger does not use FIPS validated cryptographic modules.
+====
+
+[id="distributed-tracing-rn_3-2_jaeger-release-notes_support-for-elasticsearch-operator"]
+=== Support for {es-op}
+
+{JaegerName} 3.2 is supported for use with the {es-op} 5.6, 5.7, and 5.8.
+
+[id="distributed-tracing-rn_3-2_jaeger-release-notes_deprecated-functionality"]
+=== Deprecated functionality
+
+In the {DTProductName} 3.2, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release.
+Red Hat will provide support for these components and fixes for CVEs and bugs with critical and higher severity during the current release lifecycle, but these components will no longer receive feature enhancements.
+The {TempoOperator} and the {OTELName} are the preferred Operators for distributed tracing collection and storage.
+Users must adopt the OpenTelemetry and Tempo distributed tracing stack because it is the stack to be enhanced going forward.
+
+In the {DTProductName} 3.2, the Jaeger agent is deprecated and planned to be removed in the following release.
+Red Hat will provide bug fixes and support for the Jaeger agent during the current release lifecycle, but the Jaeger agent will no longer receive enhancements and will be removed.
+The OpenTelemetry Collector provided by the {OTELName} is the preferred Operator for injecting the trace collector agent.
+
+////
+[id="distributed-tracing-rn_3-2_jaeger-release-notes_removal-notice"]
+=== Removal notice
+
+In {DTProductName} 3.2, the FEATURE has been removed. Bug fixes and support are provided only through the end of the 3.? lifecycle. As an alternative to the FEATURE for USE CASE, you can use the ALTERNATIVE instead.
+////
+
+[id="distributed-tracing-rn_3-2_jaeger-release-notes_new-features-and-enhancements"]
+=== New features and enhancements
+
+This update introduces the following enhancements for the {JaegerShortName}:
+
+* {JaegerName} 3.2 is based on the open source link:https://www.jaegertracing.io/[Jaeger] release 1.57.0.
+
+[id="distributed-tracing-rn_3-2_jaeger-release-notes_known-issues"]
+=== Known issues
+
+There is currently a known issue:
+
+* Currently, Apache Spark is not supported.
+
+ifndef::openshift-rosa[]
+
+* Currently, the streaming deployment via AMQ/Kafka is not supported on the {ibm-z-title} and {ibm-power-title} architectures.
+endif::openshift-rosa[]
+
+include::modules/support.adoc[leveloffset=+1]
+
+include::modules/making-open-source-more-inclusive.adoc[leveloffset=+1]

observability/distr_tracing/distr_tracing_rn/distr-tracing-rn-3-2.adoc

@@ -10,6 +10,67 @@ include::modules/distr-tracing-product-overview.adoc[leveloffset=+1]
 
 You can use the {DTShortName} xref:../../otel/otel-forwarding.adoc#otel-forwarding-traces[in combination with] the xref:../../otel/otel-installing.adoc#install-otel[{OTELName}].
 
+[id="distributed-tracing-rn-3-1-1"]
+== Release notes for {DTProductName} 3.1.1
+
+This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
+
+[id="distributed-tracing-rn_3-1-1_cves"]
+=== CVEs
+
+This release fixes link:https://access.redhat.com/security/cve/cve-2023-39326[CVE-2023-39326].
+
+// Tempo section
+[id="distributed-tracing-rn_3-1-1_tempo-release-notes"]
+=== {TempoName}
+
+The {TempoName} is provided through the {TempoOperator}.
+
+[id="distributed-tracing-rn_3-1-1_tempo-release-notes_known-issues"]
+==== Known issues
+
+//There is currently a known issue:
+There are currently known issues:
+
+* Currently, when used with the {TempoOperator}, the Jaeger UI only displays services that have sent traces in the last 15 minutes. For services that did not send traces in the last 15 minutes, traces are still stored but not displayed in the Jaeger UI. (link:https://issues.redhat.com/browse/TRACING-3139[TRACING-3139])
+* Currently, the {TempoShortName} fails on the IBM Z (`s390x`) architecture. (link:https://issues.redhat.com/browse/TRACING-3545[TRACING-3545])
+
+// Jaeger section
+[id="distributed-tracing-rn_3-1-1_jaeger-release-notes"]
+=== {JaegerName}
+
+The {JaegerName} is provided through the {JaegerOperator} Operator.
+
+[IMPORTANT]
+====
+Jaeger does not use FIPS validated cryptographic modules.
+====
+
+[id="distributed-tracing-rn_3-1-1_jaeger-release-notes_support-for-elasticsearch-operator"]
+==== Support for {es-op}
+
+{JaegerName} 3.1.1 is supported for use with the {es-op} 5.6, 5.7, and 5.8.
+
+[id="distributed-tracing-rn_3-1-1_jaeger-release-notes_deprecated-functionality"]
+==== Deprecated functionality
+
+In the {DTProductName} 3.1.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.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.
+
+[id="distributed-tracing-rn_3-1-1_jaeger-release-notes_known-issues"]
+==== Known issues
+
+//There is currently a known issue:
+There are currently known issues:
+
+* Currently, Apache Spark is not supported.
+
+ifndef::openshift-rosa[]
+
+* Currently, the streaming deployment via AMQ/Kafka is not supported on the {ibm-z-title} and {ibm-power-title} architectures.
+endif::openshift-rosa[]
+
 [id="distributed-tracing-rn-3-1"]
 == Release notes for {DTProductName} 3.1