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
Where telemetry is sent
Telemetry is sent to Langfuse's telemetry pipeline via PostHog Cloud.
Implementation reference: Telemetry job
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 |
assistantRuns | Total Langfuse Assistant runs started in the reporting window | Postgres |
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.
Container image downloads
Our deployment templates — the docker-compose.yml file and the 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. 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:
- Check out Troubleshooting & FAQ page.
- Use Ask AI to get instant answers to your questions.
- Ask the maintainers on GitHub Discussions.
- Create a bug report or feature request on GitHub.
Enterprise-grade support is available when self-hosting Langfuse. Learn more on our pricing page.
Last updated on
