{"version":"2.1.268","anchor":"new-telemetry-event-tengu-web-fetch-transport-records-outcom","canonical_anchor":"new-telemetry-event-tengu-web-fetch-transport-records-outcom","heading":"New telemetry event tengu_web_fetch_transport records outcome and duration of the raw HTTP fetch","tier":"internal","area":"WebFetch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-telemetry-event-tengu-web-fetch-transport-records-outcom","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New telemetry event tengu_web_fetch_transport records outcome and duration of the raw HTTP fetch\n\nA new telemetry event records the outcome and duration of each raw WebFetch network request\n\n**Unclear.** Whether the `tengu_web_fetch_transport` telemetry is active for any accounts is unread and not stated.\n\n**What**\n\nWebFetch (the tool Claude Code uses to fetch a URL's contents) now emits a telemetry event, `tengu_web_fetch_transport`, around its low-level network request. It records the outcome (error, redirect, HTTP error, or success), how long the request took (`httpDurationMs`), and how many bytes were returned.\n\n**Why**\n\nThis gives Anthropic visibility into how WebFetch's network requests are performing and failing, which can help diagnose fetch reliability issues.\n\n- Area: WebFetch\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}