Skip to content

docs(otel v2): presets export only to their own backend, add otel for a generic collector #1447

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
devin-ai-integration wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(otel v2): presets export only to their own backend, add otel for a generic collector #1447

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/observability/opentelemetry_v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,6 +236,13 @@ litellm_settings:

Each preset adds its own destination, so your spans reach all of them in parallel, each in that tool's native format.

A preset exports only to its own backend. To also send plain `gen_ai.*` spans to your own OTLP collector, list `otel` next to the presets and set the `OTEL_*` env vars; a preset on its own ignores them, so vendor vocabulary such as `langfuse.*` or OpenInference never lands on your collector.

```yaml title="config.yaml"
litellm_settings:
callbacks: ["otel", "langfuse_otel"]
```

:::

### Preset reference
Expand Down
Loading