Issue: Incorrect name Field in Langfuse Observations When Calling via ClaudeCode (Local Setup with LiteLLM Integration)

[chunxiao365]

Describe your question

I am running ClaudeCode locally and connecting it to LiteLLM, which is integrated with Langfuse.
When making calls through the OpenAI-compatible interface, the name field in Langfuse Observations correctly logs as litellm:realname.
However, when invoking via ClaudeCode, the name field fails to capture the correct value and only logs the default litellm:name.

Langfuse Cloud or Self-Hosted?

Self-Hosted

If Self-Hosted

v3.47.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 your setup with ClaudeCode → LiteLLM → Langfuse, the issue with the name field in observations appears to be related to how metadata is being passed through the integration chain(1).

When using LiteLLM Proxy with Langfuse, you can add additional Langfuse attributes to requests to customize trace attributes(1). The LiteLLM integration supports passing metadata with a langfuse_* prefix in request headers(1).

For your specific issue where the name field shows only litellm:name instead of the expected value when calling via ClaudeCode, you should verify that:

1. Metadata is being passed correctly - LiteLLM Proxy allows you to add Langfuse attributes through request metadata(1). Ensure ClaudeCode is passing the appropriate metadata fields.

2. Environment variables are configured - For the LiteLLM Proxy integration, you need these environment variables set(1):

export LANGFUSE_PUBLIC_KEY="pk-lf-..."
export LANGFUSE_SECRET_KEY="sk-lf-..."
export LANGFUSE_OTEL_HOST="https://us.cloud.langfuse.com"

(1)

3. LiteLLM callback is enabled - Your litellm_config.yaml should have(1):

litellm_settings:
 callbacks: ["langfuse_otel"]

(1)

Since you're on self-hosted Langfuse v3.47.0, this version should support the LiteLLM integration. However, the specific behavior of the name field when routing through ClaudeCode may require additional configuration in how ClaudeCode passes metadata to LiteLLM.

You can find detailed information on adding Langfuse attributes through LiteLLM in both the LiteLLM Proxy docs and LiteLLM Python SDK docs as referenced in the integration documentation(1).

📚 Sources:

1. LiteLLM Proxy Integration

---

Have another question? Just tag @inkeep.

[chunxiao365]

it doesn't work

[jannikmaierhoefer]

Hi @chunxiao365 are you using our Claude Code integration? https://langfuse.com/integrations/other/claude-code

[chunxiao365]

no,I am using litellm as proxy,which integreated with langfuse.