Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions modules/distr-tracing-architecture.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,21 @@ This module included in the following assemblies:

** *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.

* *{TempoName}* - This component is based on the open source link:https://github.com/grafana/tempo/[Grafana Tempo project].

** *Gateway* – The Gateway handles authentication, authorization, and forwarding requests to the Distributor or Query front-end service.

** *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.

** *Ingester* – The Ingester batches a trace into blocks, creates bloom filters and indexes, and then flushes it all to the back end.

** *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.

** *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.

** *Compactor* – The Compactors stream blocks to and from the back-end storage to reduce the total number of blocks.

* *{OTELName}* - This component is based on the open source link:https://opentelemetry.io/[OpenTelemetry project].

** *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.

4 changes: 3 additions & 1 deletion modules/distr-tracing-product-overview.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,10 @@ With {DTShortName} you can perform the following functions:

* Perform root cause analysis

{DTProductName} consists of two main components:
{DTProductName} consists of three components:

* *{JaegerName}* - This component is based on the open source link:https://www.jaegertracing.io/[Jaeger project].

* *{TempoName}* - This component is based on the open source link:https://github.com/grafana/tempo[Grafana Tempo project].

* *{OTELNAME}* - This component is based on the open source link:https://opentelemetry.io/[OpenTelemetry project].