We value your privacy We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies. CustomiseReject AllAccept All Customise Consent Preferences We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below. The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... Show more NecessaryAlways Active Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data. - Cookie \_\_Secure-next-auth.csrf-token.EU - Duration session - Description Description is currently not available. - Cookie \_\_Secure-next-auth.callback-url.EU - Duration session - Description Description is currently not available. - Cookie \_\_Secure-next-auth.csrf-token.US - Duration session - Description Description is currently not available. - Cookie \_\_Secure-next-auth.callback-url.US - Duration session - Description Description is currently not available. - Cookie \_\_cf\_bm - Duration 1 hour - Description This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. - Cookie \_\_hssrc - Duration session - Description This cookie is set by Hubspot whenever it changes the session cookie. The \_\_hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. - Cookie \_\_hssc - Duration 1 hour - Description HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the \_\_hstc cookie. - Cookie \_\_Secure-next-auth.csrf-token.HIPAA - Duration session - Description Description is currently not available. - Cookie \_\_Secure-next-auth.callback-url.HIPAA - Duration session - Description Description is currently not available. - Cookie \_\_Secure-next-auth.csrf-token.JP - Duration session - Description Description is currently not available. - Cookie \_\_Secure-next-auth.callback-url.JP - Duration session - Description Description is currently not available. - Cookie theme - Duration Never Expires - Description No description available. - Cookie cookietest - Duration session - Description The cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience. - Cookie cookieyes-\* - Duration 1 year - Description CookieYes sets this cookie for consent solution management. Functional Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features. - Cookie inkeepUsagePreferences\_userId - Duration 1 year - Description Description is currently not available. - Cookie \_octo - Duration 1 year - Description No description available. - Cookie logged\_in - Duration 1 year - Description No description available. Analytics Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc. - Cookie ph\_phc\_zkMwFajk8ehObUlMth0D7DtPItFnxETi3lmSvyQDrwB\_posthog - Duration 1 year - Description Description is currently not available. - Cookie \_\_hstc - Duration 6 months - Description Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). - Cookie hubspotutk - Duration 6 months - Description HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. - Cookie \_gh\_sess - Duration session - Description GitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form. - Cookie signals-sdk-user-id - Duration 1 year - Description Description is currently not available. - Cookie signals-sdk-session-id - Duration 1 hour - Description Description is currently not available. Performance Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors. No cookies to display. Advertisement Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns. No cookies to display. Uncategorised Other uncategorised cookies are those that are being analysed and have not been classified into a category as yet. No cookies to display. Reject AllSave My PreferencesAccept All [Langfuse v4: up to 165× faster ·Read moreLangfuse v4 is here: real-time, up to 165× faster ·Read more](/content/changelog/2026-08-17-langfuse-v4/index.html) Self HostingDeployment Guide [Self Hosting](/content/self-hosting/index.html) [Legacy Docs (v2)](/content/self-hosting/v2/index.html) [Deployment Guide](/content/self-hosting/v2/deployment-guide/index.html) Version: v2 Copy page # [Deployment Guide (v2)](/content/self-hosting/v2/deployment-guide\#deployment-guide-v2/index.html) This guide covers Langfuse v2. For Langfuse v3, see the [v3\\ documentation](/content/self-hosting/index.html). Langfuse v2 receives security updates until end of Q1 2025. If you have any questions while upgrading, please refer to the [v3 upgrade guide](/content/self-hosting/upgrade/upgrade-guides/upgrade-v2-to-v3/index.html) or open a thread on [GitHub Discussions](/content/gh-support/index.html). Langfuse Server, which includes the API and Web UI, is open-source and can be self-hosted using Docker. For a detailed component and architecture diagram, refer to [CONTRIBUTING.md](https://github.com/langfuse/langfuse/blob/main/CONTRIBUTING.md). Looking for a managed solution? Consider [Langfuse\\ Cloud](https://cloud.langfuse.com/) maintained by the Langfuse team. ## [Prerequisites: Postgres Database](/content/self-hosting/v2/deployment-guide\#prerequisites-postgres-database/index.html) Langfuse requires a persistent Postgres database to store its state. You can use a managed service on AWS, Azure, or GCP, or host it yourself. Once the database is ready, keep the connection string handy. At least version 12 is required. ## [Deploying the Application](/content/self-hosting/v2/deployment-guide\#deploying-the-application/index.html) Deploy the application container to your infrastructure. You can use managed services like AWS ECS, Azure Container Instances, or GCP Cloud Run, or host it yourself. During the container startup, all database migrations will be applied automatically. This can be optionally disabled via environment variables. ``` docker pull langfuse/langfuse:2 ``` ``` docker run --name langfuse \ -e DATABASE_URL=postgresql://hello \ -e NEXTAUTH_URL=http://localhost:3000 \ -e NEXTAUTH_SECRET=mysecret \ -e SALT=mysalt \ -e ENCRYPTION_KEY=0000000000000000000000000000000000000000000000000000000000000000 \ # generate via: openssl rand -hex 32 -p 3000:3000 \ -a STDOUT \ langfuse/langfuse ``` We follow _semantic versioning_ for Langfuse releases, i.e. breaking changes are only introduced in a new major version. - We recommend [automated updates](/content/self-hosting/v2/deployment-guide#update/index.html) within a major version to benefit from the latest features, bug fixes, and security patches (`docker pull langfuse/langfuse:2`). - Subscribe to our mailing list to get notified about new releases and new major versions. Subscribe ### [Recommended Instance Size](/content/self-hosting/v2/deployment-guide\#recommended-instance-size/index.html) For production environments, we suggest using a configuration of 2 CPU cores and 3 GB of RAM for the Langfuse container. On AWS, this would equate to a `t3.medium` instance. The container is stateless, allowing you to autoscale it based on actual resource usage. ### [Configuring Environment Variables](/content/self-hosting/v2/deployment-guide\#configuring-environment-variables/index.html) Langfuse can be configured using environment variables ( [.env.prod.example](https://github.com/langfuse/langfuse/blob/main/.env.prod.example)). Some are mandatory as defined in the table below: | Variable | Required / Default | Description | | --- | --- | --- | | `DATABASE_URL` | Required | Connection string of your Postgres database. Instead of `DATABASE_URL`, you can also use `DATABASE_HOST`, `DATABASE_USERNAME`, `DATABASE_PASSWORD` and `DATABASE_NAME`. | | `DIRECT_URL` | `DATABASE_URL` | Connection string of your Postgres database used for database migrations. Use this if you want to use a different user for migrations or use connection pooling on `DATABASE_URL`. **For large deployments**, configure the database user with long timeouts as migrations might need a while to complete. | | `SHADOW_DATABASE_URL` | | If your database user lacks the `CREATE DATABASE` permission, you must create a shadow database and configure the "SHADOW\_DATABASE\_URL". This is often the case if you use a Cloud database. Refer to the [Prisma docs](https://www.prisma.io/docs/orm/prisma-migrate/understanding-prisma-migrate/shadow-database#cloud-hosted-shadow-databases-must-be-created-manually) for detailed instructions. | | `NEXTAUTH_URL` | Required | URL of your deployment, e.g. `https://yourdomain.com` or `http://localhost:3000`. Required for successful authentication via OAUTH. | | `NEXTAUTH_SECRET` | Required | Used to validate login session cookies, generate secret with at least 256 entropy using `openssl rand -base64 32`. | | `SALT` | Required | Used to salt hashed API keys, generate secret with at least 256 entropy using `openssl rand -base64 32`. | | `ENCRYPTION_KEY` | Required | Used to encrypt sensitive data. Must be 256 bits, 64 string characters in hex format, generate via: `openssl rand -hex 32`. | | `LANGFUSE_CSP_ENFORCE_HTTPS` | `false` | Set to `true` to set CSP headers to only allow HTTPS connections. | | `PORT` | `3000` | Port the server listens on. | | `HOSTNAME` | `localhost` | In some environments it needs to be set to `0.0.0.0` to be accessible from outside the container (e.g. Google Cloud Run). | | `LANGFUSE_DEFAULT_ORG_ID` | | Configure optional default organization for new users. When users create an account they will be automatically added to this organization. | | `LANGFUSE_DEFAULT_ORG_ROLE` | `VIEWER` | Role of the user in the default organization (if set). Possible values are `OWNER`, `ADMIN`, `MEMBER`, `VIEWER`. See [roles](/content/docs/rbac/index.html) for details. | | `LANGFUSE_DEFAULT_PROJECT_ID` | | Configure optional default project for new users. When users create an account they will be automatically added to this project. | | `LANGFUSE_DEFAULT_PROJECT_ROLE` | `VIEWER` | Role of the user in the default project (if set). Possible values are `OWNER`, `ADMIN`, `MEMBER`, `VIEWER`. See [roles](/content/docs/rbac/index.html) for details. | | `SMTP_CONNECTION_URL` | | Configure optional SMTP server connection for transactional email. Connection URL is passed to Nodemailer ( [docs](https://nodemailer.com/smtp)). | | `EMAIL_FROM_ADDRESS` | | Configure from address for transactional email. Required if `SMTP_CONNECTION_URL` is set. | | `S3_ENDPOINT`
`S3_ACCESS_KEY_ID`
`S3_SECRET_ACCESS_KEY`
`S3_BUCKET_NAME`
`S3_REGION` | | Optional S3 configuration for enabling large exports from the UI. `S3_BUCKET_NAME` is required to enable exports. The other variables are optional and will use the default provider credential chain if not specified. | | `LANGFUSE_S3_MEDIA_UPLOAD_ENABLED`
`LANGFUSE_S3_MEDIA_UPLOAD_BUCKET`
`LANGFUSE_S3_MEDIA_UPLOAD_REGION`
`LANGFUSE_S3_MEDIA_UPLOAD_ACCESS_KEY_ID`
`LANGFUSE_S3_MEDIA_UPLOAD_SECRET_ACCESS_KEY`
`LANGFUSE_S3_MEDIA_UPLOAD_ENDPOINT`
`LANGFUSE_S3_MEDIA_UPLOAD_FORCE_PATH_STYLE`
`LANGFUSE_S3_MEDIA_UPLOAD_PREFIX`
`LANGFUSE_S3_MEDIA_MAX_CONTENT_LENGTH`
`LANGFUSE_S3_MEDIA_DOWNLOAD_URL_EXPIRY_SECONDS` | `false`
``
``
``
``
``
``
``
`1_000_000_000`
`3600` | S3 configuration for enabling [multi-modal attachments](/content/docs/tracing-features/multi-modality/index.html). All variables are optional and will use the default values shown if not specified. Set `LANGFUSE_S3_MEDIA_UPLOAD_ENABLED=true` to enable multi-modal attachments. Configured storage bucket must have a publicly resolvable hostname to support direct uploads via our SDKs and media asset fetching directly from the browser. | | `DB_EXPORT_PAGE_SIZE` | `1000` | Optional page size for streaming exports to S3 to avoid memory issues. The page size can be adjusted if needed to optimize performance. | | `LANGFUSE_AUTO_POSTGRES_MIGRATION_DISABLED` | `false` | Set to `true` to disable automatic database migrations on docker startup. | | `LANGFUSE_LOG_LEVEL` | `info` | Set the log level for the application. Possible values are `trace`, `debug`, `info`, `warn`, `error`, `fatal`. | | `LANGFUSE_LOG_FORMAT` | `text` | Set the log format for the application. Possible values are `text`, `json`. | | `NEXT_PUBLIC_BASE_PATH` | | Set the base path for the application. This is useful if you want to deploy Langfuse on a subpath, especially when integrating Langfuse into existing infrastructure. Refer to the [section](/content/self-hosting/v2/deployment-guide#custom-base-path/index.html) below for details. | ### [Authentication](/content/self-hosting/v2/deployment-guide\#authentication/index.html) #### [Email/Password](/content/self-hosting/v2/deployment-guide\#auth-email-password/index.html) Email/password authentication is enabled by default. Users can sign up and log in using their email and password. To disable email/password authentication, set `AUTH_DISABLE_USERNAME_PASSWORD=true`. In this case, you need to set up [SSO](/content/self-hosting/v2/deployment-guide#sso/index.html) instead. If you want to provision a default user for your Langfuse instance, you can use the [`LANGFUSE_INIT_*`](/content/self-hosting/v2/deployment-guide#initialization/index.html) environment variables. **Password Reset** - **If transactional emails are configured** on your instance via the `SMTP_CONNECTION_URL` and `EMAIL_FROM_ADDRESS` environments, users can reset their password by using the "Forgot password" link on the login page. - **If transactional emails are not set up**, passwords can be reset by following these steps: 1. Update the email associated with your user account in database, such as by adding a prefix. 2. You can then sign up again with a new password. 3. Reassign any organizations you were associated with via the `organization_memberships` table in database. 4. Finally, remove the old user account from the `users` table in database. #### [SSO](/content/self-hosting/v2/deployment-guide\#sso/index.html) To enable OAuth/SSO provider sign-in for Langfuse, add the following environment variables: | Provider | Variables | OAuth Redirect URL | | --- | --- | --- | | [Google](https://next-auth.js.org/providers/google) | `AUTH_GOOGLE_CLIENT_ID`
`AUTH_GOOGLE_CLIENT_SECRET`
`AUTH_GOOGLE_ALLOW_ACCOUNT_LINKING=true` (optional)
`AUTH_GOOGLE_ALLOWED_DOMAINS=langfuse.com,google.com`(optional, list of allowed domains based on [`hd` OAuth claim](https://developers.google.com/identity/openid-connect/openid-connect#an-id-tokens-payload)) | `/api/auth/callback/google` | | [GitHub](https://next-auth.js.org/providers/github) | `AUTH_GITHUB_CLIENT_ID`
`AUTH_GITHUB_CLIENT_SECRET`
`AUTH_GITHUB_ALLOW_ACCOUNT_LINKING=true` (optional) | `/api/auth/callback/github` | | GitHub Enterprise | `AUTH_GITHUB_ENTERPRISE_CLIENT_ID`
`AUTH_GITHUB_ENTERPRISE_CLIENT_SECRET`
`AUTH_GITHUB_ENTERPRISE_BASE_URL`
`AUTH_GITHUB_ENTERPRISE_ALLOW_ACCOUNT_LINKING=false` (optional) | `/api/auth/callback/github-enterprise` | | [GitLab](https://next-auth.js.org/providers/gitlab) | `AUTH_GITLAB_CLIENT_ID`
`AUTH_GITLAB_CLIENT_SECRET`
`AUTH_GITLAB_ISSUER` (optional)
`AUTH_GITLAB_ALLOW_ACCOUNT_LINKING=true` (optional) | `/api/auth/callback/gitlab` | | [AzureAD/Entra ID](https://next-auth.js.org/providers/azure-ad) | `AUTH_AZURE_AD_CLIENT_ID`
`AUTH_AZURE_AD_CLIENT_SECRET`
`AUTH_AZURE_AD_TENANT_ID`
`AUTH_AZURE_ALLOW_ACCOUNT_LINKING=true` (optional) | `/api/auth/callback/azure-ad` | | [Okta](https://next-auth.js.org/providers/okta) | `AUTH_OKTA_CLIENT_ID`
`AUTH_OKTA_CLIENT_SECRET`
`AUTH_OKTA_ISSUER`
`AUTH_OKTA_ALLOW_ACCOUNT_LINKING=true` (optional) | `/api/auth/callback/okta` | | [OneLogin](https://next-auth.js.org/providers/onelogin) | `AUTH_ONELOGIN_CLIENT_ID`
`AUTH_ONELOGIN_CLIENT_SECRET`
`AUTH_ONELOGIN_ISSUER`
`AUTH_ONELOGIN_ALLOW_ACCOUNT_LINKING=true` (optional) | `/api/auth/callback/onelogin` | | [Auth0](https://next-auth.js.org/providers/auth0) | `AUTH_AUTH0_CLIENT_ID`
`AUTH_AUTH0_CLIENT_SECRET`
`AUTH_AUTH0_ISSUER`
`AUTH_AUTH0_ALLOW_ACCOUNT_LINKING=true` (optional) | `/api/auth/callback/auth0` | | [AWS Cognito](https://next-auth.js.org/providers/cognito) | `AUTH_COGNITO_CLIENT_ID`
`AUTH_COGNITO_CLIENT_SECRET`
`AUTH_COGNITO_ISSUER`
`AUTH_COGNITO_ALLOW_ACCOUNT_LINKING=true` (optional) | `/api/auth/callback/cognito` | | [Keycloak](https://next-auth.js.org/providers/keycloak) | `AUTH_KEYCLOAK_CLIENT_ID`
`AUTH_KEYCLOAK_CLIENT_SECRET`
`AUTH_KEYCLOAK_ISSUER`
`AUTH_KEYCLOAK_ALLOW_ACCOUNT_LINKING=true` (optional) | `/api/auth/callback/keycloak` | | [Custom OAuth](https://next-auth.js.org/configuration/providers/oauth#using-a-custom-provider) ( [source](https://github.com/langfuse/langfuse/blob/main/web/src/server/auth.ts)) | `AUTH_CUSTOM_CLIENT_ID`
`AUTH_CUSTOM_CLIENT_SECRET`
`AUTH_CUSTOM_ISSUER`
`AUTH_CUSTOM_NAME` (any, used only in UI)
`AUTH_CUSTOM_ALLOW_ACCOUNT_LINKING=true` (optional)
`AUTH_CUSTOM_SCOPE` (optional, defaults to `"openid email profile"`) | `/api/auth/callback/custom` | Use `*_ALLOW_ACCOUNT_LINKING` to allow merging accounts with the same email address. This is useful when users sign in with different providers or email/password but have the same email address. You need to be careful with this setting as it can lead to security issues if the emails are not verified. Need another provider? Langfuse uses Auth.js, which integrates with [many providers](https://next-auth.js.org/providers/). Add a [feature request on GitHub](/content/ideas/index.html) if you want us to add support for a specific provider. #### [Additional configuration](/content/self-hosting/v2/deployment-guide\#additional-configuration/index.html) | Variable | Description | | --- | --- | | `AUTH_DOMAINS_WITH_SSO_ENFORCEMENT` | Comma-separated list of domains that are only allowed to sign in using SSO. Email/password sign in is disabled for these domains. E.g. `domain1.com,domain2.com` | | `AUTH_DISABLE_SIGNUP` | Set to `true` to disable sign up for new users. Only existing users can sign in. This affects all new users that try to sign up, also those who received an invite to a project and have no account yet. | | `AUTH_SESSION_MAX_AGE` | Set the maximum age of the session (JWT) in minutes. The default is 30 days (`43200`). The value must be greater than 5 minutes, as the front-end application refreshes its session every 5 minutes. | ### [Headless Initialization](/content/self-hosting/v2/deployment-guide\#initialization/index.html) By default, you need to create a user account, organization and project via the Langfuse UI before being able to use the API. You can find the API keys in the project settings within the UI. If you want to automatically initialize these resources, you can optionally use the following `LANGFUSE_INIT_*` environment variables. When these variables are set, Langfuse will automatically create the specified resources on startup if they don't already exist. This allows for easy integration with infrastructure-as-code and automated deployment pipelines. | Environment Variable | Description | Required to Create Resource | Example | | --- | --- | --- | --- | | `LANGFUSE_INIT_ORG_ID` | Unique identifier for the organization | Yes | `my-org` | | `LANGFUSE_INIT_ORG_NAME` | Name of the organization | No | `My Org` | | `LANGFUSE_INIT_PROJECT_ID` | Unique identifier for the project | Yes | `my-project` | | `LANGFUSE_INIT_PROJECT_NAME` | Name of the project | No | `My Project` | | `LANGFUSE_INIT_PROJECT_PUBLIC_KEY` | Public API key for the project | Yes | `lf_pk_1234567890` | | `LANGFUSE_INIT_PROJECT_SECRET_KEY` | Secret API key for the project | Yes | `lf_sk_1234567890` | | `LANGFUSE_INIT_USER_EMAIL` | Email address of the initial user | Yes | `user@example.com` | | `LANGFUSE_INIT_USER_NAME` | Name of the initial user | No | `John Doe` | | `LANGFUSE_INIT_USER_PASSWORD` | Password for the initial user | Yes | `password123` | The different resources depend on each other in the following way. You can e.g. initialize an organization and a user without having to also initialize a project and API keys, but you cannot initialize a project without also initializing an organization. ``` Organization ├── Project (part of organization) │ └── API Keys (set for project) └── User (owner of organization) ``` Troubleshooting: - If you use `LANGFUSE_INIT_*` in Docker Compose, do not double-quote the values ( [GitHub issue](https://github.com/langfuse/langfuse/issues/3398)). - The resources depend on one another (see note above). For example, you must create an organization to initialize a project. ### [Configuring the Enterprise Edition](/content/self-hosting/v2/deployment-guide\#ee/index.html) The Enterprise Edition ( [compare versions](/content/pricing-self-host/index.html)) of Langfuse includes additional optional configuration options that can be set via environment variables. | Variable | Description | | --- | --- | | `LANGFUSE_ALLOWED_ORGANIZATION_CREATORS` | Comma-separated list of allowlisted users that can create new organizations. By default, all users can create organizations. E.g. `user1@langfuse.com,user2@langfuse.com`. | | `LANGFUSE_UI_API_HOST` | Customize the hostname that is referenced in the settings. Defaults to `window.origin`. | | `LANGFUSE_UI_DOCUMENTATION_HREF` | Customize the documentation link reference in the menu and settings. | | `LANGFUSE_UI_SUPPORT_HREF` | Customize the support link reference in the menu and settings. | | `LANGFUSE_UI_FEEDBACK_HREF` | Replace the default feedback widget with your own feedback link. | | `LANGFUSE_UI_LOGO_DARK_MODE_HREF`
`LANGFUSE_UI_LOGO_LIGHT_MODE_HREF` | Co-brand the Langfuse interface with your own logo. Langfuse adapts to the logo width, with a maximum aspect ratio of 1:3. Narrower ratios (e.g., 2:3, 1:1) also work. The logo is fitted into a bounding box, so there are no specific pixel constraints. For reference, the example logo is 160px x 400px. | | `LANGFUSE_UI_DEFAULT_MODEL_ADAPTER` | Set the default model adapter for the LLM playground and evals. Options: `OpenAI`, `Anthropic`, `Azure`. Example: `Anthropic` | | `LANGFUSE_UI_DEFAULT_BASE_URL_OPENAI` | Set the default base URL for OpenAI API in the LLM playground and evals. Example: `https://api.openai.com/v1` | | `LANGFUSE_UI_DEFAULT_BASE_URL_ANTHROPIC` | Set the default base URL for Anthropic API in the LLM playground and evals. Example: `https://api.anthropic.com` | | `LANGFUSE_UI_DEFAULT_BASE_URL_AZURE_OPENAI` | Set the default base URL for Azure OpenAI API in the LLM playground and evals. Example: `https://{instanceName}.openai.azure.com/openai/deployments` | ### [Health and Readiness Check Endpoint](/content/self-hosting/v2/deployment-guide\#health-and-readiness-check-endpoint/index.html) Langfuse includes a health check endpoint at `/api/public/health` and a readiness check endpoint at `/api/public/ready`. The health check endpoint checks the API functionality and indicates if the application is alive. The readiness check endpoint indicates if the application is ready to serve traffic. Access the health and readiness check endpoints: ``` curl http://localhost:3000/api/public/health curl http://localhost:3000/api/public/ready ``` The potential responses from the health check endpoint are: - `200 OK`: Both the API is functioning normally and a successful connection to the database was made. - `503 Service Unavailable`: Either the API is not functioning or it couldn't establish a connection to the database. The potential responses from the readiness check endpoint are: - `200 OK`: The application is ready to serve traffic. - `500 Internal Server Error`: The application received a SIGTERM or SIGINT and should not receive traffic. Applications and monitoring services can call this endpoint periodically for health updates. Per default, the healthcheck endpoint does not validate if the database is reachable, as there are cases where the database is unavailable, but the application still serves traffic. If you want to run database healthchecks, you can add `?failIfDatabaseUnavailable=true` to the healthcheck endpoint. ### [Encryption](/content/self-hosting/v2/deployment-guide\#encryption/index.html) #### [Encryption in transit (HTTPS)](/content/self-hosting/v2/deployment-guide\#https/index.html) For encryption in transit, HTTPS is strongly recommended. Langfuse itself does not handle HTTPS directly. Instead, HTTPS is typically managed at the infrastructure level. There are two main approaches to handle HTTPS for Langfuse: 1. Load Balancer Termination: In this approach, HTTPS is terminated at the load balancer level. The load balancer handles the SSL/TLS certificates and encryption, then forwards the decrypted traffic to the Langfuse container over HTTP. This is a common and straightforward method, especially in cloud environments. - Pros: Simplifies certificate management as it is usually a fully managed service (e.g. AWS ALB), offloads encryption overhead from application servers. - Cons: Traffic between load balancer and Langfuse container is unencrypted (though typically within a secure network). 2. Service Mesh Sidecar: This method involves using a service mesh like Istio or Linkerd. A sidecar proxy is deployed alongside each Langfuse container, handling all network traffic including HTTPS. - Pros: Provides end-to-end encryption (mutual TLS), offers advanced traffic management and observability. - Cons: Adds complexity to the deployment, requires understanding of service mesh concepts. Once HTTPS is enabled, you can configure add `LANGFUSE_CSP_ENFORCE_HTTPS=true` to ensure browser only allow HTTPS connections when using Langfuse. #### [Encryption at rest (database)](/content/self-hosting/v2/deployment-guide\#encryption-at-rest/index.html) All Langfuse data is stored in your Postgres database. Database-level encryption is recommended for a secure production deployment and available across cloud providers. The Langfuse team has implemented this for Langfuse Cloud and it is fully ISO27001, SOC2 Type 2, HIPAA, and GDPR compliant ( [security center](/content/docs/security/index.html)). #### [Additional application-level encryption](/content/self-hosting/v2/deployment-guide\#application-level-encryption/index.html) In addition to in-transit and at-rest encryption, sensitive data is also encrypted or hashed at the application level. | Data | Encryption | | --- | --- | | API keys | Hashed using `SALT` | | Langfuse Console JWTs | Encrypted via `NEXTAUTH_SECRET` | | LLM API credentials stored in Langfuse | Encrypted using `ENCRYPTION_KEY` | | Integration credentials (e.g. PostHog) | Encrypted using `ENCRYPTION_KEY` | | Input/Outputs of LLM Calls, Traces, Spans | Work in progress, [contact sales](/content/talk-to-us/index.html) if you are interested in this | ### [Build Langfuse from source](/content/self-hosting/v2/deployment-guide\#build-from-source/index.html) While we recommend using the prebuilt docker image, you can also build the image yourself from source. The repo includes multiple `Dockerfile` files. You only need to build the `web` Dockerfile as shown below. ``` # clone repo git clone https://github.com/langfuse/langfuse.git cd langfuse # checkout v2 branch # main branch includes unreleased changes that might be unstable git checkout v2 # build image docker build -t langfuse/langfuse -f ./web/Dockerfile . ``` ### [Custom Base Path](/content/self-hosting/v2/deployment-guide\#custom-base-path/index.html) If you want to deploy Langfuse behind a custom base path (e.g. `https://yourdomain.com/langfuse`), you can set the `NEXT_PUBLIC_BASE_PATH` environment variable. This is useful if you want to deploy Langfuse on a subpath, especially when integrating Langfuse into existing infrastructure. As this base path is inlined in static assets, you cannot use the prebuilt docker image. **You need to build the image from source** with the `NEXT_PUBLIC_BASE_PATH` environment variable set at build time. When using a custom base path, `NEXTAUTH_URL` must be set to the full URL including the base path and `/api/auth`. For example, if you are deploying Langfuse at `https://yourdomain.com/langfuse-base-path`, you need to set: .env ``` NEXT_PUBLIC_BASE_PATH="/langfuse-base-path" NEXTAUTH_URL="https://yourdomain.com/langfuse-base-path/api/auth" ``` Build image with `NEXT_PUBLIC_BASE_PATH` as build argument: ``` # clone repo git clone https://github.com/langfuse/langfuse.git cd langfuse # checkout v2 branch # main branch includes unreleased changes that might be unstable git checkout v2 # build image with NEXT_PUBLIC_BASE_PATH docker build -t langfuse/langfuse --build-arg NEXT_PUBLIC_BASE_PATH=/langfuse-base-path -f ./web/Dockerfile . ``` Once your Langfuse instance is running, you can access both the API and console through your configured custom base path. When connecting via SDKs, make sure to include the custom base path in the hostname. ### [Troubleshooting](/content/self-hosting/v2/deployment-guide\#troubleshooting/index.html) If you encounter issues, ensure the following: - `NEXTAUTH_URL` exactly matches the URL you're accessing Langfuse with. Pay attention to the protocol (http vs https) and the port (e.g., 3000 if you do not expose Langfuse on port 80). - Set `HOSTNAME` to `0.0.0.0` if you cannot access Langfuse. - Encode special characters in `DATABASE_URL`, see this StackOverflow [answer](https://stackoverflow.com/a/68213745) for details. - If you use the SDKs to connect with Langfuse, use `auth_check()` to verify that the connection works. - Make sure you are at least on Postgres 12. - When using Docker Compose / Kubernetes, your application needs to connect to the Langfuse container at the docker internal network address that you specified, e.g. `http://langfuse:3000`/`http://langfuse.docker.internal:3000`. Learn more: [docker compose networking documentation](https://docs.docker.com/compose/how-tos/networking/), [kubernetes networking documentation](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/) - SSO - Ensure that the OAuth provider is configured correctly. The return path needs to match the `NEXTAUTH_URL`, and the OAuth client needs to be configured with the correct callback URL. - Langfuse uses NextAuth.js. Please refer to the [NextAuth.js documentation](https://next-auth.js.org/) for more information. ## [Updating the Application](/content/self-hosting/v2/deployment-guide\#update/index.html) We recommend enabling automated updates within the current major version to benefit from the latest features, bug fixes, and security patches. Coming from Langfuse v1? Please refer to the [upgrade\\ guide](/content/self-hosting/upgrade-guides/upgrade-v1-to-v2/index.html) for more details. To update the application: 1. Stop the container. 2. Pull the latest container. 3. Restart the application. During container startup, any necessary database migrations will be applied automatically if the database schema has changed. This can be optionally disabled via environment variables. Langfuse is released through tagged semver releases. Check [GitHub releases](https://github.com/langfuse/langfuse/releases) for information about the changes in each version. _Watch the repository on GitHub to get notified about new releases_ ## [Kubernetes deployments](/content/self-hosting/v2/deployment-guide\#kubernetes-deployments/index.html) Kubernetes is a popular choice for deploying Langfuse when teams maintain the rest of their infrastructure using Kubernetes. You can find community-maintained templates and Helm Charts in the [langfuse/langfuse-k8s](https://github.com/langfuse/langfuse-k8s) repository. If you encounter any bugs or have suggestions for improvements, please contribute to the repository by submitting issues or pull requests. ## [Platform-specific information](/content/self-hosting/v2/deployment-guide\#platform-specific-information/index.html) This section is work in progress and relies on community contributions. The Langfuse team/maintainers do not have the capacity to maintain or test this section. If you have successfully deployed Langfuse on a specific platform, consider contributing a guide either via a GitHub [PR/Issue](https://github.com/langfuse/langfuse-docs) or by [reaching\\ out](/content/self-hosting/v2/deployment-guide#contact/index.html) to the maintainers. Please also let us know if one of these guides does not work anymore or if you have a better solution. ### [Railway](/content/self-hosting/v2/deployment-guide\#railway/index.html) ### [Porter.run](/content/self-hosting/v2/deployment-guide\#porterrun/index.html) If you use [Porter](https://porter.run/) to deploy your application, you can easily add a Langfuse instance to your cluster via the "Add-ons". The add-on will automatically configure the necessary environment variables, inject your database credentials, and deploy and autoscale the Langfuse container. Learn more about this in our [changelog](/content/changelog/2024-08-15-deployment-as-porter-add-on/index.html). ### [AWS](/content/self-hosting/v2/deployment-guide\#aws/index.html) We recommend deploying Langfuse on AWS using the Elastic Container Service (ECS) and Fargate for a scalable and low-maintenance container deployment. Note: you can use AWS Cognito for SSO. Have a look at this configuration template: [aws-samples/deploy-langfuse-on-ecs-with-fargate](https://github.com/aws-samples/deploy-langfuse-on-ecs-with-fargate) ### [Azure](/content/self-hosting/v2/deployment-guide\#azure/index.html) Deploy Langfuse to Azure using the Azure Container Instances service for a flexible and low-maintenance container deployment. Note: you can use Azure AD for SSO. You can deploy Langfuse to Azure via the Azure Developer CLI using this template: [Azure-Samples/langfuse-on-azure](https://github.com/Azure-Samples/langfuse-on-azure). ### [Google Cloud Platform (Cloud Run & Cloud SQL)](/content/self-hosting/v2/deployment-guide\#google-cloud-platform-cloud-run--cloud-sql/index.html) The simplest way to deploy Langfuse on Google Cloud Platform is to use Cloud Run for the containerized application and Cloud SQL for the database. #### [Option 1: UI Deployment](/content/self-hosting/v2/deployment-guide\#option-1-ui-deployment/index.html) **Create Cloud SQL Instance:** 1. Open Google Cloud SQL. 2. Click on Create Instance. 3. Choose PostgreSQL and configure the instance according to your requirements. 4. You'll need the following details: - default > user: postgres - default > database schema: public - setup > password: `` - connection > connection name: `::` **Optionally: Create OAuth Credentials for sign-in with Google** 1. Open [API Credentials](https://console.cloud.google.com/apis/credentials) 2. Click "Create Credentials" and then "OAuth Client ID" 3. Choose "Web Application" and then give it an appropriate name 4. Click Create **Create Secrets:** 1. Open [Secret Manager](https://console.cloud.google.com/security/secret-manager) 2. For each secret needed (at least `AUTH_GOOGLE_CLIENT_ID, AUTH_GOOGLE_CLIENT_SECRET, DATABASE_URL, DIRECT_URL, NEXTAUTH_SECRET, NEXTAUTH_URL,` and `SALT`), click "Create Secret" and fill in the name and value. Notes: - `DATABASE_URL` is the connection string to the Cloud SQL instance. `postgresql://:@localhost//?host=/cloudsql/::&sslmode=none&pgbouncer=true` - `DIRECT_URL` is for database migrations, without `&pgbouncer=true`, the value should look like this: `postgresql://:@localhost//?host=/cloudsql/::&sslmode=none` - Set `NEXTAUTH_URL` to `http://localhost:3000`. This is a placeholder, we'll update it later. **Deploy on Cloud Run:** 01. Open Google Cloud Run. 02. Click on Create Service. 03. Enter the following container image URL: `docker.io/langfuse/langfuse:2`. We use tag `2` to pin the major version. 04. Configure the service name and region according to your requirements. 05. Select authentication as 'Allow unauthenticated invocations', as Langfuse will have its own built-in Authentication that you can use. 06. Choose 'CPU Allocation and Pricing' as "CPU is only allocated during request processing" to scale down the instance to 0 when there are no requests. 07. Configure ingress control according to your needs. For most cases, 'All' should suffice. 08. "Container(s), Volumes, Networking & Security": - Specify container port as `3000`. - On "Variables & Secrets" tab, add the required environment variables (see table above): `SALT`, `NEXTAUTH_URL`, `NEXTAUTH_SECRET`, and `DATABASE_URL`, etc. 09. Scroll all the way down to enable the Cloud SQL connections. Select the created Cloud SQL instance in the dropdown. Context: Your Cloud Run service won't be assigned a static IP, so you can't whitelist the ingress IP in Cloud SQL or any other hosted databases. Instead, we use the Google Cloud SQL Proxy. 10. Finally, you can finish deploying the application. 11. While the application is deployed for the first time, you can see how the database migrations are applied in the logs. 12. Once the application is up and running, you can find the Cloud Run service URL on top of the page. Now, choose "Edit and deploy new revision" to update the `NEXTAUTH_URL` environment variable to the Cloud Run service URL ending in `.run.app`. 13. Optionally, configure a custom domain for the Cloud Run service. **Troubleshooting: Cloud SQL Connection Issues** If you encounter an error like "Error 403: boss::NOT\_AUTHORIZED: Not authorized to access resource" or "Possibly missing permission cloudsql.instances.connect" when deploying the Langfuse container, you may need to grant 'Cloud SQL Client' permissions to the relevant service accounts. Here's how to resolve this: 1. In the Google Cloud search box, search for and select "Service Accounts". 2. Find the service accounts with names ending in `@appspot.gserviceaccount.com` and `-compute@developer.gserviceaccount.com`. 3. In the Google Cloud search box, search for and select "IAM & Admin". 4. Click "Grant Access", then "Add Principals". 5. Enter the name of the first service account you found. 6. Select the "Cloud SQL Client" role and save. 7. Repeat steps 4-6 for the second service account. After granting these permissions, try redeploying your Cloud Run service. This should resolve any authorization issues related to connecting to your Cloud SQL instance. #### [Option 2: Cloud Build](/content/self-hosting/v2/deployment-guide\#option-2-cloud-build/index.html) Google Cloud Build is GCP's continuous integration and continuous deployment (CI/CD) service that automates the building, testing, and deployment of your applications. To deploy Langfuse, you can specify your workflow in a cloudbuild.yaml file. Additionally, GCP's Secret Manager can be used to securely handle sensitive information like DATABASE\_URL and NEXTAUTH\_SECRET. Below is an example of how to set up a Cloud Build configuration: ``` # Deployment configuration for Langfuse on Google Cloud Run substitutions: _SERVICE_NAME: langfuse _REGION: europe-west1 # Change to your desired region _PROJECT_ID: your-project-id # Change to your Google Cloud project ID _SQL_INSTANCE_ID: my-cool-db # the name of the cloud sql database you create tags: ["${_PROJECT_ID}", "${_SERVICE_NAME}"] steps: # Step to deploy the Docker image to Google Cloud Run - name: "gcr.io/cloud-builders/gcloud" id: deploy-cloud-run entrypoint: bash args: - "-c" - | gcloud run deploy ${_SERVICE_NAME} --image docker.io/langfuse/langfuse:2 \ --region ${_REGION} \ --project ${_PROJECT_ID} \ --platform managed \ --port 3000 \ --allow-unauthenticated \ --memory 2Gi \ --cpu 1 \ --min-instances 0 \ --max-instances 3 \ --set-env-vars HOSTNAME=0.0.0.0 \ --add-cloudsql-instances=${_PROJECT_ID}:${_REGION}:${_SQL_INSTANCE_ID} \ --update-secrets AUTH_GOOGLE_CLIENT_ID=AUTH_GOOGLE_CLIENT_ID:latest,AUTH_GOOGLE_CLIENT_SECRET=AUTH_GOOGLE_CLIENT_SECRET:latest,SALT=SALT:latest,NEXTAUTH_URL=NEXTAUTH_URL:latest,NEXTAUTH_SECRET=NEXTAUTH_SECRET:latest,DATABASE_URL=DATABASE_URL:latest,DIRECT_URL=DIRECT_URL:latest ``` You can submit this build using [`gcloud build submit`](https://cloud.google.com/sdk/gcloud/reference/builds/submit) in your local console by issuing the below in the same folder as the `cloudbuild.yaml` file. To submit this build, use the following command in your local console, in the directory containing the `cloudbuild.yaml` file: ``` gcloud builds submit . ``` For automatic rebuilds upon new commits, set up a [Cloud Build Trigger](https://cloud.google.com/build/docs/automating-builds/create-manage-triggers) linked to your repository holding the `cloudbuild.yaml` file. This will redeploy Langfuse whenever changes are pushed to the repository. #### [Note on AlloyDB](/content/self-hosting/v2/deployment-guide\#note-on-alloydb/index.html) [AlloyDB](https://cloud.google.com/alloydb) is a fully-managed postgres compatible database offered by Google Cloud Platform that is tuned for better performance for tasks such as analytical queries and in-database embeddings. It is recommend you use it within a [Shared VPC](https://cloud.google.com/vpc/docs/shared-vpc) with your Cloud Run runtime, which will expose AlloyDB's private ip address to your application. If you are using it the DB connection string changes slightly: ``` # ALLOYDB_CONNECTION_STRING postgresql://:@:5432//?sslmode=none&pgbouncer=true ``` ``` # ALLOYDB_DIRECT_URL postgresql://:@:5432//?sslmode=none ``` ### [Heroku](/content/self-hosting/v2/deployment-guide\#heroku/index.html) To deploy this image on heroku you have to run through the steps in the following deployment guide: 1. **Pull the docker image. This can be achieved by running the following command in your terminal:** ``` docker pull langfuse/langfuse:2 ``` 2. **Get the ID of the pulled image** _Linux / MacOS_: Running the following command should result in directly printing the image ID ``` docker images | grep langfuse/langfuse | awk '[print $3]' ``` Following this tutorial, you will always have to insert this image ID when \[IMAGE\_ID\] is written. _Windows_: On windows you can print the full information of the pulled image using: ``` docker images | findstr /S "langfuse/langfuse" ``` This will result in something like: ``` langfuse/langfuse 2 cec90c920468 28 hours ago 595MB ``` Here you have to manually retrieve the image ID which in this case is `cec90c920468`. It should be located between the tag `2` and the created `28 hours ago` in this example. 3. **Prepare your terminal and docker image** First of all, you will have to be logged in to heroku using ``` heroku login ``` If this is not working, please visit the [heroku CLI setup](https://devcenter.heroku.com/articles/heroku-cli). If you succeeded in logging in to heroku via the CLI, you can continue by following the next steps: Tag the docker image (Insert your image ID into the command). You will also have to insert the name of your heroku app/dyno into \[HEROKU\_APP\_NAME\]: ``` docker tag [IMAGE_ID] registry.heroku.com/[HEROKU_APP_NAME]/web ``` 4. **Setup a database for your heroku app** In the dashboard of your heroku app, add the `Heroku Postgres`-AddOn. This will add a PostgreSQL database to your application. 5. **Set the environment variables** For the minimum deployment in heroku, you will have to set the following environment variables (see table above). The `DATABASE_URL` is your database connection string starting with `postgres://` in the configuration of your added PostgreSQL database. ``` DATABASE_URL= NEXTAUTH_SECRET= NEXTAUTH_URL= SALT= ``` Have a look at the other optional environment variables in the table above and set them if needed to configure your deployment. 6. **Push to heroku container registry** In this step you will push the docker image to the heroku container registry: (Insert the name of your heroku app/dyno) ``` docker push registry.heroku.com/[HEROKU_APP_NAME]/web ``` 7. **Deploy the docker image from the heroku registry** In the last step you will have to execute the following command to finally deploy the image. Again insert the name of your heroku app: ``` heroku container:release web --app=[HEROKU_APP_NAME] ``` ## [FAQ](/content/self-hosting/v2/deployment-guide\#faq/index.html) - [Are older versions of the SDK compatible with newer versions of Langfuse?](/content/faq/all/compatibility-langfuse-ui-and-python-sdk/index.html) - [Are prebuilt ARM images available?](/content/faq/all/arm-images/index.html) - [Can I deploy multiple instances of Langfuse behind a load balancer?](/content/faq/all/self-host-with-load-balancer/index.html) - [Clickhouse handling failed migrations in self-hosted Langfuse](/content/faq/all/self-hosting-clickhouse-handling-failed-migrations/index.html) - [How can I migrate data between Langfuse instances?](/content/faq/all/migrate-data-between-langfuse-instances/index.html) - [How can I restrict access on my self-hosted instance to internal users?](/content/faq/all/limit-access-to-internal-users/index.html) - [How do I migrate Langfuse from ClickHouse OSS to Cloud or BYOC?](/content/faq/all/self-hosting-migrate-clickhouse-oss-to-cloud/index.html) - [How do I reduce ClickHouse disk size on self-hosted Langfuse?](/content/faq/all/reduce-clickhouse-disk-size/index.html) - [How do I troubleshoot the self-hosted Langfuse Assistant?](/content/faq/all/troubleshoot-self-hosted-langfuse-assistant/index.html) - [How to manage different environments in Langfuse?](/content/faq/all/managing-different-environments/index.html) - [I cannot connect to my docker deployment, what should I do?](/content/faq/all/debug-docker-deployment/index.html) - [I have forgotten my password](/content/faq/all/forgot-password/index.html) - [Intermittent 502 and 504 network errors in self-hosted Langfuse](/content/faq/all/self-hosting-502-504-network-errors/index.html) - [JavaScript heap out of memory error in self-hosted Langfuse](/content/faq/all/self-hosting-javascript-heap-out-of-memory/index.html) - [Missing events after POST /api/public/ingestion in self-hosted Langfuse](/content/faq/all/self-hosting-missing-events-after-ingestion/index.html) - [PostgreSQL table ownership and migration failures in self-hosted Langfuse](/content/faq/all/self-hosting-postgresql-table-ownership-migration-failures/index.html) - [Queue management with BullMQ Admin API in self-hosted Langfuse](/content/faq/all/self-hosting-queue-management-bullmq-admin-api/index.html) - [Socket usage at capacity error in self-hosted Langfuse](/content/faq/all/self-hosting-socket-usage-at-capacity/index.html) - [Timezone errors in self-hosted Langfuse](/content/faq/all/self-hosting-timezone-errors/index.html) - [Where can I find the API reference for self-hosted Langfuse?](/content/faq/all/self-hosting-api-reference/index.html) - [Why is my data retention job running into timeouts?](/content/faq/all/data-retention-timeouts-and-errors/index.html) ## [GitHub Discussions](/content/self-hosting/v2/deployment-guide\#github-discussions/index.html) [Handling Rapid ClickHouse Growth (320GB+ in 60 days) via S3 Tiered Storage on EKS](https://github.com/orgs/langfuse/discussions/13013 "Langfuse Support: Handling Rapid ClickHouse Growth (320GB+ in 60 days) via S3 Tiered Storage on EKS") [Clickhouse with S3 not accessiable by Langfuse web and worker containers](https://github.com/orgs/langfuse/discussions/12759 "Langfuse Support: Clickhouse with S3 not accessiable by Langfuse web and worker containers") [I need help for setting up SMTP URL Connection](https://github.com/orgs/langfuse/discussions/12170 "Langfuse Support: I need help for setting up SMTP URL Connection") [S3 / Object Storage migration approach recommendations](https://github.com/orgs/langfuse/discussions/12097 "Langfuse Support: S3 / Object Storage migration approach recommendations") [Prompt cache keys never written to Redis on self-hosted prod (v3.133)](https://github.com/orgs/langfuse/discussions/12054 "Langfuse Support: Prompt cache keys never written to Redis on self-hosted prod (v3.133)") [Custom modification in web and build custom image](https://github.com/orgs/langfuse/discussions/12011 "Langfuse Support: Custom modification in web and build custom image") [InvalidAccessKeyId: The Access Key Id you provided does not exist in our records](https://github.com/orgs/langfuse/discussions/11959 "Langfuse Support: InvalidAccessKeyId: The Access Key Id you provided does not exist in our records") [Support needed for update (self hosted)](https://github.com/orgs/langfuse/discussions/11953 "Langfuse Support: Support needed for update (self hosted)") [Azure AD auth with PROXY: OAUTH\_PARSE\_PROFILE\_ERROR](https://github.com/orgs/langfuse/discussions/11936 "Langfuse Support: Azure AD auth with PROXY: OAUTH_PARSE_PROFILE_ERROR") [Best practices to setup replication, backup/restore and Disaster recovery in Langfuse underlying storage](https://github.com/orgs/langfuse/discussions/11933 "Langfuse Support: Best practices to setup replication, backup/restore and Disaster recovery in Langfuse underlying storage") [How to debug when evaluations are stalling](https://github.com/orgs/langfuse/discussions/11912 "Langfuse Support: How to debug when evaluations are stalling") [Langfuse Web Failing to start Because ClickHouse Tables in Readonly Mode and Zookeeper Metadata Not Found](https://github.com/orgs/langfuse/discussions/11885 "Langfuse Support: Langfuse Web Failing to start Because ClickHouse Tables in Readonly Mode and Zookeeper Metadata Not Found") [Migrate Projects and Users from one Langfuse env to another environment](https://github.com/orgs/langfuse/discussions/11856 "Langfuse Support: Migrate Projects and Users from one Langfuse env to another environment") [CROSSSLOT Redis Error Causing Prompt Creation Failure with Azure Cache for Redis in Cluster Mode (Self host in openshift)](https://github.com/orgs/langfuse/discussions/11853 "Langfuse Support: CROSSSLOT Redis Error Causing Prompt Creation Failure with Azure Cache for Redis in Cluster Mode (Self host in openshift)") [Best practices for resyncing ClickHouse replicas without impacting Langfuse](https://github.com/orgs/langfuse/discussions/11849 "Langfuse Support: Best practices for resyncing ClickHouse replicas without impacting Langfuse") [Helm deployed ClickHouse doesn't work](https://github.com/orgs/langfuse/discussions/11817 "Langfuse Support: Helm deployed ClickHouse doesn't work") [Options for Hosting ClickHouse Outside EKS Cluster](https://github.com/orgs/langfuse/discussions/11797 "Langfuse Support: Options for Hosting ClickHouse Outside EKS Cluster") [Is v2 branch having production code for server and db?](https://github.com/orgs/langfuse/discussions/11771 "Langfuse Support: Is v2 branch having production code for server and db?") [Recommendation for timeout setting](https://github.com/orgs/langfuse/discussions/11733 "Langfuse Support: Recommendation for timeout setting") [Does Langfuse's specific ClickHouse usage require RWX or RWO?](https://github.com/orgs/langfuse/discussions/11724 "Langfuse Support: Does Langfuse's specific ClickHouse usage require RWX or RWO?") [Azure EntraID SSO - Timeout on Self-Hosted](https://github.com/orgs/langfuse/discussions/11698 "Langfuse Support: Azure EntraID SSO - Timeout on Self-Hosted") [PostgreSQL Authentication Failed on Docker Compose Deployment - "provided database credentials for postgres are not valid"](https://github.com/orgs/langfuse/discussions/11688 "Langfuse Support: PostgreSQL Authentication Failed on Docker Compose Deployment - \"provided database credentials for postgres are not valid\"") [Langfuse SSO "No email found in the user profile" when idToken enabled, or "id\_token detected in the response" when disabled](https://github.com/orgs/langfuse/discussions/11605 "Langfuse Support: Langfuse SSO \"No email found in the user profile\" when idToken enabled, or \"id_token detected in the response\" when disabled") [Pulled latest version but still dont see the newer models](https://github.com/orgs/langfuse/discussions/11588 "Langfuse Support: Pulled latest version but still dont see the newer models") [Langfuse self hosted setup not working due to Postgres DB error](https://github.com/orgs/langfuse/discussions/11578 "Langfuse Support: Langfuse self hosted setup not working due to Postgres DB error") [Langfuse Free Plan Data Retention Issue (Data Only Visible for 3 Days)](https://github.com/orgs/langfuse/discussions/11508 "Langfuse Support: Langfuse Free Plan Data Retention Issue (Data Only Visible for 3 Days)") [Does NEXT\_PUBLIC\_SENTRY\_DSN work properly in self-hosted?](https://github.com/orgs/langfuse/discussions/11489 "Langfuse Support: Does NEXT_PUBLIC_SENTRY_DSN work properly in self-hosted?") [Issue when exporting large amount of data](https://github.com/orgs/langfuse/discussions/11462 "Langfuse Support: Issue when exporting large amount of data") [How do I deploy to \`render.com\` properly](https://github.com/orgs/langfuse/discussions/11375 "Langfuse Support: How do I deploy to `render.com` properly") [Langfuse +Docker+Pytest Self Hosting Issue](https://github.com/orgs/langfuse/discussions/11216 "Langfuse Support: Langfuse +Docker+Pytest Self Hosting Issue") [Self hosted Postgres DB supporting external authentication](https://github.com/orgs/langfuse/discussions/11199 "Langfuse Support: Self hosted Postgres DB supporting external authentication") [requires project-scoped API key I can't get it，ask for help](https://github.com/orgs/langfuse/discussions/11191 "Langfuse Support: requires project-scoped API key I can't get it，ask for help") [RBAC / Role-Based Authorization with External IdP (Keycloak) in Langfuse OSS](https://github.com/orgs/langfuse/discussions/11186 "Langfuse Support: RBAC / Role-Based Authorization with External IdP (Keycloak) in Langfuse OSS") [Background migrations stuck in "Queued" status](https://github.com/orgs/langfuse/discussions/11128 "Langfuse Support: Background migrations stuck in \"Queued\" status") [Setting default Data Retention value via LANGFUSE\_INIT\_PROJECT\_RETENTION env variable doesn't work.](https://github.com/orgs/langfuse/discussions/11123 "Langfuse Support: Setting default Data Retention value via LANGFUSE_INIT_PROJECT_RETENTION env variable doesn't work.") [Unable to connect the Langfuse Chart to the Postgres DB with Client Certificate](https://github.com/orgs/langfuse/discussions/11059 "Langfuse Support: Unable to connect the Langfuse Chart to the Postgres DB with Client Certificate") [i want to know minio default account and password](https://github.com/orgs/langfuse/discussions/11049 "Langfuse Support: i want to know minio default account and password") [Can't see any traces when app is deployed on AWS ECS](https://github.com/orgs/langfuse/discussions/10978 "Langfuse Support: Can't see any traces when app is deployed on AWS ECS") [Connect Langfuse to RAGflow](https://github.com/orgs/langfuse/discussions/10967 "Langfuse Support: Connect Langfuse to RAGflow") [Data Migration from Clickhouse OSS (running in EKS) to Clickhouse Cloud](https://github.com/orgs/langfuse/discussions/10956 "Langfuse Support: Data Migration from Clickhouse OSS (running in EKS) to Clickhouse Cloud") [Rolling Upgrades](https://github.com/orgs/langfuse/discussions/10912 "Langfuse Support: Rolling Upgrades") [Slow loading on UI + Clickhouse Timeout Errors](https://github.com/orgs/langfuse/discussions/10877 "Langfuse Support: Slow loading on UI + Clickhouse Timeout Errors") [How to correctly restore the PostgreSQL database for self-hosted Langfuse?](https://github.com/orgs/langfuse/discussions/10804 "Langfuse Support: How to correctly restore the PostgreSQL database for self-hosted Langfuse?") [Evals not executing in real time in high throughput environment](https://github.com/orgs/langfuse/discussions/10773 "Langfuse Support: Evals not executing in real time in high throughput environment") [Inquiry on Licensing for Self-Implemented Enterprise Features (Project-Level RBAC) on Langfuse OSS](https://github.com/orgs/langfuse/discussions/10745 "Langfuse Support: Inquiry on Licensing for Self-Implemented Enterprise Features (Project-Level RBAC) on Langfuse OSS") [Is running ClickHouse migrations on every web container startup safe when scaling? (golang-migrate concurrency)](https://github.com/orgs/langfuse/discussions/10697 "Langfuse Support: Is running ClickHouse migrations on every web container startup safe when scaling? (golang-migrate concurrency)") [Hosting on Azure Issue](https://github.com/orgs/langfuse/discussions/10675 "Langfuse Support: Hosting on Azure Issue") [Intermittent Traces from App](https://github.com/orgs/langfuse/discussions/10648 "Langfuse Support: Intermittent Traces from App") [Install Langfuse + Strands Agent without cloud and without local docker](https://github.com/orgs/langfuse/discussions/10645 "Langfuse Support: Install Langfuse + Strands Agent without cloud and without local docker") [PostgreSQL Authentication Failed Despite Setting Credentials in Helm Values During Langfuse Kubernetes Deployment (Self-Hosting)](https://github.com/orgs/langfuse/discussions/10587 "Langfuse Support: PostgreSQL Authentication Failed Despite Setting Credentials in Helm Values During Langfuse Kubernetes Deployment (Self-Hosting)") [IngestionQueue failed not getting populated with failed events during clickhouse downtime](https://github.com/orgs/langfuse/discussions/10565 "Langfuse Support: IngestionQueue failed not getting populated with failed events during clickhouse downtime") [Postgres table audit\_logs filling up in langfuse open source](https://github.com/orgs/langfuse/discussions/10446 "Langfuse Support: Postgres table audit_logs filling up in langfuse open source") [FATAL: database "admin" does not exist](https://github.com/orgs/langfuse/discussions/10404 "Langfuse Support: FATAL: database \"admin\" does not exist") [How can i setup langfuse enviroment for run experiment?](https://github.com/orgs/langfuse/discussions/10336 "Langfuse Support: How can i setup langfuse enviroment for run experiment?") [Limits Free Tier self-hosted](https://github.com/orgs/langfuse/discussions/10329 "Langfuse Support: Limits Free Tier self-hosted") [ClickHouse (self-hosted) upgrade](https://github.com/orgs/langfuse/discussions/10314 "Langfuse Support: ClickHouse (self-hosted) upgrade") [Langfuse self hosting issue in Internet facing](https://github.com/orgs/langfuse/discussions/10245 "Langfuse Support: Langfuse self hosting issue in Internet facing") [Traces stop appear in self-hosted Langfuse after restart pods](https://github.com/orgs/langfuse/discussions/10238 "Langfuse Support: Traces stop appear in self-hosted Langfuse after restart pods") [Issue with EFS-CSI Driver with the official terraform module](https://github.com/orgs/langfuse/discussions/10226 "Langfuse Support: Issue with EFS-CSI Driver with the official terraform module") [Need help understanding the role of blob storage in Langfuse](https://github.com/orgs/langfuse/discussions/10219 "Langfuse Support: Need help understanding the role of blob storage in Langfuse") [Cannot change database port with docker-compose](https://github.com/orgs/langfuse/discussions/10212 "Langfuse Support: Cannot change database port with docker-compose") [Azure Application Gateway certificate unwanted changed](https://github.com/orgs/langfuse/discussions/10183 "Langfuse Support: Azure Application Gateway certificate unwanted changed") [Self-hosting 1-click deployments](https://github.com/orgs/langfuse/discussions/10022 "Langfuse Support: Self-hosting 1-click deployments") [Auto re-connect database when db is ready](https://github.com/orgs/langfuse/discussions/9996 "Langfuse Support: Auto re-connect database when db is ready") [Clarification related to metadata persistence while running clickhouse as an ECS fargate service](https://github.com/orgs/langfuse/discussions/9964 "Langfuse Support: Clarification related to metadata persistence while running clickhouse as an ECS fargate service") [Langfuse platform features and deployment questions](https://github.com/orgs/langfuse/discussions/9895 "Langfuse Support: Langfuse platform features and deployment questions") [Self-Hosted with ElastiCache and RDS Aurora PostgreSQL - UI Doesn't show traces](https://github.com/orgs/langfuse/discussions/9849 "Langfuse Support: Self-Hosted with ElastiCache and RDS Aurora PostgreSQL - UI Doesn't show traces") [Clickhouse timeout errors](https://github.com/orgs/langfuse/discussions/9847 "Langfuse Support: Clickhouse timeout errors") [USE\_AZURE\_BLOB should be set to true by default when deploying to Azure](https://github.com/orgs/langfuse/discussions/9814 "Langfuse Support: USE_AZURE_BLOB should be set to true by default when deploying to Azure") [Azure Terraform - switch from Access Policies to RBAC for Azure KeyVault](https://github.com/orgs/langfuse/discussions/9805 "Langfuse Support: Azure Terraform - switch from Access Policies to RBAC for Azure KeyVault") [“Body exceeded 1mb limit” error on dataset upload](https://github.com/orgs/langfuse/discussions/9751 "Langfuse Support: “Body exceeded 1mb limit” error on dataset upload") [Disable Create Organizations](https://github.com/orgs/langfuse/discussions/9709 "Langfuse Support: Disable Create Organizations") [Trying to call the langfuse batch ingestion api from a lambda function, all events not visible on dashboard despite 201 success](https://github.com/orgs/langfuse/discussions/9706 "Langfuse Support: Trying to call the langfuse batch ingestion api from a lambda function, all events not visible on dashboard despite 201 success") [how many langfuse.flush() will retry for network faliure ?](https://github.com/orgs/langfuse/discussions/9700 "Langfuse Support: how many langfuse.flush() will retry for network faliure ?") [Documentation / help for recovering Langfuse from a Clickhouse DB backup](https://github.com/orgs/langfuse/discussions/9688 "Langfuse Support: Documentation / help for recovering Langfuse from a Clickhouse DB backup") [Self hosting Langfuse within our Cloud provider as a Highly available architecture](https://github.com/orgs/langfuse/discussions/9675 "Langfuse Support: Self hosting Langfuse within our Cloud provider as a Highly available architecture") [Migration between databases](https://github.com/orgs/langfuse/discussions/9620 "Langfuse Support: Migration between databases") [Self hosted migration issue](https://github.com/orgs/langfuse/discussions/9604 "Langfuse Support: Self hosted migration issue") [DOCKER-COMPOSE.BUILD.YML NO FUNCIONA](https://github.com/orgs/langfuse/discussions/9510 "Langfuse Support: DOCKER-COMPOSE.BUILD.YML NO FUNCIONA") [Rate Limit on self-hosted webapp](https://github.com/orgs/langfuse/discussions/9507 "Langfuse Support: Rate Limit on self-hosted webapp") [ClickHouse migrations marked as "dirty" prevent Langfuse Web from starting](https://github.com/orgs/langfuse/discussions/9442 "Langfuse Support: ClickHouse migrations marked as \"dirty\" prevent Langfuse Web from starting") [Migrate from one data region to another](https://github.com/orgs/langfuse/discussions/9415 "Langfuse Support: Migrate from one data region to another") [Langfuse-web failure](https://github.com/orgs/langfuse/discussions/9412 "Langfuse Support: Langfuse-web failure") [Custom email claim with keycloak (self-hosted)](https://github.com/orgs/langfuse/discussions/9400 "Langfuse Support: Custom email claim with keycloak (self-hosted)") [Any easy way of ingesting the langfuse S3/blob store data to clickhouse](https://github.com/orgs/langfuse/discussions/9350 "Langfuse Support: Any easy way of ingesting the langfuse S3/blob store data to clickhouse") [SMTP\_CONNECTION\_URL invalid due to unencoded \`/\` in password](https://github.com/orgs/langfuse/discussions/9343 "Langfuse Support: SMTP_CONNECTION_URL invalid due to unencoded `/` in password") [Self-hosted headless initialization](https://github.com/orgs/langfuse/discussions/9317 "Langfuse Support: Self-hosted headless initialization") [Failed ClickHouse Migration - "Dirty database version 23" and authentication error](https://github.com/orgs/langfuse/discussions/9298 "Langfuse Support: Failed ClickHouse Migration - \"Dirty database version 23\" and authentication error") [Custom Build Failure with node:24-alpine on K8s, Despite Increased Resources](https://github.com/orgs/langfuse/discussions/9285 "Langfuse Support: Custom Build Failure with node:24-alpine on K8s, Despite Increased Resources") [Does LangFuse support setting up usage alerting functionality in the self-hosted version?](https://github.com/orgs/langfuse/discussions/9280 "Langfuse Support: Does LangFuse support setting up usage alerting functionality in the self-hosted version?") [Traces displayed in the UI are 12-24 hours behind real-time](https://github.com/orgs/langfuse/discussions/9243 "Langfuse Support: Traces displayed in the UI are 12-24 hours behind real-time") [How to rollback langfuse?](https://github.com/orgs/langfuse/discussions/9181 "Langfuse Support: How to rollback langfuse?") [Traces saved to S3 but not RDS on AWS CDK deployment with latest image](https://github.com/orgs/langfuse/discussions/9175 "Langfuse Support: Traces saved to S3 but not RDS on AWS CDK deployment with latest image") [Langfuse Worker OOM kills due to low memory resource request](https://github.com/orgs/langfuse/discussions/9152 "Langfuse Support: Langfuse Worker OOM kills due to low memory resource request") [How to tell if migration is working? (And do all project keys reset when migrating to v3?)](https://github.com/orgs/langfuse/discussions/9113 "Langfuse Support: How to tell if migration is working? (And do all project keys reset when migrating to v3?)") [OpenTelemetry SSL Handshake Error](https://github.com/orgs/langfuse/discussions/9109 "Langfuse Support: OpenTelemetry SSL Handshake Error") [Support login when Keycloak/LDAP users have no valid email](https://github.com/orgs/langfuse/discussions/9036 "Langfuse Support: Support login when Keycloak/LDAP users have no valid email") [Backup of prompt table when self-hosting Langfuse](https://github.com/orgs/langfuse/discussions/9019 "Langfuse Support: Backup of prompt table when self-hosting Langfuse") ["Device or resource busy" when fetching prompt in production](https://github.com/orgs/langfuse/discussions/8868 "Langfuse Support: \"Device or resource busy\" when fetching prompt in production") [Genuine sign-in getting flagged as phishing](https://github.com/orgs/langfuse/discussions/8805 "Langfuse Support: Genuine sign-in getting flagged as phishing") [bug: connection to self-hosted langfuse is not working](https://github.com/orgs/langfuse/discussions/8796 "Langfuse Support: bug: connection to self-hosted langfuse is not working") [Bug: Error message during langfuse web startup. Cannot set property message of ZodError which has only a getter](https://github.com/orgs/langfuse/discussions/8781 "Langfuse Support: Bug: Error message during langfuse web startup. Cannot set property message of ZodError which has only a getter") [Langfuse Selfhosted Deployment containers sequence](https://github.com/orgs/langfuse/discussions/8748 "Langfuse Support: Langfuse Selfhosted Deployment containers sequence") [High Inode Usage on MinIO Backend (~8.6M files/day) Leading to Rapid Filesystem Exhaustion](https://github.com/orgs/langfuse/discussions/8713 "Langfuse Support: High Inode Usage on MinIO Backend (~8.6M files/day) Leading to Rapid Filesystem Exhaustion") [Azure self-hosted deployment SSO configuration issue](https://github.com/orgs/langfuse/discussions/8684 "Langfuse Support: Azure self-hosted deployment SSO configuration issue") [Azure deployment SSO error](https://github.com/orgs/langfuse/discussions/8679 "Langfuse Support: Azure deployment SSO error") [Local helm deployment (colima, macOS, k3s)](https://github.com/orgs/langfuse/discussions/8676 "Langfuse Support: Local helm deployment (colima, macOS, k3s)") [Really slow latency for viewing traces within a timestamp and viewing a specific trace.](https://github.com/orgs/langfuse/discussions/8675 "Langfuse Support: Really slow latency for viewing traces within a timestamp and viewing a specific trace.") [Self-Hosted docker connectivity issues](https://github.com/orgs/langfuse/discussions/8672 "Langfuse Support: Self-Hosted docker connectivity issues") [Possible to get Keycloack Realm to manage Langfuse organizations or projects](https://github.com/orgs/langfuse/discussions/8618 "Langfuse Support: Possible to get Keycloack Realm to manage Langfuse organizations or projects") [Error: Body exceeded 4.5mb limit when migrating from Langfuse Cloud to Self-hosted](https://github.com/orgs/langfuse/discussions/8614 "Langfuse Support: Error: Body exceeded 4.5mb limit when migrating from Langfuse Cloud to Self-hosted") [Backfilling traces, observations and scores on langfuse](https://github.com/orgs/langfuse/discussions/8574 "Langfuse Support: Backfilling traces, observations and scores on langfuse") [Web to Clickhouse connection issue](https://github.com/orgs/langfuse/discussions/8525 "Langfuse Support: Web to Clickhouse connection issue") [CROSSSLOT error initializing worker container](https://github.com/orgs/langfuse/discussions/8420 "Langfuse Support: CROSSSLOT error initializing worker container") [Langfuse LLM as judge stuck at Running Evaluator](https://github.com/orgs/langfuse/discussions/8388 "Langfuse Support: Langfuse LLM as judge stuck at Running Evaluator") [Will langfuse open source ever allow programmatic org/project management?](https://github.com/orgs/langfuse/discussions/8386 "Langfuse Support: Will langfuse open source ever allow programmatic org/project management?") [How to package langfuse into our own enterprise software?](https://github.com/orgs/langfuse/discussions/8381 "Langfuse Support: How to package langfuse into our own enterprise software?") [Azure deployment 404 error](https://github.com/orgs/langfuse/discussions/8345 "Langfuse Support: Azure deployment 404 error") [rate limit issue when calling evalution in aws self hosted environment.](https://github.com/orgs/langfuse/discussions/7953 "Langfuse Support: rate limit issue when calling evalution in aws self hosted environment.") [Open Source Self-Hosting Appears Unusable](https://github.com/orgs/langfuse/discussions/7890 "Langfuse Support: Open Source Self-Hosting Appears Unusable") [Help to fix the error: Max retries exceed with url: /v1/traces](https://github.com/orgs/langfuse/discussions/7867 "Langfuse Support: Help to fix the error: Max retries exceed with url: /v1/traces") [Deploying with AWS Terraform](https://github.com/orgs/langfuse/discussions/7800 "Langfuse Support: Deploying with AWS Terraform") [Unable to load from S3 on new task deployment on ECS](https://github.com/orgs/langfuse/discussions/7742 "Langfuse Support: Unable to load from S3 on new task deployment on ECS") [Langfuseweb sometimes unable to connect to clickhouse](https://github.com/orgs/langfuse/discussions/7616 "Langfuse Support: Langfuseweb sometimes unable to connect to clickhouse") [Clickhouse storage increases even when there is no activity](https://github.com/orgs/langfuse/discussions/7582 "Langfuse Support: Clickhouse storage increases even when there is no activity") [How to enable Organizations API for OSS self-hosted deployments?](https://github.com/orgs/langfuse/discussions/7512 "Langfuse Support: How to enable Organizations API for OSS self-hosted deployments?") [Langfuse on Terraform GCP without a custom domain](https://github.com/orgs/langfuse/discussions/7511 "Langfuse Support: Langfuse on Terraform GCP without a custom domain") [Langfuse Web image takes lot of time to build and fails \[3.75.1\]\]](https://github.com/orgs/langfuse/discussions/7502 "Langfuse Support: Langfuse Web image takes lot of time to build and fails [3.75.1]]") [Certificate error while calling the self hosted llm from local machine](https://github.com/orgs/langfuse/discussions/7416 "Langfuse Support: Certificate error while calling the self hosted llm from local machine") [When Langfuse traces are stored in ClickHouse, the project\_id column is available, but there is no direct mapping or column provided for the project\_name.](https://github.com/orgs/langfuse/discussions/7403 "Langfuse Support: When Langfuse traces are stored in ClickHouse, the project_id column is available, but there is no direct mapping or column provided for the project_name.") [Invalid credentials error when running langfuse & otel-collector locally](https://github.com/orgs/langfuse/discussions/7071 "Langfuse Support: Invalid credentials error when running langfuse & otel-collector locally") [Migration of Clickhouse to new location](https://github.com/orgs/langfuse/discussions/6875 "Langfuse Support: Migration of Clickhouse to new location") [Redis only supported in standalone mode?](https://github.com/orgs/langfuse/discussions/6818 "Langfuse Support: Redis only supported in standalone mode?") [Could we use Redis 6.2 instead?](https://github.com/orgs/langfuse/discussions/6708 "Langfuse Support: Could we use Redis 6.2 instead?") [ClickHouse container keeps restarting with Exit Code 210: "Operation not permitted" during system table loading](https://github.com/orgs/langfuse/discussions/6707 "Langfuse Support: ClickHouse container keeps restarting with Exit Code 210: \"Operation not permitted\" during system table loading") [Ingestion failing due to CPU wait time](https://github.com/orgs/langfuse/discussions/6666 "Langfuse Support: Ingestion failing due to CPU wait time") [Store traces and observations in postgres for downstream applications](https://github.com/orgs/langfuse/discussions/6618 "Langfuse Support: Store traces and observations in postgres for downstream applications") [Getting "Unexpected error occurred. Please check your request and contact support: https://langfuse.com/support."](https://github.com/orgs/langfuse/discussions/6526 "Langfuse Support: Getting \"Unexpected error occurred. Please check your request and contact support: https://langfuse.com/support.\"") [Background migrations stuck at Queued](https://github.com/orgs/langfuse/discussions/6335 "Langfuse Support: Background migrations stuck at Queued") [Strange behaviour between self hosted and cloud langfuse : input output null and 0 token on self hosted](https://github.com/orgs/langfuse/discussions/6238 "Langfuse Support: Strange behaviour between self hosted and cloud langfuse : input output null and 0 token on self hosted") [Upgrading self-hosted langfuse from 2 to 3](https://github.com/orgs/langfuse/discussions/6225 "Langfuse Support: Upgrading self-hosted langfuse from 2 to 3") [Batch export configuration missing in docker-compose.yml](https://github.com/orgs/langfuse/discussions/6197 "Langfuse Support: Batch export configuration missing in docker-compose.yml") [Trace does not have a timestamp, using event time](https://github.com/orgs/langfuse/discussions/6194 "Langfuse Support: Trace does not have a timestamp, using event time") [Self-Hosted Backups](https://github.com/orgs/langfuse/discussions/6156 "Langfuse Support: Self-Hosted Backups") [Data resilience options for ClickHouse component of Langfuse](https://github.com/orgs/langfuse/discussions/6133 "Langfuse Support: Data resilience options for ClickHouse component of Langfuse") [Error uploading media](https://github.com/orgs/langfuse/discussions/6081 "Langfuse Support: Error uploading media") [Leaner docker-compose.yaml file for self-hosters...](https://github.com/orgs/langfuse/discussions/6078 "Langfuse Support: Leaner docker-compose.yaml file for self-hosters...") [Langfuse 1.0.0 Helm Chart](https://github.com/orgs/langfuse/discussions/6061 "Langfuse Support: Langfuse 1.0.0 Helm Chart") [Self-Hosting LangFuse:3 with ECS, CFN, and ECS Service Connect](https://github.com/orgs/langfuse/discussions/6045 "Langfuse Support: Self-Hosting LangFuse:3 with ECS, CFN, and ECS Service Connect") [Image Deployment Issue](https://github.com/orgs/langfuse/discussions/6018 "Langfuse Support: Image Deployment Issue") [Highly available Postgres and Redis in K8s Chart](https://github.com/orgs/langfuse/discussions/5992 "Langfuse Support: Highly available Postgres and Redis in K8s Chart") [Delete traces via API](https://github.com/orgs/langfuse/discussions/5952 "Langfuse Support: Delete traces via API") [Is there a tutorial available for installing langfuse without using Docker?](https://github.com/orgs/langfuse/discussions/5930 "Langfuse Support: Is there a tutorial available for installing langfuse without using Docker?") [Hardware resource recommendations for Redis and ClickHouse](https://github.com/orgs/langfuse/discussions/5924 "Langfuse Support: Hardware resource recommendations for Redis and ClickHouse") [Is there a way to automate apiKey/apiSecret creation for new projects?](https://github.com/orgs/langfuse/discussions/5806 "Langfuse Support: Is there a way to automate apiKey/apiSecret creation for new projects?") [Self-hosted Langfuse V3 just removed the database](https://github.com/orgs/langfuse/discussions/5802 "Langfuse Support: Self-hosted Langfuse V3 just removed the database") [Requirements doubled from v2 to v3](https://github.com/orgs/langfuse/discussions/5785 "Langfuse Support: Requirements doubled from v2 to v3") [Disable Background Migrations](https://github.com/orgs/langfuse/discussions/5754 "Langfuse Support: Disable Background Migrations") [Challenges in Deploying Langfuse v3 in Active-Active Mode Using Docker Compose](https://github.com/orgs/langfuse/discussions/5692 "Langfuse Support: Challenges in Deploying Langfuse v3 in Active-Active Mode Using Docker Compose") [Langfuse V3 Self-Hosting: Deployment Options, Cost, and Scaling Considerations](https://github.com/orgs/langfuse/discussions/5669 "Langfuse Support: Langfuse V3 Self-Hosting: Deployment Options, Cost, and Scaling Considerations") [Values.yaml should contains storageClassName: