{"version":"2.1.301","anchor":"otel-hostarch-resource-now-taken-from-local-helper-not-hos","canonical_anchor":"otel-hostarch-resource-now-taken-from-local-helper-not-hos","heading":"OpenTelemetry data no longer runs the standard host lookup","tier":"notice","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/otel-hostarch-resource-now-taken-from-local-helper-not-hos","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### OpenTelemetry data no longer runs the standard host lookup\n\nClaude Code now sets the host architecture in OpenTelemetry data itself instead of running the standard host detector\n\n**Unclear.** Whether hostname and host ID fields still appear in exported OpenTelemetry data is not stated.\n\n**What**\n\nOpenTelemetry is a standard way to send usage and performance data to a monitoring system. That data includes a description of the machine it came from. Claude Code no longer builds this description with OpenTelemetry's standard host detector. It now fills in the host architecture field, such as the processor type, on its own.\n\n**Why**\n\nThe standard host detector also gathers the machine's hostname and an ID for the host, and that lookup no longer runs.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}