docs: add Openlayer to the observability integrations - #975
Open
viniciusdsmello wants to merge 2 commits into
Open
docs: add Openlayer to the observability integrations#975viniciusdsmello wants to merge 2 commits into
viniciusdsmello wants to merge 2 commits into
Conversation
Openlayer is an AI evaluation and observability platform that ingests OTLP/HTTP. LiteLLM gained an `openlayer` callback, so this documents it alongside the other OTLP integrations: a dedicated page under observability, an entry in the vendor preset tabs and the preset table in the OpenTelemetry v2 guide, and a sidebar link. The page notes two things the generic OTLP setup does not cover. The endpoint is a base URL rather than the signal path, because LiteLLM appends `/v1/traces` itself and appends it only once; and the SDK example needs no `LITELLM_OTEL_V2` flag, since without it the callback exports through the v1 OpenTelemetry logger, which covers synchronous calls too. The proxy tab keeps the flag, matching the other presets. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0179aCXUKqsQkF8TRvFQY3t8
viniciusdsmello
marked this pull request as ready for review
August 20, 2026 22:39
Openlayer builds a row's input and output from the root span of the trace. From the SDK the model call is the root, so the prompt and response sit on the row; through the proxy the model call is nested under the gateway request, so the row summarises the request instead. The page claimed the row always carries both, which is wrong for proxy users, verified against real rows on both paths Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0179aCXUKqsQkF8TRvFQY3t8
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the
openlayercallback that BerriAI/litellm#37719 adds. Openlayer is an AI evaluation and observability platform that ingests OTLP/HTTP protobuf, so the integration is a base URL plus two credentials.Three changes: a dedicated page at
docs/observability/openlayer_integration.mdmodelled on the Levo page, since Levo is the closest existing analogue (OTLP with bearer auth plus a routing header); an entry in both the vendor preset tabs and the preset table in the OpenTelemetry v2 guide; and a sidebar link.Two things the page calls out
The endpoint is a base URL rather than the signal path. LiteLLM appends
/v1/tracesitself, on both the v1 and v2 paths, and appends it only once, so the already suffixed spelling resolves to the same URL instead of doubling into/v1/otel/v1/traces/v1/traces. That is the mistake someone hand-writingOTEL_ENDPOINTmakes, so it seemed worth stating rather than leaving to be discovered.The SDK example deliberately sets no
LITELLM_OTEL_V2flag. Without it the callback exports through the v1 OpenTelemetry logger, which covers synchronous calls; the proxy tab keeps the flag, matching how the other presets are documented. Both paths read the same credentials, so they cannot drift.Verification
node scripts/check-writing-style.js docs blog release_notesreports no prose em dashes and no vocabulary warnings in the new or edited files.npm run buildsucceeds; the page renders atbuild/docs/observability/openlayer_integrationand the#span-attributesanchor it links resolves. The broken anchors the build reports are pre-existing in release notes and unrelated.The setup the page describes was run end to end against a live Openlayer pipeline on both the v1 and v2 paths, so the env vars, the endpoint and the header shape are what the code actually sends.
Note
No screenshot tab was added to the "What each backend renders" section of the v2 guide, since each of those embeds an image and there is no Openlayer image in
static/img/observabilityyet. Levo is documented the same way. Happy to add one if you would like it.