--- title: Telemetry (self-hosted) sidebarTitle: Telemetry description: Learn what telemetry Langfuse sends from self-hosted deployments, why it is collected, and when it can be disabled. label: "Version: v4" --- # Telemetry Langfuse self-hosted sends a small amount of deployment telemetry to Langfuse. For Langfuse Enterprise (self-hosted), this telemetry is used for license compliance and to understand license usage at a high level. For Langfuse OSS, the same telemetry helps us understand adoption and prioritize improvements and roadmap items. Langfuse does not send raw traces, prompts, observations, scores, or dataset contents from your self-hosted deployment. Only high-level aggregated usage metrics are shared. ## Application telemetry [#application-telemetry] ### Where telemetry is sent Telemetry is sent to Langfuse's telemetry pipeline via PostHog Cloud. Implementation reference: [Telemetry job](https://github.com/langfuse/langfuse/blob/main/web/src/features/telemetry/index.ts) ### What is sent Langfuse calculates these values locally and sends a single telemetry event. All metrics are aggregated across all projects of the instance before they are sent. Langfuse does not send raw ClickHouse rows or per-project breakdowns. | Field | Meaning | Source | | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -------------------------- | | `langfuseVersion` | The running Langfuse version | Application metadata | | `eeLicenseKey` | The configured `LANGFUSE_EE_LICENSE_KEY`, if present | Environment variable | | `userDomains` | Up to 30 email domains from the local `users` table with user counts. Raw email addresses are not sent as they are considered PII. | Postgres | | `totalProjects` | Current number of non-deleted projects | Postgres | | `traces` | Total traces created in the reporting window | Local ClickHouse aggregate | | `scores` | Total scores created in the reporting window | Local ClickHouse aggregate | | `observations` | Total observations created in the reporting window | Local ClickHouse aggregate | | `datasets` | Total datasets created in the reporting window | Postgres | | `datasetItems` | Total dataset items created in the reporting window | Postgres | | `datasetRuns` | Total dataset runs created in the reporting window | Postgres | | `datasetRunItems` | Total dataset run items created in the reporting window | Local ClickHouse aggregate | | `startTimeframe` / `endTimeframe` | The reporting window used for the counts above | Application metadata | ## Can I disable telemetry? ### Langfuse OSS Yes. Set `TELEMETRY_ENABLED=false` on all Langfuse application containers. ### Langfuse Enterprise (self-hosted) Enterprise self-hosted telemetry is used for license compliance and cannot be disabled. If you have procurement, network, or privacy questions, please [contact us](/support). ### Container image downloads [#container-image-downloads] Our deployment templates — the [`docker-compose.yml`](https://github.com/langfuse/langfuse/blob/main/docker-compose.yml) file and the [`langfuse-k8s`](https://github.com/langfuse/langfuse-k8s) Helm chart — reference the Langfuse application images as `docker.langfuse.com/langfuse/langfuse` and `docker.langfuse.com/langfuse/langfuse-worker`. `docker.langfuse.com` is a registry endpoint used to measure open source adoption via [Reo.dev](https://reo.dev). Only the pull is observed — no data from your running Langfuse instance is involved, and the endpoint is contacted only when you fetch an image. You can also pull the images directly from Docker Hub. Replace `docker.langfuse.com/langfuse/...` with `langfuse/...` (or the fully qualified `docker.io/langfuse/...`) wherever the image is referenced. --- If you experience any issues when self-hosting Langfuse, please: 1. Check out [Troubleshooting & FAQ](/self-hosting/troubleshooting-and-faq) page. 2. Use [Ask AI](/ask-ai) to get instant answers to your questions. 3. Ask the maintainers on [GitHub Discussions](/gh-support). 4. Create a bug report or feature request on [GitHub](/issues). Enterprise-grade support is available when self-hosting Langfuse. Learn more on our [pricing page](/pricing-self-host). --- ## 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/self-hosting/security/telemetry.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**: , 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 `) to read or write traces, prompts, datasets, and scores from the terminal. Found an error in these docs? Please open an issue at .