From 0492317099864f59d8c598d08b18d38e6a9c0587 Mon Sep 17 00:00:00 2001 From: AIMikav <619anamika@gmail.com> Date: Sat, 29 Mar 2025 13:02:46 +0000 Subject: [PATCH] fix: update sink name for traces and metrics in LlamaStack 0.1.8 --- docs/source/building_applications/telemetry.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/source/building_applications/telemetry.md b/docs/source/building_applications/telemetry.md index 833117740..4572480cd 100644 --- a/docs/source/building_applications/telemetry.md +++ b/docs/source/building_applications/telemetry.md @@ -45,14 +45,16 @@ Here's an example that sends telemetry signals to all three sink types. Your con - provider_id: meta-reference provider_type: inline::meta-reference config: - sinks: ['console', 'sqlite', 'otel'] - otel_endpoint: "http://localhost:4318/v1/traces" + sinks: ['console', 'sqlite', 'otel_trace', 'otel_metric'] + otel_trace_endpoint: "http://localhost:4318/v1/traces" + otel_metric_endpoint: "http://localhost:4318/v1/metrics" sqlite_db_path: "/path/to/telemetry.db" ``` ### Jaeger to visualize traces -The `otel` sink works with any service compatible with the OpenTelemetry collector. Let's use Jaeger to visualize this data. +The `otel` sink works with any service compatible with the OpenTelemetry collector, traces and metrics has two separate endpoints. +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: