tPj"$UdZddlZddlmZmZddlmZmZddlmZm Z m Z ddl m Z ddl mZddlmZmZdd lmZdd lmZmZmZmZed d g Zeed<GddZej;de ege efdededefdZy)uJ Ingest pre-built logging payloads from external producers and replay them through LiteLLM's standard success/failure callback fan-out. This exists for hosts that own a request outside the Python process — e.g. the `litellm-rust` gateway proxying realtime websockets. Those hosts can't use the in-process logging object, so they POST a finished `StandardLoggingPayload` here and Python replays it through the exact same path a normal completion uses: `Logging.async_success_handler` / `async_failure_handler`. Every registered callback (spend logs, Langfuse, Datadog, ...) fires unchanged — there is no spend-logs-specific or callback-specific code here, only the replay. The endpoint is generic: realtime is the first producer, but the contract is the self-describing `StandardLoggingPayload`, so completions/responses can use it too. N)datetimetimezone)AnyFinal) APIRouterDepends HTTPException)verbose_proxy_logger)Logging)LitellmUserRolesUserAPIKeyAuth)user_api_key_auth)CallbackLogFailureCallbackLogRecordCallbackLogsRequestCallbackLogsResponsez/v1/rust_control_planezrust control plane)prefixtagsrust_control_plane_routerceZdZdZededefdZedee efde fdZ edee efdee effdZ de dd fd Zd ee defd Zy ) CallbackLogsReplayeru~ Replays finished logging payloads through LiteLLM's callback fan-out. Each helper is small and pure so the replay path is easy to read and test: rebuild a `Logging` object from the payload, seed `model_call_details` with exactly what the callbacks read, then dispatch to the success/failure handler. No spend/callback logic lives here — only the replay. valuereturnct|ttfr.tjt|t j St|tr|Stjt j S)zI`StandardLoggingPayload` stores startTime/endTime as float epoch seconds.)tz) isinstanceintfloatr fromtimestamprutcnow)rs |/home/oem/CyberBrain26-unified/.venv/lib/python3.12/site-packages/litellm/proxy/logging_endpoints/callback_logs_endpoints.py_epoch_to_datetimez'CallbackLogsReplayer._epoch_to_datetime2sO ec5\ *))%,8<<H H eX &L||x||,,payloadc 6|jdxsd}|jdxsd}tj|jd}|jdxs0|jdxstt j }t ||jdxsgd |||d }|jd xsi}|jd |jd |jd|jd|jd|jd|jdd}|jj|||jd|jdxsd|d |i|jdxsd d|S)a Reconstruct a `Logging` object from a finished payload and seed `model_call_details` with exactly what the success/failure callbacks read: the prebuilt `standard_logging_object`, the resolved `response_cost`, and the `litellm_params.metadata` keys used for cost attribution. Setting `standard_logging_object` up front makes the handler skip rebuilding it. model call_type acompletion startTimelitellm_call_ididmessagesF)r'r.streamr) start_timer, function_idmetadatauser_api_key_hashuser_api_key_aliasuser_api_key_user_iduser_api_key_team_iduser_api_key_org_iduser_api_key_end_user_idspend_logs_metadata) user_api_keyr4r5r6r7r8r9custom_llm_provider response_costg cache_hit)r'r)r;r<standard_logging_objectlitellm_paramsr=) getrr#struuiduuid4LiteLLMLoggingmodel_call_detailsupdate)r%r'r)r0call_id logging_objr2litellm_metadatas r"_build_logging_objz'CallbackLogsReplayer._build_logging_obj;s{{7+1r";;{3D} 0CCGKKP[D\]  %67a7;;t;LaPSTXT^T^T`Pa+[[,2!# +2++j*A*GR$LL)<="*,,/C"D$,LL1G$H$,LL1G$H#+<<0E#F(0 5O(P#+<<0E#F3  &&--&'.{{3H'I!(_!=!D+2#-/?"@$[[5>  r$c|jd|jdd|jdd|jddddS)zBMinimal response object so usage-derived spend-log fields resolve.r- prompt_tokensrcompletion_tokens total_tokens)rLrMrN)r-usage)r@)r%s r"_response_obj_from_payloadz/CallbackLogsReplayer._response_obj_from_payloadrsJ++d#!(_a!@%,[[1Da%H ' NA >  r$recordNc vK|j}tjd|j|j d|j d|j d|j |}|j |j d}|j |j d}|jdk(r,|j|j|||d {y |jxs|j d xsd }|jt|d || d {y 7O7w)z?Replay one record through the matching success/failure handler.zECallbackLogsReplayer: replaying %s record id=%s model=%s call_type=%sr-r'r)r+endTimesuccess)resultr0end_timeN error_strzreplayed failurer()traceback_exceptionr0rV) standard_logging_payloadr debugstatusr@rJr#async_success_handlerrPerrorasync_failure_handler Exception)selfrQr%rHr0rVrWs r"replayzCallbackLogsReplayer.replay~s&88"" S MM KK  KK KK $  "44W=  33GKK 4LM 11'++i2HI ==I %3366w?%!4   &||]w{{;/G]K]I33)$$&%! 4    s%C#D9%D5&A D9/D70D97D9recordsc Kd}g}t|D]$\}} |j|d{|dz }&t jd|t|t|t||S7B#t$rO}|jt |t |t jd|t |Yd}~d}~wwxYww)zReplay a batch; a single bad record never sinks the rest. Each failure is reported back with its batch index so the caller can retry/triage it.rN)indexr]z4CallbackLogsReplayer: failed to replay record %s: %sz7CallbackLogsReplayer: batch done processed=%s failed=%s) processedfailedfailures) enumeraterar_appendrrAr exceptionrZlenr)r`rbrfrhrerQes r" replay_batchz!CallbackLogsReplayer.replay_batchs 46&w/ ME6 kk&)))Q   "" E  M $iH X`aa*  2c!f MN$..JF s>C A2A0 A29C 0A22 C ;ACC C  C )__name__ __module__ __qualname____doc__ staticmethodrrr#dictrArDrJrPrralistrrnr$r"rr(s-#-(--4DcN4~44l  DcN  tCH~    #4<b$/@*AbFZbr$rz/logs) dependenciesbodyuser_api_key_dictrcK|jtjk7r tddt j |j d{S7w)z Replay a batch of finished logging payloads through the callback fan-out. Admin-only: the payloads write spend logs and trigger every callback, so this is a trusted internal route, not a public surface. izE/v1/rust_control_plane/logs is admin-only (proxy admin key required).) status_codedetailN) user_roler PROXY_ADMINr rrnrb)rxrys r"ingest_callback_logsrsP""&6&B&BBZ  &'44T\\B BB BsAAAA)rrrBrrtypingrrfastapirrr litellm._loggingr *litellm.litellm_core_utils.litellm_loggingr rDlitellm.proxy._typesr r $litellm.proxy.auth.user_api_key_authr+litellm.types.proxy.callback_logs_endpointsrrrrr__annotations__rpostrrvr$r"rs  '551PAB$-4LThSi#j5jIbIbX +,-  )00A(BC C%CC Cr$