mirror of
https://github.com/meta-llama/llama-stack.git
synced 2025-12-30 13:09:32 +00:00
661985e240
Some checks failed
SqlStore Integration Tests / test-postgres (3.13) (push) Failing after 0s
Integration Auth Tests / test-matrix (oauth2_token) (push) Failing after 1s
Integration Tests (Replay) / generate-matrix (push) Successful in 3s
SqlStore Integration Tests / test-postgres (3.12) (push) Failing after 4s
Test Llama Stack Build / generate-matrix (push) Failing after 3s
Test Llama Stack Build / build (push) Has been skipped
Test External Providers Installed via Module / test-external-providers-from-module (venv) (push) Has been skipped
Test llama stack list-deps / generate-matrix (push) Failing after 3s
Test llama stack list-deps / list-deps (push) Has been skipped
API Conformance Tests / check-schema-compatibility (push) Successful in 11s
Python Package Build Test / build (3.13) (push) Successful in 19s
Python Package Build Test / build (3.12) (push) Successful in 23s
Test Llama Stack Build / build-single-provider (push) Successful in 33s
Test llama stack list-deps / show-single-provider (push) Successful in 36s
Test llama stack list-deps / list-deps-from-config (push) Successful in 44s
Vector IO Integration Tests / test-matrix (push) Failing after 57s
Test External API and Providers / test-external (venv) (push) Failing after 1m37s
Unit Tests / unit-tests (3.12) (push) Failing after 1m56s
UI Tests / ui-tests (22) (push) Successful in 2m2s
Unit Tests / unit-tests (3.13) (push) Failing after 2m35s
Pre-commit / pre-commit (22) (push) Successful in 3m16s
Test Llama Stack Build / build-custom-container-distribution (push) Successful in 3m34s
Test Llama Stack Build / build-ubi9-container-distribution (push) Successful in 3m59s
Integration Tests (Replay) / Integration Tests (, , , client=, ) (push) Failing after 4m30s
# What does this PR do? the build.yaml is only used in the following ways: 1. list-deps 2. distribution code-gen since `llama stack build` no longer exists, I found myself asking "why do we need two different files for list-deps and run"? Removing the BuildConfig and altering the usage of the DistributionTemplate in llama stack list-deps is the first step in removing the build yaml entirely. Removing the BuildConfig and build.yaml cuts the files users need to maintain in half, and allows us to focus on the stability of _just_ the run.yaml This PR removes the build.yaml, BuildConfig datatype, and its usage throughout the codebase. Users are now expected to point to run.yaml files when running list-deps, and our codebase automatically uses these types now for things like `get_provider_registry`. **Additionally, two renames: `StackRunConfig` -> `StackConfig` and `run.yaml` -> `config.yaml`.** The build.yaml made sense for when we were managing the build process for the user and actually _producing_ a run.yaml _from_ the build.yaml, but now that we are simply just getting the provider registry and listing the deps, switching to config.yaml simplifies the scope here greatly. ## Test Plan existing list-deps usage should work in the tests. --------- Signed-off-by: Charlie Doern <cdoern@redhat.com>
43 lines
1.5 KiB
Text
43 lines
1.5 KiB
Text
---
|
|
title: Telemetry
|
|
description: Monitor and observe Llama Stack applications with comprehensive telemetry capabilities
|
|
sidebar_label: Telemetry
|
|
sidebar_position: 8
|
|
---
|
|
|
|
import Tabs from '@theme/Tabs';
|
|
import TabItem from '@theme/TabItem';
|
|
|
|
# Telemetry
|
|
|
|
The preferred way to instrument Llama Stack is with OpenTelemetry. Llama Stack enriches the data
|
|
collected by OpenTelemetry to capture helpful information about the performance and behavior of your
|
|
application. Here is an example of how to forward your telemetry to an OTLP collector from Llama Stack:
|
|
|
|
```sh
|
|
export OTEL_EXPORTER_OTLP_ENDPOINT="http://127.0.0.1:4318"
|
|
export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
|
|
export OTEL_SERVICE_NAME="llama-stack-server"
|
|
|
|
uv pip install opentelemetry-distro opentelemetry-exporter-otlp
|
|
uv run opentelemetry-bootstrap -a requirements | uv pip install --requirement -
|
|
|
|
uv run opentelemetry-instrument llama stack run config.yaml
|
|
```
|
|
|
|
|
|
### Known issues
|
|
|
|
Some database instrumentation libraries have a known bug where spans get wrapped twice, or do not get connected to a trace.
|
|
To prevent this, you can disable database specific tracing, and rely just on the SQLAlchemy tracing. If you are using
|
|
`sqlite3` as your database, for example, you can disable the additional tracing like this:
|
|
|
|
```sh
|
|
export OTEL_PYTHON_DISABLED_INSTRUMENTATIONS="sqlite3"
|
|
```
|
|
|
|
|
|
## Related Resources
|
|
|
|
- **[OpenTelemetry Documentation](https://opentelemetry.io/)** - Comprehensive observability framework
|
|
- **[Jaeger Documentation](https://www.jaegertracing.io/)** - Distributed tracing visualization
|