---
title: Does Langfuse support OpenTelemetry logs, metrics, or span links?
seoTitle: "OpenTelemetry Signals Supported by Langfuse"
description: Langfuse ingests OpenTelemetry traces over OTLP/HTTP. OTel logs and metrics are not ingested, and span links are not displayed.
tags: [observability, opentelemetry, integration]
---

# Does Langfuse support OpenTelemetry logs, metrics, or span links?

Langfuse ingests **traces only**, at `/api/public/otel/v1/traces` over OTLP/HTTP with protobuf or JSON payloads. gRPC is not supported.

| Signal                             | Supported                                                                                               |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Traces (spans, attributes, events) | Yes                                                                                                     |
| Metrics                            | No. `/api/public/otel/v1/metrics` accepts requests so exporters do not fail, but the data is discarded. |
| Logs                               | No. There is no logs endpoint.                                                                          |
| Span links                         | No. Links on spans are ignored during ingestion and are not shown in the UI.                            |

Any language with an OpenTelemetry SDK, for example Java, Go, or .NET, can send traces to Langfuse with an OTLP/HTTP exporter. To show token usage, cost, and model information, set the attributes described in [OpenTelemetry](/integrations/native/opentelemetry). Langfuse calculates metrics such as cost and latency from the ingested traces; see [Metrics](/docs/metrics/overview).

## Send logs and metrics to ClickStack

For OpenTelemetry logs and metrics, use [ClickStack](https://clickhouse.com/clickstack), the open-source observability stack built on ClickHouse. ClickStack ingests logs, metrics, and traces for operational monitoring, while Langfuse focuses on inspecting, evaluating, and improving your AI application.

Both accept OpenTelemetry, so you can export the same traces to Langfuse and ClickStack and keep sending logs and metrics to ClickStack only. See [Langfuse and ClickStack](/integrations/clickhouse/observability) for the setup.

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/faq/all/opentelemetry-logs-metrics-span-links.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx @langfuse/cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.