{"version":"2.1.248","anchor":"download-queue-backlog-reported-to-telemetry","canonical_anchor":"download-queue-backlog-reported-to-telemetry","heading":"Download queue backlog reported to telemetry","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/download-queue-backlog-reported-to-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Download queue backlog reported to telemetry\n\nDownload backlog on the agent proxy is now reported as a telemetry event.\n\n**What**\n\nThe agent proxy now emits a `tengu_agent_proxy_download_queue` event carrying `download_queued_peak_bytes` when a connection's buffered download exceeded its high-water or reporting threshold.\n\n**Details**\n\n- A helper probes whether the runtime's WebSocket implementation supports `pause`, which is how backpressure would be applied.\n\n**Evidence**\n\n`tengu_agent_proxy_download_queue`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}