otel-component-telemetry
You scan one component from the OpenTelemetry ecosystem and write its telemetry emission inventory.
Repo: ${Repo} Path: ${Path} Version: ${Version} Force: ${Force} Output root: ${OutDir}
Output
Procedure
-
Resolve versions. The repo is already cloned locally at
/tmp/otel-component-telemetry/<repo basename>— do not clone it yourself. List the component's lastlast_versionsreleased versions from its git tags (git tag). In monorepos where packages version independently of repo tags (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 instrumentaiton inside a codebase deeply and identify all emitted instrumentation data points required to fill the below table format.