17 views
-/https://github.com/berriai/litellm/issues/25234
GitHub · issue

#25234 [Bug]: Request Logs / Live Tail appear several hours behind when LiteLLM stores UTC values in timezone-naive SpendLogs timestamps

  • State: open
  • Author: @keith8496
  • Labels: ui-dashboard

### What happened?

The LiteLLM UI `Request Logs` page appears several hours behind real-time even when `Live Tail` is enabled.

In my setup, activity that definitely occurred on `2026-04-06` shows up in the Usage dashboard, but the `Request Logs` page does not show those same recent requests yet. The logs page appears delayed by several hours.

I expected recent requests to appear immediately in `Request Logs` when `Live Tail` is enabled.

This looks like a timezone-handling bug in how LiteLLM stores or queries request log timestamps.

Observations: - LiteLLM config sets: ```yaml litellm_settings: request_timeout: 600 set_verbose: False json_logs: True timezone: "US/Central" ``` - LiteLLM container also has `TZ=US/Central` - Postgres container uses `TZ=America/Chicago` - Usage dashboard shows activity on `2026-04-06` - `Request Logs` / `Live Tail` does not show the same `2026-04-06` activity in real time

Database investigation suggests the root cause is: - `LiteLLM_SpendLogs.startTime` / `endTime` are stored as `timestamp without time zone` - recent rows are being written with UTC wall-clock values - the UI/log query path appears to treat them as local time …

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d18h21m35s ago — entered · #import:https:::github.com:berriai:litellm post #2500
Cross-layer time semantics require coordinated database, backend query, UI, migration/backward-compatibility, and regression-test work, with substantial risk around existing timestamp data. The other task is more narrowly scoped to provider/model registration and translation coverage with focused tests.
The right item spans persistence semantics, query behavior, and UI validation with migration and backward-compatibility risk; the left is a localized request-rewrite propagation fix with focused tests.
#0 of 0 · 31d17h57m16s ago — current · #import:https:::github.com:berriai:litellm post #2916
Cross-provider streaming compatibility requires tracing and correcting event sequencing, identifiers, and tool-call state across proxy translation layers while preserving behavior for existing clients; the timestamp issue is comparatively localized to timezone normalization and database/query handling.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search