Answer: Lower the export intervals so data reaches the collector while a short task is still running. By default, metrics export every 60 seconds and traces and logs export every 5 seconds; the example shortens all three intervals to 1000. Status: Confirmed Entry: tool/claude-code/integrations/flush-telemetry-short-lived-calls Revision: 1 Digest: sha256:8acf72749cd74031 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:02:50Z Last changed: 2026-11-13T03:02:50Z Last verified: 2026-11-20T12:16:53Z Next check: 2026-11-21T12:16:53Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of Default metrics export interval | 60 seconds | seconds | [1] | 2026-11-20 Default traces and logs export interval | 5 seconds | seconds | [1] | 2026-11-20 OTEL_METRIC_EXPORT_INTERVAL | 1000 | | [1] | 2026-11-20 OTEL_LOGS_EXPORT_INTERVAL | 1000 | | [1] | 2026-11-20 OTEL_TRACES_EXPORT_INTERVAL | 1000 | | [1] | 2026-11-20 Sources: [1] Anthropic. "Observability with OpenTelemetry". https://code.claude.com/docs/en/agent-sdk/observability.md Role: primary. Accessed: 2026-11-20T12:16:53Z Quote: "By default, metrics export every 60 seconds and traces and logs export every 5 seconds." (Supports: Default metrics export interval, Default traces and logs export interval) Quote: ""OTEL_METRIC_EXPORT_INTERVAL": "1000"," (Supports: OTEL_METRIC_EXPORT_INTERVAL) Quote: ""OTEL_LOGS_EXPORT_INTERVAL": "1000"," (Supports: OTEL_LOGS_EXPORT_INTERVAL) Quote: ""OTEL_TRACES_EXPORT_INTERVAL": "1000"," (Supports: OTEL_TRACES_EXPORT_INTERVAL) Published: 2026-11-20T10:36:10Z Snapshot SHA-256: 01e682cd9021a18dc9d162abc2354c4eda3478f2879c1666cd438ff23100515d (captured 2026-11-13T03:02:50Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:02:50Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:16:53Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:16:53Z Last attempt: 2026-11-20T12:16:53Z Notes and limitations: Extracted automatically from a single official source (section "Flush telemetry from short-lived calls"). Related: https://latestn.com/tool/claude-code/integrations/gateway-request-headers Which request headers must an LLM gateway forward for Claude Code to work correctly? https://latestn.com/tool/claude-code/integrations/gateway-supported-api-formats Which API formats does a gateway need to support for Claude Code to work with it? https://latestn.com/tool/claude-code/integrations/ghes-supported-features Which Claude Code features support GitHub Enterprise Server and how do they differ from github.com? https://latestn.com/tool/claude-code/integrations/enable-telemetry-export How do I enable OpenTelemetry telemetry export in the Claude Agent SDK? https://latestn.com/tool/claude-code/integrations/expose-reply-tool How do I expose a reply tool so Claude can send messages back through a Claude Code channel? https://latestn.com/tool/claude-code/integrations/features-by-provider Which Claude Code features are available on Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:02:50Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/integrations/flush-telemetry-short-lived-calls/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/integrations/flush-telemetry-short-lived-calls POST: https://latestn.com/dispute/tool/claude-code/integrations/flush-telemetry-short-lived-calls with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/integrations/flush-telemetry-short-lived-calls?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I flush telemetry from short-lived Claude Agent SDK calls? Revision 1, last verified 2026-11-20T12:16:53Z. https://latestn.com/tool/claude-code/integrations/flush-telemetry-short-lived-calls (accessed 2026-11-21T09:58:52Z). @misc{LatestN_tool_claude_code_integrations_flush_telemetry_short_lived_calls_r1, title = {How do I flush telemetry from short-lived Claude Agent SDK calls?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/integrations/flush-telemetry-short-lived-calls}}, note = {Revision 1; digest sha256:8acf72749cd74031; last verified 2026-11-20T12:16:53Z; accessed 2026-11-21T09:58:52Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/integrations/flush-telemetry-short-lived-calls