You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
== Component versions in the {DTProductName} 3.1.1
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}].
13
12
14
-
[options="header"]
15
-
|===
16
-
|Operator |Component |Version
17
-
18
-
|{TempoName}
19
-
|Tempo
20
-
|2.3.1
21
-
22
-
//for each new release, update the release number in the xref path on the following line
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}].
@@ -90,12 +82,12 @@ In the {DTProductName} 3.1, Jaeger and support for Elasticsearch remain deprecat
90
82
91
83
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.
The {OTELName} is provided through the {OTELOperator}.
15
+
14
16
[id="otel-rn_3-1_new-features-and-enhancements"]
15
17
=== New features and enhancements
16
18
17
19
//plural: `enhancements:`
18
20
This update introduces the following enhancements:
19
21
20
-
* {OTELName} 3.1 is based on link:https://opentelemetry.io/[OpenTelemetry] 0.93.0.
22
+
* {OTELName} 3.1 is based on the open source link:https://opentelemetry.io/[OpenTelemetry] release 0.93.0.
21
23
22
24
* Support for the target allocator in the OpenTelemetry Collector. The target allocator is an optional component of the OpenTelemetry Operator that shards Prometheus receiver scrape targets across the deployed fleet of OpenTelemetry Collector instances. The target allocator provides integration with the Prometheus `PodMonitor` and `ServiceMonitor` custom resources.
23
25
@@ -49,7 +51,7 @@ This update introduces the following bug fixes:
49
51
50
52
This update introduces the following enhancements:
51
53
52
-
* {OTELName} 3.0 is based on link:https://opentelemetry.io/[OpenTelemetry] 0.89.0.
54
+
* {OTELName} 3.0 is based on the open source link:https://opentelemetry.io/[OpenTelemetry] release 0.89.0.
53
55
* The *OpenShift distributed tracing data collection Operator* is renamed as the *{OTELOperator}*.
54
56
* Support for the ARM architecture.
55
57
* Support for the Prometheus receiver for metrics collection.
{OTELName} 2.0 is based on link:https://opentelemetry.io/[OpenTelemetry] 0.33.0.
420
+
{OTELName} 2.0 is based on the open source link:https://opentelemetry.io/[OpenTelemetry] release 0.33.0.
419
421
420
422
This release adds the {OTELName} as a link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview], which you install using the {OTELName} Operator. {OTELName} is based on the link:https://opentelemetry.io/[OpenTelemetry] APIs and instrumentation. The {OTELName} includes the OpenTelemetry Operator and Collector. You can use the Collector to receive traces in the OpenTelemetry or Jaeger protocol and send the trace data to the {OTELName}. Other capabilities of the Collector are not supported at this time. The OpenTelemetry Collector allows developers to instrument their code with vendor agnostic APIs, avoiding vendor lock-in and enabling a growing ecosystem of observability tooling.
0 commit comments