Krish Dholakia 53a1e31729 feat(spend-logs): add truncation note when error logs are truncated for DB storage (#22936) ...

When the messages or response JSON fields in spend logs are truncated
before being written to the database, the truncation marker now includes
a note explaining:
- This is a DB storage safeguard
- Full, untruncated data is still sent to logging callbacks (OTEL, Datadog, etc.)
- The MAX_STRING_LENGTH_PROMPT_IN_DB env var can be used to increase the limit

Also emits a verbose_proxy_logger.info message when truncation occurs in
the request body or response spend log paths.

Adds 3 new tests:
- test_truncation_includes_db_safeguard_note
- test_response_truncation_logs_info_message
- test_request_body_truncation_logs_info_message

Co-authored-by: Cursor Agent <cursoragent@cursor.com>

2026-03-05 16:58:46 -08:00

..

test_cloudzero_endpoints.py

…

test_spend_management_endpoints.py

[Release Fix] (#22411)

2026-02-28 09:46:35 -08:00

test_spend_query_optimization.py

…

test_spend_tracking_utils.py

feat(spend-logs): add truncation note when error logs are truncated for DB storage (#22936)

2026-03-05 16:58:46 -08:00