From 967b19018698f5366f823228a900a2e3967690c8 Mon Sep 17 00:00:00 2001 From: Ali <115415312+xogoodnow@users.noreply.github.com> Date: Thu, 19 Dec 2024 15:25:50 +0330 Subject: [PATCH 1/2] Update architecture.md Hi, Clarified the querier's role in querying both ingesters and backend storage. Also, Improved grammar and rephrased. --- docs/sources/tempo/operations/architecture.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/sources/tempo/operations/architecture.md b/docs/sources/tempo/operations/architecture.md index ed1bf16c522..193dddcbd48 100644 --- a/docs/sources/tempo/operations/architecture.md +++ b/docs/sources/tempo/operations/architecture.md @@ -53,11 +53,10 @@ Queriers connect to the Query Frontend via a streaming gRPC connection to proces ## Querier The querier is responsible for finding the requested trace id in either the ingesters or the backend storage. Depending on -parameters it will query both the ingesters and pull bloom/indexes from the backend to search blocks in object -storage. +parameters it will query the ingesters for recently ingested traces and it pulls the bloom filters and indexes form the backend storage to efficiently locate the traces within object storage blocks. The querier exposes an HTTP endpoint at: -`GET /querier/api/traces/`, but its not expected to be used directly. +`GET /querier/api/traces/`, but it is not intended for direct use. Queries should be sent to the Query Frontend. From 5a7555e57c75b2754c62f810edbfad7762245fff Mon Sep 17 00:00:00 2001 From: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com> Date: Tue, 7 Jan 2025 10:47:27 -0500 Subject: [PATCH 2/2] Apply suggestions from code review --- docs/sources/tempo/operations/architecture.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/sources/tempo/operations/architecture.md b/docs/sources/tempo/operations/architecture.md index 193dddcbd48..35ec58d1f2f 100644 --- a/docs/sources/tempo/operations/architecture.md +++ b/docs/sources/tempo/operations/architecture.md @@ -52,8 +52,8 @@ Queriers connect to the Query Frontend via a streaming gRPC connection to proces ## Querier -The querier is responsible for finding the requested trace id in either the ingesters or the backend storage. Depending on -parameters it will query the ingesters for recently ingested traces and it pulls the bloom filters and indexes form the backend storage to efficiently locate the traces within object storage blocks. +The querier finds the requested trace ID in either the ingesters or the backend storage. Depending on +parameters, the querier queries the ingesters for recently ingested traces and pulls the bloom filters and indexes from the backend storage to efficiently locate the traces within object storage blocks. The querier exposes an HTTP endpoint at: `GET /querier/api/traces/`, but it is not intended for direct use.