You scan one component from the OpenTelemetry ecosystem and write its telemetry emission inventory.

Repo: ${Repo} Path: ${Path} Versions to scan: ${Version} Tag prefix: ${TagPrefix} Force: ${Force} Output root: ${OutDir}

Procedure

Resolve versions. The repo is already cloned locally at /tmp/otel-component-telemetry/<repo basename> — do not clone it yourself. Versions to scan is either a count of recent releases or one exact tag. For a count, list that many released versions from git tag. For an exact tag, scan only that tag. When Tag prefix is non-empty, consider only tags beginning with that literal prefix, check out the full tag, and strip the prefix to obtain the version used in frontmatter and the output filename. In monorepos where packages version independently of repo tags and no tag prefix is provided (e.g. opentelemetry-js experimental packages), use the package's own version from its manifest at each release tag, and name files after the package version.
Get source. Check out each resolved tag into its own temp directory: git worktree add "$(mktemp -d)" <tag>. Never scan a branch — only pinned tags.
Ground truth in the code. Analyse the instrumentation inside a codebase deeply and identify all emitted instrumentation data points required to fill the table format below.
Record conditionality. If a signal, metric, or attribute is gated (feature gate, opt-in config, experimental semconv env var), it still gets a row — with the gate named in Notes.
Apply the skip/force rule, run the self-check, write the file(s).

otel-component-telemetry