Allow DB fallback for failure metadata enrichment lookups

Accurate logging is more important than avoiding the rare DB lookup
on the async failure path. Remove check_cache_only=True so lookups
fall back to DB when the key/team is not in cache.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
yuneng-jiang 2026-02-24 19:43:55 -08:00 committed by Sameer Kankute
parent 64d88f7d53
commit 02134a07bb

View file

@ -263,7 +263,7 @@ class _ProxyDBLogger(CustomLogger):
async def _enrich_failure_metadata_with_key_info(metadata: dict) -> dict:
"""
Enriches failure spend log metadata by looking up the key object (and team object)
from cache when key fields are missing.
from cache/DB when key fields are missing.
This handles two scenarios:
1. Auth errors (401): UserAPIKeyAuth is created with only api_key set, all other
@ -291,7 +291,6 @@ class _ProxyDBLogger(CustomLogger):
prisma_client=prisma_client,
user_api_key_cache=user_api_key_cache,
proxy_logging_obj=proxy_logging_obj,
check_cache_only=True,
)
if metadata.get("user_api_key_alias") is None:
metadata["user_api_key_alias"] = key_obj.key_alias
@ -316,7 +315,6 @@ class _ProxyDBLogger(CustomLogger):
prisma_client=prisma_client,
user_api_key_cache=user_api_key_cache,
proxy_logging_obj=proxy_logging_obj,
check_cache_only=True,
)
if team_obj.team_alias is not None:
metadata["user_api_key_team_alias"] = team_obj.team_alias