Skip to content

Commit bc5ba93

Browse files
jeana-redhatjeana-redhat
authored
Merge pull request #80135 from max-cx/OBSDOCS-1124
OBSDOCS-1124: Release notes for Distributed tracing 3.3
2 parents 294e6ed + bc3437e commit bc5ba93

File tree

2 files changed

+203
-1
lines changed

2 files changed

+203
-1
lines changed

‎observability/distr_tracing/distr-tracing-rn.adoc

Lines changed: 134 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,143 @@ toc::[]
88

99
include::modules/distr-tracing-product-overview.adoc[leveloffset=+1]
1010

11-
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}].
11+
You can use the {TempoName} xref:../otel/otel-forwarding.adoc#otel-forwarding-traces[in combination with] the xref:../otel/otel-rn.adoc#otel_rn[{OTELName}].
1212

1313
include::snippets/distr-tracing-and-otel-disclaimer-about-docs-for-supported-features-only.adoc[]
1414

15+
[id="distr-tracing_3-3_{context}"]
16+
== Release notes for {DTProductName} 3.3
17+
18+
This release of the {DTProductName} includes the {TempoName} and the deprecated {JaegerName}.
19+
20+
////
21+
[id="distr-tracing_3-3_cves_{context}"]
22+
=== CVEs
23+
24+
This release fixes the following CVEs:
25+
26+
* link:https://access.redhat.com/security/cve/CVE-202?-????/[CVE-202?-????]
27+
////
28+
29+
[id="distr-tracing_3-3_tempo-release-notes_{context}"]
30+
=== {TempoName}
31+
32+
The {TempoName} is provided through the {TempoOperator}.
33+
34+
The {TempoName} 3.3 is based on the open source link:https://grafana.com/oss/tempo/[Grafana Tempo] 2.5.0.
35+
36+
////
37+
[id="distr-tracing_3-3_tempo-release-notes_technology-preview-features_{context}"]
38+
==== Technology Preview features
39+
40+
This update introduces the following Technology Preview feature:
41+
42+
* ???.
43+
44+
:FeatureName: The Tempo monolithic deployment
45+
include::snippets/technology-preview.adoc[leveloffset=+1]
46+
////
47+
48+
[id="distr-tracing_3-3_tempo-release-notes_new-features-and-enhancements_{context}"]
49+
==== New features and enhancements
50+
51+
This update introduces the following enhancements:
52+
53+
* Support for securing the Jaeger UI and Jaeger APIs with the OpenShift OAuth Proxy. (link:https://issues.redhat.com/browse/TRACING-4108[TRACING-4108])
54+
* Support for using the service serving certificates, which are generated by {product-title}, on ingestion APIs when multitenancy is disabled. (link:https://issues.redhat.com/browse/TRACING-3954[TRACING-3954])
55+
* Support for ingesting by using the OTLP/HTTP protocol when multitenancy is enabled. (link:https://issues.redhat.com/browse/TRACING-4171[TRACING-4171])
56+
* Support for the AWS S3 Secure Token authentication. (link:https://issues.redhat.com/browse/TRACING-4176[TRACING-4176])
57+
* Support for automatically reloading certificates. (link:https://issues.redhat.com/browse/TRACING-4185[TRACING-4185])
58+
* Support for configuring the duration for which service names are available for querying. (link:https://issues.redhat.com/browse/TRACING-4214[TRACING-4214])
59+
60+
////
61+
[id="distr-tracing_3-3_tempo-release-notes_deprecated-functionality_{context}"]
62+
==== Deprecated functionality
63+
64+
In the {TempoName} 3.3, ???.
65+
////
66+
67+
////
68+
[id="distr-tracing_3-3_tempo-release-notes_removal-notice_{context}"]
69+
==== Removal notice
70+
71+
In the {TempoName} 3.3, 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.
72+
////
73+
74+
[id="distr-tracing_3-3_tempo-release-notes_bug-fixes_{context}"]
75+
==== Bug fixes
76+
77+
This update introduces the following bug fixes:
78+
79+
* Before this update, storage certificate names did not support dots. With this update, storage certificate name can contain dots. (link:https://issues.redhat.com/browse/TRACING-4348[TRACING-4348])
80+
* Before this update, some users had to select a certificate when accessing the gateway route. With this update, there is no prompt to select a certificate. (link:https://issues.redhat.com/browse/TRACING-4431[TRACING-4431])
81+
* Before this update, the gateway component was not scalable. With this update, the gateway component is scalable. (link:https://issues.redhat.com/browse/TRACING-4497[TRACING-4497])
82+
* Before this update the Jaeger UI might fail with the *504 Gateway Time-out* error when accessed via a route. With this update, users can specify route annotations for increasing timeout, such as `haproxy.router.openshift.io/timeout: 3m`, when querying large data sets. (link:https://issues.redhat.com/browse/TRACING-4511[TRACING-4511])
83+
84+
[id="distr-tracing_3-3_tempo-release-notes_known-issues_{context}"]
85+
==== Known issues
86+
87+
There is currently a known issue:
88+
89+
* Currently, the {TempoShortName} fails on the {ibm-z-title} (`s390x`) architecture. (link:https://issues.redhat.com/browse/TRACING-3545[TRACING-3545])
90+
91+
[id="distr-tracing_3-3_jaeger-release-notes_{context}"]
92+
=== {JaegerName}
93+
94+
The {JaegerName} is provided through the {JaegerOperator} Operator.
95+
96+
The {JaegerName} 3.3 is based on the open source link:https://www.jaegertracing.io/[Jaeger] release 1.57.0.
97+
98+
[IMPORTANT]
99+
====
100+
Jaeger does not use FIPS validated cryptographic modules.
101+
====
102+
103+
[id="distr-tracing_3-3_jaeger-release-notes_support-for-elasticsearch-operator_{context}"]
104+
==== Support for the {es-op}
105+
106+
The {JaegerName} 3.3 is supported for use with the {es-op} 5.6, 5.7, and 5.8.
107+
108+
[id="distr-tracing_3-3_jaeger-release-notes_deprecated-functionality_{context}"]
109+
==== Deprecated functionality
110+
111+
In the {DTProductName} 3.3, Jaeger and support for Elasticsearch remain deprecated, and both are planned to be removed in a future release.
112+
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.
113+
The {TempoOperator} and the {OTELName} are the preferred Operators for distributed tracing collection and storage.
114+
Users must adopt the OpenTelemetry and Tempo distributed tracing stack because it is the stack to be enhanced going forward.
115+
116+
In the {DTProductName} 3.3, the Jaeger agent is deprecated and planned to be removed in the following release.
117+
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.
118+
The OpenTelemetry Collector provided by the {OTELName} is the preferred Operator for injecting the trace collector agent.
119+
120+
////
121+
[id="distr-tracing_3-3_jaeger-release-notes_removal-notice_{context}"]
122+
==== Removal notice
123+
124+
In the {JaegerName} 3.3, 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.
125+
////
126+
127+
////
128+
[id="distr-tracing_3-3_jaeger-release-notes_bug-fixes_{context}"]
129+
==== Bug fixes
130+
131+
This update introduces the following bug fixes:
132+
133+
* Before this update, ???. With this update, ???. (link:https://issues.redhat.com/browse/TRACING-????/[TRACING-????])
134+
////
135+
136+
[id="distr-tracing_3-3_jaeger-release-notes_known-issues_{context}"]
137+
==== Known issues
138+
139+
There are currently known issues:
140+
141+
* Currently, Apache Spark is not supported.
142+
143+
ifndef::openshift-rosa[]
144+
145+
* Currently, the streaming deployment via AMQ/Kafka is not supported on the {ibm-z-title} and {ibm-power-title} architectures.
146+
endif::openshift-rosa[]
147+
15148
[id="distr-tracing_3-2-2_{context}"]
16149
== Release notes for {DTProductName} 3.2.2
17150

‎observability/otel/otel-rn.adoc

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,77 @@ toc::[]
88

99
include::modules/otel-product-overview.adoc[leveloffset=+1]
1010

11+
You can use the {OTELName} xref:otel-forwarding.adoc#otel-forwarding-traces[in combination with] the xref:../distr_tracing/distr-tracing-rn.adoc#distr-tracing-rn[{TempoName}].
12+
1113
include::snippets/distr-tracing-and-otel-disclaimer-about-docs-for-supported-features-only.adoc[]
1214

15+
[id="otel_3-3_{context}"]
16+
== Release notes for {OTELName} 3.3
17+
18+
The {OTELName} is provided through the {OTELOperator}.
19+
20+
The {OTELName} 3.3 is based on the open source link:https://opentelemetry.io/docs/collector/[OpenTelemetry] release 0.107.0.
21+
22+
[id="otel_3-3_cves_{context}"]
23+
=== CVEs
24+
25+
This release fixes the following CVEs:
26+
27+
* link:https://access.redhat.com/security/cve/CVE-2024-6104[CVE-2024-6104]
28+
* link:https://access.redhat.com/security/cve/CVE-2024-42368[CVE-2024-42368]
29+
30+
[id="otel_3-3_technology-preview-features_{context}"]
31+
=== Technology Preview features
32+
33+
This update introduces the following Technology Preview features:
34+
35+
* Group-by-attribute processor
36+
* Metrics transform processor
37+
* Routing connector
38+
* Exporting logs to the LokiStack log store
39+
40+
:FeatureName: Each of these features
41+
include::snippets/technology-preview.adoc[leveloffset=+1]
42+
43+
[id="otel_3-3_new-features-and-enhancements_{context}"]
44+
=== New features and enhancements
45+
46+
This update introduces the following enhancements:
47+
48+
* Collector dashboard for the internal Collector metrics and analyzing Collector health and performance. (link:https://issues.redhat.com/browse/TRACING-3768[TRACING-3768])
49+
* Support for automatically reloading certificates in both the OpenTelemetry Collector and instrumentation. (link:https://issues.redhat.com/browse/TRACING-4186[TRACING-4186])
50+
51+
////
52+
[id="otel_3-3_jaeger-release-notes_deprecated-functionality_{context}"]
53+
=== Deprecated functionality
54+
55+
In the {OTELName} 3.3, ???. (link:https://issues.redhat.com/browse/TRACING-????/[TRACING-????])
56+
////
57+
58+
////
59+
[id="otel_3-3_removal-notice_{context}"]
60+
=== Removal notice
61+
62+
In the {OTELName} 3.3, 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.
63+
////
64+
65+
[id="otel_3-3_bug-fixes_{context}"]
66+
=== Bug fixes
67+
68+
This update introduces the following bug fixes:
69+
70+
* Before this update, the `ServiceMonitor` object was failing to scrape operator metrics due to missing permissions for accessing the metrics endpoint. With this update, this issue is fixed by creating the `ServiceMonitor` custom resource when operator monitoring is enabled. (link:https://issues.redhat.com/browse/TRACING-4288[TRACING-4288])
71+
* Before this update, the Collector service and the headless service were both monitoring the same endpoints, which caused duplication of metrics collection and `ServiceMonitor` objects. With this update, this issue is fixed by not creating the headless service. (link:https://issues.redhat.com/browse/OBSDA-773[OBSDA-773])
72+
73+
////
74+
[id="otel_3-3_known-issues_{context}"]
75+
=== Known issues
76+
77+
There are currently known issues:
78+
79+
* ???. (link:https://issues.redhat.com/browse/TRACING-????/[TRACING-????])
80+
////
81+
1382
[id="otel_3-2-2_{context}"]
1483
== Release notes for {OTELName} 3.2.2
1584

0 commit comments

Comments
 (0)