Feature Request: Support per-component Langfuse configuration (without global environment variables)

[flefevre]

Hi Langflow team,

First of all — thanks for the fantastic work on Langflow and the integrations with Langfuse! The current setup makes it very easy to trace flows to Langfuse by passing the required keys as environment variables.

I have a feature request regarding the Langfuse observability integration:

🚀 Problem

At the moment, Langflow’s Langfuse integration requires the API keys (LANGFUSE_SECRET_KEY, LANGFUSE_PUBLIC_KEY, LANGFUSE_HOST, etc.) to be set as global environment variables before starting the Langflow server. ([Langflow Documentation]1)

However, in more complex scenarios — for example multi-tenant workflows, multiple Langfuse projects, or different trace destinations depending on the LLM component — it would be very helpful to configure Langfuse per component (LLM/chain) instead of only at the server level.

In other words:

• A way to pass Langfuse keys and trace config directly in the LLM/chain node itself, instead of only using environment variables for the entire server.
• This would allow dispatching traces to different Langfuse projects (or different configurations) depending on the component or use case.

❓ Use Cases

1. Multi-tenant deployments — where each tenant should get tracing in their own Langfuse project.
2. Dynamic trace routing — send debug traces to staging Langfuse project and production traces to another.
3. Fine-grained control — set sampling rate, metadata, and API keys per model invocation/component.

❓ Is this feasible?

I’m curious to know:

• Is there a plan to support per-component Langfuse configuration?
• Would the maintainers consider adding this as a feature?
• If not, what would be the recommended way to implement this currently?

Thanks in advance 🙏

Si tu veux, je peux aussi t’aider à créér le même texte adapté pour “Issues” ou “Discussion” sur GitHub avec les labels suggérés (ex. enhancement, help wanted, question).