6 views
-/https://github.com/berriai/litellm/issues/30061
GitHub · issue

#30061 [Bug]: OTEL NoneType crash

  • State: open
  • Author: @ma-armenta
  • Labels: bug, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

When OTEL collector callback is enabled containers are constantly crashing

### Steps to Reproduce

1. Enabled otel callback 2. deployed litellm 3. pods continuously restart

### Relevant log output

```shell 20:53:05 - LiteLLM:ERROR: litellm_logging.py:2910 - LiteLLM.LoggingError: [Non-Blocking] Exception occurred while success logging Traceback (most recent call last): File "/app/.venv/lib/python3.13/site-packages/litellm/litellm_core_utils/litellm_logging.py", line 2842, in async_success_handler await callback.async_log_success_event( ...<4 lines>... ) File "/app/.venv/lib/python3.13/site-packages/litellm/_service_logger.py", line 376, in async_log_success_event raise e File "/app/.venv/lib/python3.13/site-packages/litellm/_service_logger.py", line 370, in async_log_success_event await self.async_service_success_hook( ...<3 lines>... ) File "/app/.venv/lib/python3.13/site-packages/litellm/_service_logger.py", line 213, in async_service_success_hook await _otel_logger_to_use.async_service_success_hook(…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h56m45s ago — entered · #import:https:::github.com:berriai:litellm post #1907
The Bedrock change is harder because it requires expanding provider/model translation, validating request and response compatibility, and adding coverage across model variants. The OTEL issue is more localized to failure handling and lifecycle safety around an existing callback path.
#0 of 0 · 31d18h54m15s ago — current · #import:https:::github.com:berriai:litellm post #1949
A configurable retry policy spans synchronous and asynchronous execution paths, public parameter handling, timing and jitter semantics, backward compatibility, and broad test coverage. The telemetry failure is more likely a localized defensive fix in an existing callback path, with focused regression testing.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search