From 4f29f0f3a1335b4941d0e2724cf5f0c1d028db6d Mon Sep 17 00:00:00 2001 From: Ryan Perry Date: Fri, 1 Nov 2024 14:18:22 -0500 Subject: [PATCH 1/7] docs: Update readme with explore traces info --- README.md | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index f96eda63c6f..3c29bb1c194 100644 --- a/README.md +++ b/README.md @@ -8,13 +8,25 @@ Go Report Card

-Grafana Tempo is an open source, easy-to-use and high-scale distributed tracing backend. Tempo is cost-efficient, requiring only object storage to operate, and is deeply integrated with Grafana, Prometheus, and Loki. +Grafana Tempo is an open source, easy-to-use, and high-scale distributed tracing backend. Tempo is cost-efficient, requiring only object storage to operate, and is deeply integrated with Grafana, Prometheus, and Loki. -Tempo is Jaeger, Zipkin, Kafka, OpenCensus and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them and then writes them to Azure, GCS, S3 or local disk. As such, it is robust, cheap and easy to operate! +Tempo is Jaeger, Zipkin, Kafka, OpenCensus, and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them, and then writes them to Azure, GCS, S3, or local disk. As such, it is robust, cheap, and easy to operate! -Tempo implements [TraceQL](https://grafana.com/docs/tempo/latest/traceql/), a traces-first query language inspired by LogQL and PromQL. This query language allows users to very precisely and easily select spans and jump directly to the spans fulfilling the specified conditions: +## Business Value of Distributed Tracing +Distributed tracing helps teams quickly pinpoint performance issues and understand the flow of requests across services. The Explore Traces UI simplifies this process by offering a user-friendly interface to view and analyze trace data, making it easier to identify and resolve issues without needing to write complex queries. -![Tempo data source query editor](https://grafana.com/media/docs/grafana/data-sources/tempo/query-editor/tempo-ds-query-ed-example-v11-a.png) +## Explore Traces UI: A better way to get value from your tracing data +We are excited to introduce the Explore Traces app as part of the Grafana Explore suite. This app provides a queryless and intuitive experience for analyzing tracing data, allowing teams to quickly identify performance issues, latency bottlenecks, and errors without needing to write complex queries or use TraceQL. + +Key Features: +- **Intuitive Trace Analysis**: Spot slow or error-prone traces with easy, point-and-click interactions. +- **RED Metrics Overview**: Use Rate, Errors, and Duration metrics to highlight performance issues. +- **Automated Comparison**: Identify problematic attributes with automatic trace comparison. +- **Simplified Visualizations**: Access rich visual data without needing to construct TraceQL queries. + +![Explore Traces UI](docs/sources/tempo/explore-traces-ui.png) + +Tempo implements [TraceQL](https://grafana.com/docs/tempo/latest/traceql/), a traces-first query language inspired by LogQL and PromQL. These powerful querying capabilities power the Explore Traces UI behind the scense, but can also be used directly. ## Getting started From bc8d3c03d9dcab9747d1384d23f3370f7d89a3cd Mon Sep 17 00:00:00 2001 From: Ryan Perry Date: Fri, 1 Nov 2024 14:30:44 -0500 Subject: [PATCH 2/7] Update README.md --- README.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 3c29bb1c194..9fe4705b069 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ Go Report Card

-Grafana Tempo is an open source, easy-to-use, and high-scale distributed tracing backend. Tempo is cost-efficient, requiring only object storage to operate, and is deeply integrated with Grafana, Prometheus, and Loki. +Grafana Tempo is an open source, easy-to-use, and high-scale distributed tracing backend. Tempo is cost-efficient, requiring only object storage to operate, and is deeply integrated with Grafana, Prometheus, and Loki. It is powered by [TraceQL](https://grafana.com/docs/tempo/latest/traceql/), a traces-first query language inspired by LogQL and PromQL which enables targeted queries or rich UI-driven analyses. Tempo is Jaeger, Zipkin, Kafka, OpenCensus, and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them, and then writes them to Azure, GCS, S3, or local disk. As such, it is robust, cheap, and easy to operate! @@ -16,7 +16,7 @@ Tempo is Jaeger, Zipkin, Kafka, OpenCensus, and OpenTelemetry compatible. It ing Distributed tracing helps teams quickly pinpoint performance issues and understand the flow of requests across services. The Explore Traces UI simplifies this process by offering a user-friendly interface to view and analyze trace data, making it easier to identify and resolve issues without needing to write complex queries. ## Explore Traces UI: A better way to get value from your tracing data -We are excited to introduce the Explore Traces app as part of the Grafana Explore suite. This app provides a queryless and intuitive experience for analyzing tracing data, allowing teams to quickly identify performance issues, latency bottlenecks, and errors without needing to write complex queries or use TraceQL. +We are excited to introduce the [Explore Traces app](https://github.com/grafana/explore-traces) as part of the Grafana Explore suite. This app provides a queryless and intuitive experience for analyzing tracing data, allowing teams to quickly identify performance issues, latency bottlenecks, and errors without needing to write complex queries or use TraceQL. Key Features: - **Intuitive Trace Analysis**: Spot slow or error-prone traces with easy, point-and-click interactions. @@ -24,11 +24,15 @@ Key Features: - **Automated Comparison**: Identify problematic attributes with automatic trace comparison. - **Simplified Visualizations**: Access rich visual data without needing to construct TraceQL queries. -![Explore Traces UI](docs/sources/tempo/explore-traces-ui.png) +![image](https://github.com/user-attachments/assets/991205df-1b27-489f-8ef0-1a05ee158996) -Tempo implements [TraceQL](https://grafana.com/docs/tempo/latest/traceql/), a traces-first query language inspired by LogQL and PromQL. These powerful querying capabilities power the Explore Traces UI behind the scense, but can also be used directly. +To learn more see the following links: +- [Explore Traces repo](https://github.com/grafana/explore-traces) +- [Explore Traces Documentation](https://grafana.com/docs/grafana/latest/explore/simplified-exploration/traces/) +- [Demo video](https://github.com/user-attachments/assets/8103e173-6dcf-4659-b938-7614c8a5b52d +) -## Getting started +## Getting started with Tempo - [Get started documentation](https://grafana.com/docs/tempo/latest/getting-started/) - [Deployment Examples](./example) From 4ec23e2c9de7225dbca5321e9fd2882e10143b3e Mon Sep 17 00:00:00 2001 From: Ryan Perry Date: Mon, 4 Nov 2024 10:01:08 -0600 Subject: [PATCH 3/7] Update README.md Co-authored-by: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com> --- README.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 9fe4705b069..23b9469833b 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,17 @@ Go Report Card

-Grafana Tempo is an open source, easy-to-use, and high-scale distributed tracing backend. Tempo is cost-efficient, requiring only object storage to operate, and is deeply integrated with Grafana, Prometheus, and Loki. It is powered by [TraceQL](https://grafana.com/docs/tempo/latest/traceql/), a traces-first query language inspired by LogQL and PromQL which enables targeted queries or rich UI-driven analyses. +Grafana Tempo is an open source, easy-to-use, and high-scale distributed tracing backend. Tempo is cost-efficient, requiring only object storage to operate, and is deeply integrated with Grafana, Prometheus, and Loki. + +Tempo is Jaeger, Zipkin, Kafka, OpenCensus, and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them, and then writes them to Azure, GCS, S3, or local disk. As such, it is robust, cheap, and easy to operate! + +## TraceQL + +Tempo implements [TraceQL](https://grafana.com/docs/tempo/latest/traceql/), a traces-first query language inspired by LogQL and PromQL, which enables targeted queries or rich UI-driven analyses. + +### TraceQL metrics + +[TraceQL metrics](https://grafana.com/docs/tempo/latest/traceql/metrics-queries/) is an experimental feature in Grafana Tempo that creates metrics from traces. Metric queries extend trace queries by applying a function to trace query results. This powerful feature allows for ad hoc aggregation of any existing TraceQL query by any dimension available in your traces, much in the same way that LogQL metric queries create metrics from logs. Tempo is Jaeger, Zipkin, Kafka, OpenCensus, and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them, and then writes them to Azure, GCS, S3, or local disk. As such, it is robust, cheap, and easy to operate! From 628ee1ea261d395fdc0431345c9bf8eb9a25d171 Mon Sep 17 00:00:00 2001 From: Ryan Perry Date: Mon, 4 Nov 2024 10:01:17 -0600 Subject: [PATCH 4/7] Update README.md Co-authored-by: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 23b9469833b..cce809ecd38 100644 --- a/README.md +++ b/README.md @@ -38,7 +38,7 @@ Key Features: To learn more see the following links: - [Explore Traces repo](https://github.com/grafana/explore-traces) -- [Explore Traces Documentation](https://grafana.com/docs/grafana/latest/explore/simplified-exploration/traces/) +- [Explore Traces documentation](https://grafana.com/docs/grafana/latest/explore/simplified-exploration/traces/) - [Demo video](https://github.com/user-attachments/assets/8103e173-6dcf-4659-b938-7614c8a5b52d ) From eed7b8355c1ee7943a0b5f70378298223622a4f9 Mon Sep 17 00:00:00 2001 From: Ryan Perry Date: Mon, 4 Nov 2024 10:01:32 -0600 Subject: [PATCH 5/7] Update README.md Co-authored-by: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com> --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index cce809ecd38..864e244d363 100644 --- a/README.md +++ b/README.md @@ -22,9 +22,13 @@ Tempo implements [TraceQL](https://grafana.com/docs/tempo/latest/traceql/), a tr Tempo is Jaeger, Zipkin, Kafka, OpenCensus, and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them, and then writes them to Azure, GCS, S3, or local disk. As such, it is robust, cheap, and easy to operate! -## Business Value of Distributed Tracing +## Business value of distributed tracing + Distributed tracing helps teams quickly pinpoint performance issues and understand the flow of requests across services. The Explore Traces UI simplifies this process by offering a user-friendly interface to view and analyze trace data, making it easier to identify and resolve issues without needing to write complex queries. +Refer to [Use traces to find solutions](https://grafana.com/docs/tempo/latest/introduction/solutions-with-traces/)t o learn more about how you can use distributed tracing to investigate and solve issues. + + ## Explore Traces UI: A better way to get value from your tracing data We are excited to introduce the [Explore Traces app](https://github.com/grafana/explore-traces) as part of the Grafana Explore suite. This app provides a queryless and intuitive experience for analyzing tracing data, allowing teams to quickly identify performance issues, latency bottlenecks, and errors without needing to write complex queries or use TraceQL. From 648479212f5680550d47ef20ca519643b91f1872 Mon Sep 17 00:00:00 2001 From: Ryan Perry Date: Mon, 4 Nov 2024 10:03:05 -0600 Subject: [PATCH 6/7] Update README.md --- README.md | 21 ++++++++++----------- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 864e244d363..bf44693d345 100644 --- a/README.md +++ b/README.md @@ -12,23 +12,12 @@ Grafana Tempo is an open source, easy-to-use, and high-scale distributed tracing Tempo is Jaeger, Zipkin, Kafka, OpenCensus, and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them, and then writes them to Azure, GCS, S3, or local disk. As such, it is robust, cheap, and easy to operate! -## TraceQL - -Tempo implements [TraceQL](https://grafana.com/docs/tempo/latest/traceql/), a traces-first query language inspired by LogQL and PromQL, which enables targeted queries or rich UI-driven analyses. - -### TraceQL metrics - -[TraceQL metrics](https://grafana.com/docs/tempo/latest/traceql/metrics-queries/) is an experimental feature in Grafana Tempo that creates metrics from traces. Metric queries extend trace queries by applying a function to trace query results. This powerful feature allows for ad hoc aggregation of any existing TraceQL query by any dimension available in your traces, much in the same way that LogQL metric queries create metrics from logs. - -Tempo is Jaeger, Zipkin, Kafka, OpenCensus, and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them, and then writes them to Azure, GCS, S3, or local disk. As such, it is robust, cheap, and easy to operate! - ## Business value of distributed tracing Distributed tracing helps teams quickly pinpoint performance issues and understand the flow of requests across services. The Explore Traces UI simplifies this process by offering a user-friendly interface to view and analyze trace data, making it easier to identify and resolve issues without needing to write complex queries. Refer to [Use traces to find solutions](https://grafana.com/docs/tempo/latest/introduction/solutions-with-traces/)t o learn more about how you can use distributed tracing to investigate and solve issues. - ## Explore Traces UI: A better way to get value from your tracing data We are excited to introduce the [Explore Traces app](https://github.com/grafana/explore-traces) as part of the Grafana Explore suite. This app provides a queryless and intuitive experience for analyzing tracing data, allowing teams to quickly identify performance issues, latency bottlenecks, and errors without needing to write complex queries or use TraceQL. @@ -46,6 +35,16 @@ To learn more see the following links: - [Demo video](https://github.com/user-attachments/assets/8103e173-6dcf-4659-b938-7614c8a5b52d ) +## TraceQL + +Tempo implements [TraceQL](https://grafana.com/docs/tempo/latest/traceql/), a traces-first query language inspired by LogQL and PromQL, which enables targeted queries or rich UI-driven analyses. + +### TraceQL metrics + +[TraceQL metrics](https://grafana.com/docs/tempo/latest/traceql/metrics-queries/) is an experimental feature in Grafana Tempo that creates metrics from traces. Metric queries extend trace queries by applying a function to trace query results. This powerful feature allows for ad hoc aggregation of any existing TraceQL query by any dimension available in your traces, much in the same way that LogQL metric queries create metrics from logs. + +Tempo is Jaeger, Zipkin, Kafka, OpenCensus, and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them, and then writes them to Azure, GCS, S3, or local disk. As such, it is robust, cheap, and easy to operate! + ## Getting started with Tempo - [Get started documentation](https://grafana.com/docs/tempo/latest/getting-started/) From 22f5feec86b59c70fee7ae17a5f7d03c798dc6c7 Mon Sep 17 00:00:00 2001 From: Kim Nylander <104772500+knylander-grafana@users.noreply.github.com> Date: Mon, 4 Nov 2024 12:48:40 -0500 Subject: [PATCH 7/7] Update README.md --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index bf44693d345..6a0a4b32c69 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,6 @@ Grafana Tempo is an open source, easy-to-use, and high-scale distributed tracing backend. Tempo is cost-efficient, requiring only object storage to operate, and is deeply integrated with Grafana, Prometheus, and Loki. -Tempo is Jaeger, Zipkin, Kafka, OpenCensus, and OpenTelemetry compatible. It ingests batches in any of the mentioned formats, buffers them, and then writes them to Azure, GCS, S3, or local disk. As such, it is robust, cheap, and easy to operate! ## Business value of distributed tracing