aidog-request-inspect

To debug a failed AiDog proxy request, query the local SQLite proxy_log table using the request id to retrieve the full lifecycle, including upstream payloads, retry chains, and response bodies for local inspection.

A single AiDog proxy request log exposes inbound requests, upstream requests and responses, status codes, token counts, estimated costs, and retry chains, while automatically redacting sensitive headers for safe local analysis.

Yes, you can list recent proxy requests and filter them by group or isolate specific error cases by status code, enabling faster triage of routing, protocol conversion, and retry failures.

AiDog proxy request inspection automatically redacts sensitive headers from the logged data while preserving the request and response bodies, token counts, and upstream response details needed for debugging.

A request id is required to pinpoint the exact proxy exchange in the SQLite log, allowing you to trace the specific upstream platform, transformed payload, and retry attempts that caused a routing or protocol conversion failure.

The best way to review AiDog proxy retry chains and upstream responses is to look up the request by id in the local SQLite proxy_log, which surfaces the complete retry history and exact upstream response body for local debugging.