Skip to content

Commit f6af8a7

Browse files
authored
Merge pull request #1 from pavolloffay/distributed-tracing-2.9-tempo-overview
TRACING-3289 | Distributed tracing 2.9 tempo overview
2 parents b933865 + e6d84e5 commit f6af8a7

File tree

2 files changed

+18
-1
lines changed

2 files changed

+18
-1
lines changed

modules/distr-tracing-architecture.adoc

+15
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,21 @@ This module included in the following assemblies:
2525

2626
** *Jaeger Console* – With the {JaegerName} user interface, you can visualize your distributed tracing data. On the Search page, you can find traces and explore details of the spans that make up an individual trace.
2727

28+
* *{TempoName}* - This component is based on the open source link:https://github.com/grafana/tempo/[Grafana Tempo project].
29+
30+
** *Gateway* – The Gateway handles authentication, authorization, and forwarding requests to the Distributor or Query front-end service.
31+
32+
** *Distributor* – The Distributor accepts spans in multiple formats including Jaeger, OpenTelemetry, and Zipkin. It routes spans to Ingesters by hashing the `+traceID+` and using a distributed consistent hash ring.
33+
34+
** *Ingester* – The Ingester batches a trace into blocks, creates bloom filters and indexes, and then flushes it all to the back end.
35+
36+
** *Query Frontend* – The Query Frontend is responsible for sharding the search space for an incoming query. The search query is then sent to the Queriers. The Query Frontend deployment exposes the Jaeger UI through the Tempo Query sidecar.
37+
38+
** *Querier* - The Querier is responsible for finding the requested trace ID in either the Ingesters or the back-end storage. Depending on parameters, it can query the Ingesters and pull Bloom indexes from the back end to search blocks in object storage.
39+
40+
** *Compactor* – The Compactors stream blocks to and from the back-end storage to reduce the total number of blocks.
41+
2842
* *{OTELName}* - This component is based on the open source link:https://opentelemetry.io/[OpenTelemetry project].
2943
3044
** *OpenTelemetry Collector* - The OpenTelemetry Collector is a vendor-agnostic way to receive, process, and export telemetry data. The OpenTelemetry Collector supports open-source observability data formats, for example, Jaeger and Prometheus, sending to one or more open-source or commercial back-ends. The Collector is the default location instrumentation libraries export their telemetry data.
45+

modules/distr-tracing-product-overview.adoc

+3-1
Original file line numberDiff line numberDiff line change
@@ -21,8 +21,10 @@ With {DTShortName} you can perform the following functions:
2121
2222
* Perform root cause analysis
2323
24-
{DTProductName} consists of two main components:
24+
{DTProductName} consists of three components:
2525

2626
* *{JaegerName}* - This component is based on the open source link:https://www.jaegertracing.io/[Jaeger project].
2727
28+
* *{TempoName}* - This component is based on the open source link:https://github.com/grafana/tempo[Grafana Tempo project].
29+
2830
* *{OTELNAME}* - This component is based on the open source link:https://opentelemetry.io/[OpenTelemetry project].

0 commit comments

Comments
 (0)