{"version":"2.1.269","anchor":"opentelemetry-metrics-can-optionally-include-vcsrepository","canonical_anchor":"opentelemetry-metrics-can-optionally-include-vcsrepository","heading":"OpenTelemetry metrics can optionally include VCS\/repository attributes","tier":"use","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/opentelemetry-metrics-can-optionally-include-vcsrepository","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### OpenTelemetry metrics can optionally include VCS\/repository attributes\n\nOpenTelemetry metrics can now optionally tag data with the project's git repository and provider details.\n\n**What**\n\nWhen 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.\n\n**Why**\n\nTeams 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.\n\n- Area: Telemetry\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}