Pulled latest version but still dont see the newer models

[Hamma111]

Describe your question

I self hosted langfuse about 6 months back. Here is what I have done so far

1. Pulled the latest code from github
2. ran docker compose up --build
3. migrated the DB docker compose exec langfuse-worker pnpm run db:migrate

However, I am unable to see newer models in my frontend UI, and I also dont see them in my DB as well when I run

SELECT name, price_input, price_output
FROM models
ORDER BY created_at DESC;

I could not find links to relevant issues. Is there way to be able to get the latest modes as well when upgrading to newer langfuse version?

Langfuse Cloud or Self-Hosted?

Self-Hosted

If Self-Hosted

latest version. v3.147.0,

And version I was previously using: v3.122.0

If Langfuse Cloud

No response

SDK and integration versions

No response

Pre-Submission Checklist

• I have checked for existing issues/discussions and consulted Langfuse AI.

[inkeep-ai-assistant[bot]]

Based on the available sources, when you upgrade Langfuse, new model definitions are included in the updated version but are only applied to newly ingested traces/generations by default(1).

To apply new model definitions and prices to your existing historical data, you need to run a specific migration command(1):

pnpm run models:migrate

(1)

However, this command needs to be run from within the Langfuse repository with proper database configuration(1). Here are the steps:

1. Clone the repository and navigate to it(1)
2. Create an .env file with your database connection string(1):

NODE_ENV=production

# Replace with your database connection string
DATABASE_URL=postgresql://postgres:postgres@localhost:5432/postgres

(1)

3. Install dependencies with pnpm i(1)
4. Execute the migration: pnpm run models:migrate(1)

This migration will apply the new model logic and prices to existing data in your database(1). The process is non-blocking and doesn't impact availability(1).

After running this migration, you should see the newer models reflected in both your UI and database queries.

Important: Make sure to remove the .env file after the migration to avoid connecting to the production database from your local machine(1).

📚 Sources:

1. Migrate Langfuse v1 to v2

---

Have another question? Just tag @inkeep.

[Hamma111]

this does not help as I am not migrating from v1 to v2

[Hamma111]

cc @inkeep

[inkeep-ai-assistant[bot]]

I understand the confusion. While the documentation I referenced is titled "v1 to v2," the pnpm run models:migrate command applies to any version upgrade where new models are added(1).

The key point is that when Langfuse includes support for new models in any update, these new model definitions are only applied to newly ingested traces by default(1). To apply them to existing data (which would also populate your models table), you need to run the models migration command(1).

Since you're on v3.147.0 (upgraded from v3.122.0), the same migration process applies:

1. Clone the Langfuse repository(1)
2. Create an .env file with your database connection(1):

NODE_ENV=production
DATABASE_URL=postgresql://postgres:postgres@localhost:5432/postgres

(1)

3. Run pnpm i(1)
4. Execute pnpm run models:migrate(1)

This migration is non-blocking and will populate your database with the newer model definitions that were added between v3.122.0 and v3.147.0(1).

If this approach doesn't resolve your issue, there may be a different problem with how the models are being loaded or displayed in your specific setup that isn't covered in the available documentation.

📚 Sources:

1. Migrate Langfuse v1 to v2

---

Have another question? Just tag @inkeep.