From 9497cc3e431c4d219d4d4c846765d024c7c0af59 Mon Sep 17 00:00:00 2001 From: Dinesh Yeduguru Date: Thu, 5 Dec 2024 21:13:29 -0800 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Adrian Cole <64215+codefromthecrypt@users.noreply.github.com> --- docs/source/experimental/telemetry/index.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/source/experimental/telemetry/index.md b/docs/source/experimental/telemetry/index.md index a83f7583c..a95fb6859 100644 --- a/docs/source/experimental/telemetry/index.md +++ b/docs/source/experimental/telemetry/index.md @@ -85,6 +85,7 @@ Currently, only the meta-reference provider is implemented. It can be configured ## Configuration +Here's an example that sends telemetry signals to all three sink types. Your configuration might use only one. ```yaml telemetry: - provider_id: meta-reference @@ -96,6 +97,9 @@ Currently, only the meta-reference provider is implemented. It can be configured ``` ## Jaeger to visualize traces + +The `otel` sink works with any service compatible with the OpenTelemetry collector. Let's use Jaeger to visualize this data. + Start a Jaeger instance with the OTLP HTTP endpoint at 4318 and the Jaeger UI at 16686 using the following command: ```bash @@ -113,7 +117,9 @@ docker run -d \ Once the Jaeger instance is running, you can visualize traces by navigating to http://localhost:16686. -## Querying Examples +## Querying Traces Stored in SQLIte + +The `sqlite` sink allows you to query traces without an external system. Here are some example queries: Querying Traces for a agent session