litellm - 💡(How to fix) Fix [Bug]: Langfuse logging stopped working on its own on v1.81.16 [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#23034Fetched 2026-04-08 00:38:44
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Timeline (top)
labeled ×3renamed ×2

Error Message

2026-03-07T10:23:07.958154483Z Unexpected error occurred. Please check your request and contact support: https://langfuse.com/support. 2026-03-07T10:52:02.593399783Z Unexpected error occurred. Please check your request and contact support: https://langfuse.com/support.

Code Example

Looking at the logs:

1. `sudo docker logs litellm --timestamps | grep -C 5 langfuse` when not in DEBUG log shows:

2026-03-07T10:23:04.400439529Z Initialized litellm callbacks, Async Success Callbacks: [<bound method Router.deployment_callback_on_success of <litellm.router.Router object at 0x75b384cde270>>, <litellm.proxy.hooks.proxy_track_cost_callback._ProxyDBLogger object at 0x75b3849c1f90>, <litellm.integrations.langfuse.langfuse_prompt_management.LangfusePromptManagement object at 0x75b3849c5be0>, <litellm.proxy.hooks.litellm_skills.main.SkillsInjectionHook object at 0x75b38a41c6e0>, <litellm.proxy.hooks.model_max_budget_limiter._PROXY_VirtualKeyModelMaxBudgetLimiter object at 0x75b3874d86e0>, <litellm.proxy.hooks.max_budget_limiter._PROXY_MaxBudgetLimiter object at 0x75b38331d6d0>, <litellm.proxy.hooks.parallel_request_limiter_v3._PROXY_MaxParallelRequestsHandler_v3 object at 0x75b383929550>, <litellm.proxy.hooks.cache_control_check._PROXY_CacheControlCheck object at 0x75b38331e350>, <litellm.proxy.hooks.responses_id_security.ResponsesIDSecurity object at 0x75b3839296a0>, <litellm_enterprise.proxy.hooks.managed_files._PROXY_LiteLLMManagedFiles object at 0x75b3839297f0>, <litellm_enterprise.proxy.hooks.managed_vector_stores._PROXY_LiteLLMManagedVectorStores object at 0x75b383929940>, <litellm._service_logger.ServiceLogging object at 0x75b38748d810>]
2026-03-07T10:23:04.400460454Z Final returned optional params: {'stream': True, 'stream_options': {'include_usage': True}, 'max_retries': 0, 'extra_body': {}}
2026-03-07T10:23:04.400475264Z INFO:     172.19.0.1:55630 - "POST /chat/completions HTTP/1.1" 200 OK
2026-03-07T10:31:58.226163580Z Logging Details LiteLLM-Async Success Call, cache_hit=False
2026-03-07T10:31:58.226241456Z Async success callbacks: Got a complete streaming response
2026-03-07T10:31:58.226248573Z INFO:     172.19.0.1:51726 - "GET /v1/models HTTP/1.1" 200 OK
2026-03-07T10:23:07.958154483Z Unexpected error occurred. Please check your request and contact support: https://langfuse.com/support.


2. In DEBUG mode it's not really more informative:

2026-03-07T10:52:00.014672387Z 11:52:00 - LiteLLM Proxy:DEBUG: daily_spend_update_queue.py:94 - Aggregated daily spend update transactions: {'User-Agent: OpenAI_2026-03-07_9d
REDACTEDopenrouter/anthropic/claude-sonnet-4.6_openrouter_/chat/completions': {'tag': 'User-Agent: OpenAI', 'date': '20
26-03-07', 'api_key': 'REDACTED', 'model': 'openrouter/anthropic/claude-sonnet-4.6', 'model_group': 'litellm_oli_best'
, 'mcp_namespaced_tool_name': None, 'custom_llm_provider': 'openrouter', 'endpoint': '/chat/completions', 'prompt_tokens': 11, 'completion_tokens': 26, 'spend': 0.0, 'api_req
uests': 1, 'successful_requests': 1, 'failed_requests': 0, 'cache_read_input_tokens': 0, 'cache_creation_input_tokens': 0, 'request_id': 'gen-1772880717-54Kfdpk2t6kf3iRuVUx6'
}, 'User-Agent: OpenAI/Python 2.21.0_2026-03-REDACTED/anthropic/claude-sonnet-4.6_openrouter_/chat/compl
etions': {'tag': 'User-Agent: OpenAI/Python 2.21.0', 'date': '2026-03-07', 'api_key': 'REDACTED', 'model': 'openrouter
/anthropic/claude-sonnet-4.6', 'model_group': 'litellm_oli_best', 'mcp_namespaced_tool_name': None, 'custom_llm_provider': 'openrouter', 'endpoint': '/chat/completions', 'pro
mpt_tokens': 11, 'completion_tokens': 26, 'spend': 0.0, 'api_requests': 1, 'successful_requests': 1, 'failed_requests': 0, 'cache_read_input_tokens': 0, 'cache_creation_input
_tokens': 0, 'request_id': 'gen-1772880717-54KfVUx6'}}
2026-03-07T10:52:00.014711296Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1155 - Daily Tag Spend transactions: 2
2026-03-07T10:52:00.028247156Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1318 - Processed 2 daily tag transactions in 0.01s
2026-03-07T10:52:00.028288900Z 11:52:00 - LiteLLM Proxy:DEBUG: daily_spend_update_queue.py:94 - Aggregated daily spend update transactions: {}
2026-03-07T10:52:00.028296541Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1155 - Daily End_user Spend transactions: 0
2026-03-07T10:52:00.028302861Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1188 - No new transactions to process for daily end_user spend update
2026-03-07T10:52:00.028323848Z 11:52:00 - LiteLLM Proxy:DEBUG: daily_spend_update_queue.py:94 - Aggregated daily spend update transactions: {}
2026-03-07T10:52:00.028351476Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1155 - Daily Agent Spend transactions: 0
2026-03-07T10:52:00.028359949Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1188 - No new transactions to process for daily agent spend update
2026-03-07T10:52:00.028393202Z 11:52:00 - LiteLLM Proxy:DEBUG: utils.py:4285 - Spend Logs transactions: 1
2026-03-07T10:52:00.044277346Z 11:52:00 - LiteLLM Proxy:DEBUG: utils.py:4216 - Flushed 1 logs to the DB.
2026-03-07T10:52:00.044326102Z 11:52:00 - LiteLLM Proxy:DEBUG: utils.py:4225 - 1 logs processed. Remaining in queue: 0
2026-03-07T10:52:02.593399783Z Unexpected error occurred. Please check your request and contact support: https://langfuse.com/support.
2026-03-07T10:52:03.957824904Z 11:52:03 - LiteLLM Proxy:DEBUG: spend_update_queue.py:34 - Aggregating updates by entity type: []
2026-03-07T10:52:03.957882154Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:720 - User Spend transactions: {}
2026-03-07T10:52:03.957891450Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:763 - End-User Spend transactions: {}
2026-03-07T10:52:03.957900465Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:778 - KEY Spend transactions: {}
2026-03-07T10:52:03.957906170Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:819 - Team Spend transactions: {}
2026-03-07T10:52:03.957911263Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:867 - Team Membership Spend transactions: {}
2026-03-07T10:52:03.957935638Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:935 - Org Spend transactions: {}
2026-03-07T10:52:03.957982836Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1014 - Tag Spend transactions: {}



I see a few lines like this:

2026-03-07T10:52:16.975707533Z 11:52:16 - LiteLLM Proxy:DEBUG: proxy_server.py:4052 - param_name=general_settings, param_value={'salt_key': 'sk-mlj', 'master_key': 's', 'database_url': 'pogr2', 'store_model_in_db': 'T
rue', 'proxy_batch_write_at': 1, 'database_connection_pool_limit': 50, 'proxy_budget_rescheduler_max_time': 64, 'proxy_budget_rescheduler_min_time': 60}
2026-03-07T10:52:16.975772629Z 11:52:16 - LiteLLM Proxy:DEBUG: proxy_server.py:4052 - param_name=litellm_settings, param_value={'telemetry': True, 'drop_params': True, 'num_r
etries': 5, 'set_verbose': True, 'request_timeout': 600, 'failure_callback': ['langfuse'], 'success_callback': ['langfuse']}
2026-03-07T10:52:16.975779986Z 11:52:16 - LiteLLM Proxy:DEBUG: proxy_server.py:4052 - param_name=environment_variables, param_value={'LANGFUSE_HOST': 'REDACTED', 'LANGFUSE_PUBLIC_KEY': 'REDACTED', 'LANGFUSE_SECRET_KEY': 'REDACTED'}
2026-03-07T10:52:19.958743531Z 11:52:19 - LiteLLM Proxy:DEBUG: spend_update_queue.py:34 - Aggregating updates by entity type: []
2026-03-07T10:52:19.958786802Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:720 - User Spend transactions: {}
2026-03-07T10:52:19.958795241Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:763 - End-User Spend transactions: {}
2026-03-07T10:52:19.958822536Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:778 - KEY Spend transactions: {}
2026-03-07T10:52:19.958849480Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:819 - Team Spend transactions: {}
2026-03-07T10:52:19.958885029Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:867 - Team Membership Spend transactions: {}
2026-03-07T10:52:19.958911492Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:935 - Org Spend transactions: {}
2026-03-07T10:52:19.958941864Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1014 - Tag Spend transactions: {}
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

A bug happened!

As you can see in langfuse, the logging stopped to 0 on the 26 of february:

<img width="869" height="447" alt="Image" src="https://github.com/user-attachments/assets/c3c1ba53-ed99-48e0-a731-fbb2d6c94710" />

As we can see, it's the date of release of 1.81.16

<img width="865" height="384" alt="Image" src="https://github.com/user-attachments/assets/de58b1a3-928b-47c6-891c-2ddf1f586394" />

Langfuse was not updated at that time:

<img width="861" height="513" alt="Image" src="https://github.com/user-attachments/assets/609ac15c-37cc-47c2-806c-39dbb0fca9ff" />
  • I have not changed my configuration since (I use git so I was able to definitively check).
  • I'm using watchtower to automatically update my containers btw.
  • I checked that it was not a networking issue (using curl from the litellm container to the langfuse container worked fine)
  • sadly it seems that reverting to v1.81.14-stable does not resolve the issue.

edit: I connected to the UI and saw that the langfuse callback was failing. I used the UI to set the secret, public and host values of langfuse from the env var. Now the callback test says "Success" but I still don't see the trace appearing in langfuse.

In any case:

  • If the UI can get out of sync with the ENV values, it's a bug
  • if the logging (in or out of DEBUG log level) cannot write explicitely that the callback is failing, that a bug too.

Edit2: I was using the image ghcr.io/berriai/litellm:main-latest and now switched to ghcr.io/berriai/litellm:main-stable and notice that it works. I don't know if it's the changing of container or something to do with callbacks etc but now it indeed logs to my self hosted langfuse.


Steps to Reproduce

  1. Upgrade from 1.81.15 to 1.81.16 apparently
  2. Not doing anything else in particular

Relevant log output

Looking at the logs:

1. `sudo docker logs litellm --timestamps | grep -C 5 langfuse` when not in DEBUG log shows:

2026-03-07T10:23:04.400439529Z Initialized litellm callbacks, Async Success Callbacks: [<bound method Router.deployment_callback_on_success of <litellm.router.Router object at 0x75b384cde270>>, <litellm.proxy.hooks.proxy_track_cost_callback._ProxyDBLogger object at 0x75b3849c1f90>, <litellm.integrations.langfuse.langfuse_prompt_management.LangfusePromptManagement object at 0x75b3849c5be0>, <litellm.proxy.hooks.litellm_skills.main.SkillsInjectionHook object at 0x75b38a41c6e0>, <litellm.proxy.hooks.model_max_budget_limiter._PROXY_VirtualKeyModelMaxBudgetLimiter object at 0x75b3874d86e0>, <litellm.proxy.hooks.max_budget_limiter._PROXY_MaxBudgetLimiter object at 0x75b38331d6d0>, <litellm.proxy.hooks.parallel_request_limiter_v3._PROXY_MaxParallelRequestsHandler_v3 object at 0x75b383929550>, <litellm.proxy.hooks.cache_control_check._PROXY_CacheControlCheck object at 0x75b38331e350>, <litellm.proxy.hooks.responses_id_security.ResponsesIDSecurity object at 0x75b3839296a0>, <litellm_enterprise.proxy.hooks.managed_files._PROXY_LiteLLMManagedFiles object at 0x75b3839297f0>, <litellm_enterprise.proxy.hooks.managed_vector_stores._PROXY_LiteLLMManagedVectorStores object at 0x75b383929940>, <litellm._service_logger.ServiceLogging object at 0x75b38748d810>]
2026-03-07T10:23:04.400460454Z Final returned optional params: {'stream': True, 'stream_options': {'include_usage': True}, 'max_retries': 0, 'extra_body': {}}
2026-03-07T10:23:04.400475264Z INFO:     172.19.0.1:55630 - "POST /chat/completions HTTP/1.1" 200 OK
2026-03-07T10:31:58.226163580Z Logging Details LiteLLM-Async Success Call, cache_hit=False
2026-03-07T10:31:58.226241456Z Async success callbacks: Got a complete streaming response
2026-03-07T10:31:58.226248573Z INFO:     172.19.0.1:51726 - "GET /v1/models HTTP/1.1" 200 OK
2026-03-07T10:23:07.958154483Z Unexpected error occurred. Please check your request and contact support: https://langfuse.com/support.


2. In DEBUG mode it's not really more informative:

2026-03-07T10:52:00.014672387Z 11:52:00 - LiteLLM Proxy:DEBUG: daily_spend_update_queue.py:94 - Aggregated daily spend update transactions: {'User-Agent: OpenAI_2026-03-07_9d
REDACTEDopenrouter/anthropic/claude-sonnet-4.6_openrouter_/chat/completions': {'tag': 'User-Agent: OpenAI', 'date': '20
26-03-07', 'api_key': 'REDACTED', 'model': 'openrouter/anthropic/claude-sonnet-4.6', 'model_group': 'litellm_oli_best'
, 'mcp_namespaced_tool_name': None, 'custom_llm_provider': 'openrouter', 'endpoint': '/chat/completions', 'prompt_tokens': 11, 'completion_tokens': 26, 'spend': 0.0, 'api_req
uests': 1, 'successful_requests': 1, 'failed_requests': 0, 'cache_read_input_tokens': 0, 'cache_creation_input_tokens': 0, 'request_id': 'gen-1772880717-54Kfdpk2t6kf3iRuVUx6'
}, 'User-Agent: OpenAI/Python 2.21.0_2026-03-REDACTED/anthropic/claude-sonnet-4.6_openrouter_/chat/compl
etions': {'tag': 'User-Agent: OpenAI/Python 2.21.0', 'date': '2026-03-07', 'api_key': 'REDACTED', 'model': 'openrouter
/anthropic/claude-sonnet-4.6', 'model_group': 'litellm_oli_best', 'mcp_namespaced_tool_name': None, 'custom_llm_provider': 'openrouter', 'endpoint': '/chat/completions', 'pro
mpt_tokens': 11, 'completion_tokens': 26, 'spend': 0.0, 'api_requests': 1, 'successful_requests': 1, 'failed_requests': 0, 'cache_read_input_tokens': 0, 'cache_creation_input
_tokens': 0, 'request_id': 'gen-1772880717-54KfVUx6'}}
2026-03-07T10:52:00.014711296Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1155 - Daily Tag Spend transactions: 2
2026-03-07T10:52:00.028247156Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1318 - Processed 2 daily tag transactions in 0.01s
2026-03-07T10:52:00.028288900Z 11:52:00 - LiteLLM Proxy:DEBUG: daily_spend_update_queue.py:94 - Aggregated daily spend update transactions: {}
2026-03-07T10:52:00.028296541Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1155 - Daily End_user Spend transactions: 0
2026-03-07T10:52:00.028302861Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1188 - No new transactions to process for daily end_user spend update
2026-03-07T10:52:00.028323848Z 11:52:00 - LiteLLM Proxy:DEBUG: daily_spend_update_queue.py:94 - Aggregated daily spend update transactions: {}
2026-03-07T10:52:00.028351476Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1155 - Daily Agent Spend transactions: 0
2026-03-07T10:52:00.028359949Z 11:52:00 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1188 - No new transactions to process for daily agent spend update
2026-03-07T10:52:00.028393202Z 11:52:00 - LiteLLM Proxy:DEBUG: utils.py:4285 - Spend Logs transactions: 1
2026-03-07T10:52:00.044277346Z 11:52:00 - LiteLLM Proxy:DEBUG: utils.py:4216 - Flushed 1 logs to the DB.
2026-03-07T10:52:00.044326102Z 11:52:00 - LiteLLM Proxy:DEBUG: utils.py:4225 - 1 logs processed. Remaining in queue: 0
2026-03-07T10:52:02.593399783Z Unexpected error occurred. Please check your request and contact support: https://langfuse.com/support.
2026-03-07T10:52:03.957824904Z 11:52:03 - LiteLLM Proxy:DEBUG: spend_update_queue.py:34 - Aggregating updates by entity type: []
2026-03-07T10:52:03.957882154Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:720 - User Spend transactions: {}
2026-03-07T10:52:03.957891450Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:763 - End-User Spend transactions: {}
2026-03-07T10:52:03.957900465Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:778 - KEY Spend transactions: {}
2026-03-07T10:52:03.957906170Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:819 - Team Spend transactions: {}
2026-03-07T10:52:03.957911263Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:867 - Team Membership Spend transactions: {}
2026-03-07T10:52:03.957935638Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:935 - Org Spend transactions: {}
2026-03-07T10:52:03.957982836Z 11:52:03 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1014 - Tag Spend transactions: {}



I see a few lines like this:

2026-03-07T10:52:16.975707533Z 11:52:16 - LiteLLM Proxy:DEBUG: proxy_server.py:4052 - param_name=general_settings, param_value={'salt_key': 'sk-mlj', 'master_key': 's', 'database_url': 'pogr2', 'store_model_in_db': 'T
rue', 'proxy_batch_write_at': 1, 'database_connection_pool_limit': 50, 'proxy_budget_rescheduler_max_time': 64, 'proxy_budget_rescheduler_min_time': 60}
2026-03-07T10:52:16.975772629Z 11:52:16 - LiteLLM Proxy:DEBUG: proxy_server.py:4052 - param_name=litellm_settings, param_value={'telemetry': True, 'drop_params': True, 'num_r
etries': 5, 'set_verbose': True, 'request_timeout': 600, 'failure_callback': ['langfuse'], 'success_callback': ['langfuse']}
2026-03-07T10:52:16.975779986Z 11:52:16 - LiteLLM Proxy:DEBUG: proxy_server.py:4052 - param_name=environment_variables, param_value={'LANGFUSE_HOST': 'REDACTED', 'LANGFUSE_PUBLIC_KEY': 'REDACTED', 'LANGFUSE_SECRET_KEY': 'REDACTED'}
2026-03-07T10:52:19.958743531Z 11:52:19 - LiteLLM Proxy:DEBUG: spend_update_queue.py:34 - Aggregating updates by entity type: []
2026-03-07T10:52:19.958786802Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:720 - User Spend transactions: {}
2026-03-07T10:52:19.958795241Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:763 - End-User Spend transactions: {}
2026-03-07T10:52:19.958822536Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:778 - KEY Spend transactions: {}
2026-03-07T10:52:19.958849480Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:819 - Team Spend transactions: {}
2026-03-07T10:52:19.958885029Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:867 - Team Membership Spend transactions: {}
2026-03-07T10:52:19.958911492Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:935 - Org Spend transactions: {}
2026-03-07T10:52:19.958941864Z 11:52:19 - LiteLLM Proxy:DEBUG: db_spend_update_writer.py:1014 - Tag Spend transactions: {}

What part of LiteLLM is this about?

Proxy

What LiteLLM version are you on ?

v1.81.16

Twitter / LinkedIn details

No response

extent analysis

Fix Plan

To resolve the issue with logging stopping after upgrading to v1.81.16, follow these steps:

  • Downgrade to a stable version: The user has already tried downgrading to v1.81.14-stable without success. However, switching to ghcr.io/berriai/litellm:main-stable resolved the issue.
  • Verify environment variables: Ensure that the environment variables LANGFUSE_HOST, LANGFUSE_PUBLIC_KEY, and LANGFUSE_SECRET_KEY are set correctly.
  • Update Langfuse configuration: Use the UI to set the secret, public, and host values of Langfuse from the environment variables.

Example code to set environment variables:

import os

os.environ['LANGFUSE_HOST'] = 'your_langfuse_host'
os.environ['LANGFUSE_PUBLIC_KEY'] = 'your_langfuse_public_key'
os.environ['LANGFUSE_SECRET_KEY'] = 'your_langfuse_secret_key'

Verification

To verify that the fix worked:

  1. Check the logs for any errors related to Langfuse.
  2. Test the Langfuse callback using the UI.
  3. Verify that logging is working as expected.

Extra Tips

  • Ensure that the litellm_settings parameter failure_callback and success_callback are set to ['langfuse'].
  • Check the proxy_server.py logs for any errors related to Langfuse configuration.
  • If issues persist, try resetting the Langfuse configuration to its default values.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix [Bug]: Langfuse logging stopped working on its own on v1.81.16 [1 participants]