phoenix-oss/llama-stack-mirror
0
0
Fork 1
mirror of https://github.com/meta-llama/llama-stack.git synced 2025-08-02 08:44:44 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix Jaeger instructions

Browse source 
Signed-off-by: Yuri Shkuro <github@ysh.us>
This commit is contained in:
Yuri Shkuro 2024-12-07 14:07:41 -05:00
parent b3cb8eaa38
commit 09a0014910
1 changed files with 5 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/source/building_applications/telemetry.md
View file

@ -40,7 +40,7 @@ structured_log_event = SpanStartPayload(
- **Traces**: Collection of related spans forming a complete request flow - **Traces**: Collection of related spans forming a complete request flow
### Sinks ### Sinks
- **OpenTelemetry**: Send events to an OpenTelemetry Collector. This is useful for visualizing traces in a service like Jaeger. - **OpenTelemetry**: Send events to an OpenTelemetry Collector. This is useful for visualizing traces in a tool like Jaeger.
- **SQLite**: Store events in a local SQLite database. This is needed if you want to query the events later through the Llama Stack API. - **SQLite**: Store events in a local SQLite database. This is needed if you want to query the events later through the Llama Stack API.
- **Console**: Print events to the console. - **Console**: Print events to the console.
@ -124,13 +124,12 @@ The `otel` sink works with any service compatible with the OpenTelemetry collect
Start a Jaeger instance with the OTLP HTTP endpoint at 4318 and the Jaeger UI at 16686 using the following command: Start a Jaeger instance with the OTLP HTTP endpoint at 4318 and the Jaeger UI at 16686 using the following command:
```bash ```bash
$ docker run --rm \ $ docker run --rm --name jaeger \
--name jaeger jaegertracing/jaeger:2.0.0 \ -p 16686:16686 -p 4318:4318 \
-p 16686:16686 -p 4318:4318 \ jaegertracing/jaeger:2.1.0
--set receivers.otlp.protocols.http.endpoint=0.0.0.0:4318
``` ```
Once the Jaeger instance is running, you can visualize traces by navigating to http://localhost:16686. Once the Jaeger instance is running, you can visualize traces by navigating to http://localhost:16686/.
## Querying Traces Stored in SQLIte ## Querying Traces Stored in SQLIte