From 668fac0f74443a6e6d38d37a79e003e8ff2db90d Mon Sep 17 00:00:00 2001 From: Rohan Mehta Date: Sun, 23 Mar 2025 18:14:10 -0400 Subject: [PATCH] Improve tracing error messages --- src/agents/tracing/processors.py | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/src/agents/tracing/processors.py b/src/agents/tracing/processors.py index 29eb0f58..5d8f4d8a 100644 --- a/src/agents/tracing/processors.py +++ b/src/agents/tracing/processors.py @@ -117,18 +117,22 @@ def export(self, items: list[Trace | Span[Any]]) -> None: # If the response is a client error (4xx), we wont retry if 400 <= response.status_code < 500: - logger.error(f"Tracing client error {response.status_code}: {response.text}") + logger.error( + f"[non-fatal] Tracing client error {response.status_code}: {response.text}" + ) return # For 5xx or other unexpected codes, treat it as transient and retry - logger.warning(f"Server error {response.status_code}, retrying.") + logger.warning( + f"[non-fatal] Tracing: server error {response.status_code}, retrying." + ) except httpx.RequestError as exc: # Network or other I/O error, we'll retry - logger.warning(f"Request failed: {exc}") + logger.warning(f"[non-fatal] Tracing: request failed: {exc}") # If we reach here, we need to retry or give up if attempt >= self.max_retries: - logger.error("Max retries reached, giving up on this batch.") + logger.error("[non-fatal] Tracing: max retries reached, giving up on this batch.") return # Exponential backoff + jitter