Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

OpenTelemetry metrics can optionally include VCS/repository attributes

OpenTelemetry metrics can now optionally tag data with the project's git repository and provider details.

TierUse it nowhow much it should matter to you
Useful4my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaTelemetrywhat it touches
KindNew Featuresin v2.1.269,
Use it now Notable

OpenTelemetry metrics can now optionally tag data with the project's git repository and provider details.

What

When the OTEL_METRICS_INCLUDE_REPOSITORY setting is enabled, Claude Code now parses the project's git remote URL and attaches repository details to its OpenTelemetry (an open standard for exporting logs, metrics and traces) metrics: vcs.repository.url.full, vcs.repository.name, vcs.owner.name, vcs.provider.name, and vcs.ref.head.revision/name/type. It recognizes GitHub, GitLab, Bitbucket (including self-hosted Bitbucket Server "scm" URLs and the SSH port 7999 form), and Gitea-style remote URLs.

Why

Teams that export Claude Code's metrics to an observability backend can now break them down by repository, owner and provider without adding this tagging themselves.

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded OTEL_METRICS_INCLUDE_REPOSITORY to tag OpenTelemetry metrics and events with vcs. repository attributes; commit events get…

See this entry in the whole of v2.1.269 →

Feedback