Skip to content

Commit 0547537

Browse files
eromanova97eromanova97
authored
Merge pull request #96782 from max-cx/dt+otel-3.7
OBSDOCS-1698: Distributed Tracing and OpenTelemetry release 3.7
2 parents 46bdb97 + 298ce7f commit 0547537

38 files changed

+576
-3043
lines changed

‎_topic_maps/_topic_map.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3222,6 +3222,8 @@ Topics:
32223222
Topics:
32233223
- Name: Release notes for the Red Hat build of OpenTelemetry
32243224
File: otel-rn
3225+
- Name: About the Red Hat build of OpenTelemetry
3226+
File: otel-architecture
32253227
- Name: Installing the Red Hat build of OpenTelemetry
32263228
File: otel-installing
32273229
- Name: Configuring the Collector

‎modules/distr-tracing-product-overview.adoc‎

Lines changed: 0 additions & 22 deletions
This file was deleted.

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

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/distr_tracing/distr-tracing-rn.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="distr-tracing-product-overview_{context}"]
7+
= About this release
8+
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.
10+
11+
[NOTE]
12+
====
13+
Some linked Jira tickets are accessible only with Red Hat credentials.
14+
====

‎modules/distr-tracing-tempo-coo-ui-plugin.adoc‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/distr_tracing/distr-tracing-tempo-configuring.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="distr-tracing-tempo-coo-ui-plugin_{context}"]
7+
= Configuring the UI
8+
9+
You can use the distributed tracing UI plugin of the {coo-first} as the user interface (UI) for the {DTProductName}. For more information about installing and using the distributed tracing UI plugin, see "Distributed tracing UI plugin" in _Cluster Observability Operator_.

‎modules/distr-tracing-tempo-key-concepts-in-distributed-tracing.adoc‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/distr-tracing-architecture.adoc
4+
// * service_mesh/v2x/ossm-architecture.adoc
5+
// * service_mesh/v1x/ossm-architecture.adoc
6+
// * serverless/observability/tracing/serverless-tracing.adoc
7+
8+
:_mod-docs-content-type: CONCEPT
9+
[id="distr-tracing-tempo-key-concepts-in-distributed-tracing_{context}"]
10+
= Key concepts in distributed tracing
11+
12+
Every time a user takes an action in an application, a request is executed by the architecture that may require dozens of different services to participate to produce a response.
13+
{DTProductName} lets you perform distributed tracing, which records the path of a request through various microservices that make up an application.
14+
15+
_Distributed tracing_ is a technique that is used to tie the information about different units of work together — usually executed in different processes or hosts — to understand a whole chain of events in a distributed transaction.
16+
Developers can visualize call flows in large microservice architectures with distributed tracing.
17+
It is valuable for understanding serialization, parallelism, and sources of latency.
18+
19+
{DTProductName} records the execution of individual requests across the whole stack of microservices, and presents them as traces. A _trace_ is a data/execution path through the system. An end-to-end trace consists of one or more spans.
20+
21+
A _span_ represents a logical unit of work in {DTProductName} that has an operation name, the start time of the operation, and the duration, as well as potentially tags and logs. Spans may be nested and ordered to model causal relationships.
22+
23+
As a service owner, you can use distributed tracing to instrument your services to gather insights into your service architecture.
24+
You can use {DTProductName} for monitoring, network profiling, and troubleshooting the interaction between components in modern, cloud-native, microservices-based applications.
25+
26+
With {DTShortName}, you can perform the following functions:
27+
28+
* Monitor distributed transactions
29+
30+
* Optimize performance and latency
31+
32+
* Perform root cause analysis
33+
34+
You can combine {DTShortName} with other relevant components of the {product-title}:
35+
36+
* {OTELName} for forwarding traces to a TempoStack instance
37+
38+
* Distributed tracing UI plugin of the {coo-first}

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

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/distr_tracing/distr-tracing-rn.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="fixed-issues_{context}"]
7+
= Fixed issues
8+
9+
This release fixes the following CVE:
10+
11+
* link:https://access.redhat.com/security/cve/cve-2025-22874[CVE-2025-22874]

‎modules/distr-tracing-tempo-rn-deprecated-features.adoc‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/distr_tracing/distr-tracing-rn.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="deprecated-features_{context}"]
7+
= Deprecated features
8+
9+
None.

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

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/distr_tracing/distr-tracing-rn.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="new-features-and-enhancements_{context}"]
7+
= New features and enhancements
8+
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.

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

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/distr_tracing/distr-tracing-rn.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="known-issues_{context}"]
7+
= Known issues
8+
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]

‎modules/distr-tracing-tempo-rn-removed-features.adoc‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * observability/distr_tracing/distr-tracing-rn.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="removed-features_{context}"]
7+
= Removed features
8+
9+
None.

0 commit comments

Comments
 (0)