Skip to content

docs: improve alternative backend and client discoverability #1985

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
axelray-dev wants to merge 2 commits into
base: main
Choose a base branch
from
+4 −2
Open

docs: improve alternative backend and client discoverability #1985

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f739c82
docs: improve alternative backend and client discoverability
axelray-dev Jun 1, 2026
204845c
docs: remove Node.js and Rust from non-first-class examples
axelray-dev Jun 1, 2026
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
2 changes: 2 additions & 0 deletions docs/how-to-guides/alternative-backends.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ description: Learn how to connect Logfire to any backend that supports OpenTelem

**Logfire** uses the OpenTelemetry standard. This means that you can configure the SDK to export to any backend that supports OpenTelemetry.

This is useful when you want to send telemetry to a self-hosted backend or collector, such as Jaeger, Grafana Tempo, or any other OTLP-compatible server.
Comment on lines 7 to +9
Copy link
Copy Markdown
Collaborator

@alexmojaki alexmojaki Jun 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these two lines overlap too much. if this PR is AI generated, please give it a human review.


The easiest way is to set the `OTEL_EXPORTER_OTLP_ENDPOINT` environment variable to a URL that points to your backend.
This will be used as a base, and the SDK will append `/v1/traces` and `/v1/metrics` to the URL to send traces and metrics, respectively.

Expand Down
2 changes: 1 addition & 1 deletion docs/how-to-guides/alternative-clients.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: "Guide on how to use the standard OpenTelemetry SDK to export Node.

**Logfire** uses the OpenTelemetry standard. This means that you can configure standard OpenTelemetry SDKs
in many languages to export to the **Logfire** backend, including those outside our
[first-class supported languages](../languages.md). Depending on your SDK, you may need to set only
[first-class supported languages](../languages.md) (e.g., Node.js, Rust, Go, Ruby, or any other language with an OpenTelemetry SDK). Depending on your SDK, you may need to set only
Comment thread
cubic-dev-ai[bot] marked this conversation as resolved.
Outdated
these [environment variables](https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/):

- `OTEL_EXPORTER_OTLP_ENDPOINT=https://logfire-us.pydantic.dev` for both traces and metrics, or:
Expand Down
2 changes: 1 addition & 1 deletion docs/why.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,7 +170,7 @@ Learn more about the [Pydantic Plugin here](integrations/pydantic.md).

Because **Pydantic Logfire** is built on [OpenTelemetry](https://opentelemetry.io/), you can
use a wealth of existing tooling and infrastructure, including
[instrumentation for many common Python packages](https://opentelemetry-python-contrib.readthedocs.io/en/latest/index.html). Logfire also supports cross-language data integration and data export to any OpenTelemetry-compatible backend or proxy.
[instrumentation for many common Python packages](https://opentelemetry-python-contrib.readthedocs.io/en/latest/index.html). You can also use Logfire with any other OpenTelemetry-compatible language — see [Alternative Clients](how-to-guides/alternative-clients.md) for examples with Node.js, Rust, and Go — or [export to any OpenTelemetry-compatible backend](how-to-guides/alternative-backends.md) such as Jaeger or Grafana Tempo.

For example, we can instrument a simple FastAPI app with just 2 lines of code:

Expand Down
Loading