Unclear Whether this is controlled by the tengu_api_success gate is unread for this account, so nothing can be said about whether it is switched on.
What
- The end-of-request telemetry (the
api_requestevent and related completion logging) now tracks afirstContentMsvalue — time to first content — separately from time-to-first-token, and includes attft_msfield when that value is available. - The main API-call success event,
tengu_api_success, now also recordsfirstContentMs, a client-generated request ID (clientRequestId), and the UUID of the originating user message (user_message_uuid). - The API call dispatcher now generates a new
clientRequestIdfor each attempt (sent as an extra header) and tracks an attempt counter, reporting request lifecycle telemetry — success/failure, status code, error class, attempt number,clientRequestId,requestId— plus adurationMsfield ontengu_api_successthat excludes time spent on retries.
Why These fields give much finer-grained visibility into API call performance and retry behavior, making it possible to distinguish slow model responses from network/retry overhead and to trace individual attempts by their request ID.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether this is controlled by the tengu_api_success gate is unread for this account, so nothing can be said about whether it is switched on.