From c075d68d20ef2822fcbf3af49dfbc7b6adc76a19 Mon Sep 17 00:00:00 2001 From: axelray-dev Date: Mon, 1 Jun 2026 22:08:00 +0800 Subject: [PATCH 1/4] docs: improve alternative backend and client discoverability Fixes #484 - alternative-backends.md: add keywords for search indexing (self-hosted backend, collector, Jaeger, Grafana Tempo, OTLP-compatible server) - alternative-clients.md: add language examples for search indexing (Node.js, Rust, Go, Ruby, OpenTelemetry SDK) - why.md: replace vague 'cross-language data integration' with explicit links to Alternative Clients and Alternative Backends pages --- docs/how-to-guides/alternative-backends.md | 2 ++ docs/how-to-guides/alternative-clients.md | 2 +- docs/why.md | 2 +- 3 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/how-to-guides/alternative-backends.md b/docs/how-to-guides/alternative-backends.md index 1e0c83a28..87ca09147 100644 --- a/docs/how-to-guides/alternative-backends.md +++ b/docs/how-to-guides/alternative-backends.md @@ -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. + 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. diff --git a/docs/how-to-guides/alternative-clients.md b/docs/how-to-guides/alternative-clients.md index eade16b87..fc1b86cd8 100644 --- a/docs/how-to-guides/alternative-clients.md +++ b/docs/how-to-guides/alternative-clients.md @@ -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 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: diff --git a/docs/why.md b/docs/why.md index 691aa5167..319193055 100644 --- a/docs/why.md +++ b/docs/why.md @@ -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: From ce120f79e6d45403058945fcfaed1f52d392e9ee Mon Sep 17 00:00:00 2001 From: axelray-dev Date: Mon, 1 Jun 2026 22:23:22 +0800 Subject: [PATCH 2/4] docs: remove Node.js and Rust from non-first-class examples These languages have custom first-class SDKs per docs/languages.md. Keep only Go, Ruby, and generic OpenTelemetry SDK languages as examples of languages outside first-class support. --- docs/how-to-guides/alternative-clients.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to-guides/alternative-clients.md b/docs/how-to-guides/alternative-clients.md index fc1b86cd8..69f6339b0 100644 --- a/docs/how-to-guides/alternative-clients.md +++ b/docs/how-to-guides/alternative-clients.md @@ -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) (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 +[first-class supported languages](../languages.md) (e.g., Go, Ruby, or any other language with an OpenTelemetry SDK). Depending on your SDK, you may need to set only 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: From ab8a222b048ee75e1316cd8b74775a02aa80d69c Mon Sep 17 00:00:00 2001 From: axelray-dev <110029405+axelray-dev@users.noreply.github.com> Date: Thu, 4 Jun 2026 01:00:20 +0800 Subject: [PATCH 3/4] docs: remove overlapping alternative-backends sentence, simplify why.md wording --- docs/how-to-guides/alternative-backends.md | 2 -- docs/why.md | 2 +- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/how-to-guides/alternative-backends.md b/docs/how-to-guides/alternative-backends.md index 87ca09147..1e0c83a28 100644 --- a/docs/how-to-guides/alternative-backends.md +++ b/docs/how-to-guides/alternative-backends.md @@ -6,8 +6,6 @@ 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. - 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. diff --git a/docs/why.md b/docs/why.md index 319193055..25569b5b4 100644 --- a/docs/why.md +++ b/docs/why.md @@ -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). 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. +[instrumentation for many common Python packages](https://opentelemetry-python-contrib.readthedocs.io/en/latest/index.html). Logfire also supports [other OpenTelemetry-compatible languages](how-to-guides/alternative-clients.md) and can [export to any OpenTelemetry-compatible backend](how-to-guides/alternative-backends.md). For example, we can instrument a simple FastAPI app with just 2 lines of code: From b1f921647df4d410f151b7f782d43c35de1d87ff Mon Sep 17 00:00:00 2001 From: axelray-dev <110029405+axelray-dev@users.noreply.github.com> Date: Thu, 4 Jun 2026 01:59:52 +0800 Subject: [PATCH 4/4] docs: add concrete language and backend keywords to why.md for search discoverability --- docs/why.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/why.md b/docs/why.md index 25569b5b4..257b09f62 100644 --- a/docs/why.md +++ b/docs/why.md @@ -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 [other OpenTelemetry-compatible languages](how-to-guides/alternative-clients.md) and can [export to any OpenTelemetry-compatible backend](how-to-guides/alternative-backends.md). +[instrumentation for many common Python packages](https://opentelemetry-python-contrib.readthedocs.io/en/latest/index.html). Logfire also works with OpenTelemetry SDKs in languages such as Node.js, Rust, and Go, and can export to backends such as Jaeger or Grafana Tempo. See [Alternative Clients](how-to-guides/alternative-clients.md) and [Alternative Backends](how-to-guides/alternative-backends.md). For example, we can instrument a simple FastAPI app with just 2 lines of code: