Skip to content

Commit bd1e016

Browse files
max-cxmax-cx
committed
"OBSDOCS-1699: 3.8 release of Distribute Tracing and OpenTelemetry
This PR publishes the 3.8 release and consolidates the following PRs: #102702 #103126 #102819 #102760 #102804 #102897 Jira: https://issues.redhat.com/browse/OBSDOCS-1699
1 parent c386e6a commit bd1e016

30 files changed

+365
-62
lines changed

‎modules/distr-tracing-tempo-about-rn.adoc‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,12 @@
66
[id="distr-tracing-product-overview_{context}"]
77
= About this release
88

9-
{DTShortName} 3.7 is provided through the link:https://catalog.redhat.com/software/containers/rhosdt/tempo-operator-bundle/642c3e0eacf1b5bdbba7654a/history[{TempoOperator} 0.18.0] and based on the open source link:https://grafana.com/oss/tempo/[Grafana Tempo] 2.8.2.
9+
[role="_abstract"]
10+
{DTShortName} 3.8 is provided through the link:https://catalog.redhat.com/software/containers/rhosdt/tempo-operator-bundle/642c3e0eacf1b5bdbba7654a/history[{TempoOperator} 0.19.0] and based on the open source link:https://grafana.com/oss/tempo/[Grafana Tempo] 2.9.0.
1011

12+
////
1113
[NOTE]
1214
====
1315
Some linked Jira tickets are accessible only with Red Hat credentials.
1416
====
17+
////

‎modules/distr-tracing-tempo-install-web-console.adoc‎

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
[id="distr-tracing-tempo-install-web-console_{context}"]
77
= Installing the {TempoOperator} by using the web console
88

9-
You can install the {TempoOperator} from the *Administrator* view of the web console.
9+
You can install the {TempoOperator} from the {product-title} web console.
1010

1111
.Prerequisites
1212

@@ -23,7 +23,14 @@ Object storage is required and not included with the {TempoShortName}. You must
2323
2424
.Procedure
2525

26-
. Go to *Ecosystem* -> *Software Catalog* and search for `{TempoOperator}`.
26+
. In the web console, search for `{TempoOperator}`.
27+
+
28+
[TIP]
29+
====
30+
In {product-title} 4.19 or earlier, go to *Operators* -> *OperatorHub*.
31+
32+
In {product-title} 4.20 or later, go to *Ecosystem* -> *Software Catalog*.
33+
====
2734

2835
. Select the *{TempoOperator}* that is *provided by Red Hat*.
2936
+

‎modules/distr-tracing-tempo-rn-bug-fixes.adoc‎

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,17 @@
66
[id="fixed-issues_{context}"]
77
= Fixed issues
88

9-
This release fixes the following CVE:
9+
Resolved issue with TLS certificates affecting Tempo pods::
10+
Before this update, the Tempo pods would stop to communicate because internal TLS certificates were renewed. With this update, the Tempo pods automatically restart when certificates are renewed.
11+
+
12+
link:https://issues.redhat.com/browse/TRACING-5622[TRACING-5622]
1013

11-
* link:https://access.redhat.com/security/cve/cve-2025-22874[CVE-2025-22874]
14+
Tempo query frontend no longer fails to fetch trace JSON::
15+
Before this update, clicking on *Trace* in the Jaeger UI and refreshing the page, or accessing *Trace* -> *Trace Timeline* -> *Trace JSON* from the Tempo query frontend, might result in the Tempo query pod failing with an EOF error. With this update, this issue is resolved.
16+
+
17+
link:https://issues.redhat.com/browse/TRACING-5483[TRACING-5483]
18+
19+
[NOTE]
20+
====
21+
Some linked Jira tickets are accessible only with Red Hat credentials.
22+
====

‎modules/distr-tracing-tempo-rn-enhancements.adoc‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,5 +6,4 @@
66
[id="new-features-and-enhancements_{context}"]
77
= New features and enhancements
88

9-
Network policy to restrict API access::
10-
With this update, the {TempoOperator} creates a network policy for the Operator to restrict access to the used APIs.
9+
None.

‎modules/distr-tracing-tempo-rn-known-issues.adoc‎

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,11 @@
66
[id="known-issues_{context}"]
77
= Known issues
88

9-
Tempo query frontend fails to fetch trace JSON::
10-
In the Jaeger UI, clicking on *Trace* and refreshing the page, or accessing *Trace* -> *Trace Timeline* -> *Trace JSON* from the Tempo query frontend, might result in the Tempo query pod failing with an EOF error.
11-
+
12-
To work around this problem, use the distributed tracing UI plugin to view traces.
13-
+
14-
link:https://issues.redhat.com/browse/TRACING-5483[TRACING-5483]
9+
None.
10+
11+
////
12+
[NOTE]
13+
====
14+
Some linked Jira tickets are accessible only with Red Hat credentials.
15+
====
16+
////

‎modules/distr-tracing-tempo-rn-technology-preview-features.adoc‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,5 +8,13 @@
88

99
None.
1010

11+
[IMPORTANT]
12+
====
13+
[subs="attributes+"]
14+
Technology Preview features are not supported with Red{nbsp}Hat production service level agreements (SLAs) and might not be functionally complete. Red{nbsp}Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
15+
16+
For more information about the support scope of Red{nbsp}Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
17+
====
18+
1119
//:FeatureName: Each of these features
1220
//include::snippets/technology-preview.adoc[leveloffset=+1]

‎modules/otel-about-rn.adoc‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,12 @@
66
[id="otel-product-overview_{context}"]
77
= About this release
88

9-
{OTELName} 3.7 is provided through the link:https://catalog.redhat.com/software/containers/rhosdt/opentelemetry-operator-bundle/615618406feffc5384e84400/history[{OTELOperator} 0.135.0] and based on the open source link:https://opentelemetry.io/docs/collector/[OpenTelemetry] release 0.135.0.
9+
[role="_abstract"]
10+
{OTELName} 3.8 is provided through the link:https://catalog.redhat.com/software/containers/rhosdt/opentelemetry-operator-bundle/615618406feffc5384e84400/history[{OTELOperator} 0.140.0] and based on the open source link:https://opentelemetry.io/docs/collector/[OpenTelemetry] release 0.140.0.
1011

12+
////
1113
[NOTE]
1214
====
1315
Some linked Jira tickets are accessible only with Red Hat credentials.
1416
====
17+
////

‎modules/otel-collector-config-options.adoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
// Module included in the following assemblies:
22
//
3-
// * observability/otel/otel-configuration-of-otel-collector.adoc
3+
// * observability/otel/otel-configuration-of-otel-intro.adoc
44

55
:_mod-docs-content-type: REFERENCE
66
[id="otel-collector-config-options_{context}"]

‎modules/otel-collector-profile-signal.adoc‎

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/otel/otel-configuration-of-otel-intro.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="otel-collector-profile-signal_{context}"]
7+
= Profile signal
8+
9+
[role="_abstract"]
10+
The Profile signal is an emerging telemetry data format for observing code execution and resource consumption.
11+
12+
:FeatureName: The Profile signal
13+
include::snippets/technology-preview.adoc[leveloffset=+1]
14+
15+
The Profile signal allows you to pinpoint inefficient code down to specific functions. Such profiling allows you to precisely identify performance bottlenecks and resource inefficiencies down to the specific line of code. By correlating such high-fidelity profile data with traces, metrics, and logs, it enables comprehensive performance analysis and targeted code optimization in production environments.
16+
17+
Profiling can target an application or operating system:
18+
19+
* Using profiling to observe an application can help developers validate code performance, prevent regressions, and monitor resource consumption such as memory and CPU usage, and thus identify and improve inefficient code.
20+
21+
* Using profiling to observe operating systems can provide insights into the infrastructure, system calls, kernel operations, and I/O wait times, and thus help in optimizing infrastructure for efficiency and cost savings.
22+
23+
.OpenTelemetry Collector custom resource with the enabled Profile signal
24+
[source,yaml]
25+
----
26+
apiVersion: opentelemetry.io/v1beta1
27+
kind: OpenTelemetryCollector
28+
metadata:
29+
name: otel-profiles-collector
30+
namespace: otel-profile
31+
spec:
32+
args:
33+
feature-gates: service.profilesSupport # <1>
34+
config:
35+
receivers:
36+
otlp: # <2>
37+
protocols:
38+
grpc:
39+
endpoint: '0.0.0.0:4317'
40+
http:
41+
endpoint: '0.0.0.0:4318'
42+
exporters:
43+
otlp/pyroscope:
44+
endpoint: "pyroscope.pyroscope-monitoring.svc.cluster.local:4317" # <3>
45+
service:
46+
pipelines: # <4>
47+
profiles:
48+
receivers: [otlp]
49+
exporters: [otlp/pyroscope]
50+
# ...
51+
----
52+
<1> Enables profiles by setting the `feature-gates` field as shown here.
53+
<2> Configures the OTLP Receiver to set up the OpenTelemetry Collector to receive profile data via the OTLP.
54+
<3> Configures where to export profiles to, such as a storage.
55+
<4> Defines a profiling pipeline, including a configuration for forwarding the received profile data to an OTLP-compatible profiling back end such as Grafana Pyroscope.
56+
57+
[role="_additional-resources"]
58+
.Additional resources
59+
* link:https://opentelemetry.io/docs/specs/otel/profiles/[OpenTelemetry Profiles]
60+
* link:https://opentelemetry.io/docs/specs/semconv/general/profiles/[Profiles attributes]

‎modules/otel-creating-required-RBAC-resources-automatically.adoc‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
// Module included in the following assemblies:
22
//
3-
// * observability/otel/otel-configuration-of-otel-collector.adoc
3+
// * observability/otel/otel-configuration-of-otel-intro.adoc
44

55
:_mod-docs-content-type: PROCEDURE
66
[id="otel-creating-required-RBAC-resources-automatically_{context}"]

0 commit comments

Comments
 (0)