Proposal: Define instrumentations/packages - #872
Conversation
|
Are packages versioned? What's the difference between a package and just a repository directly? |
Would be versioned by the registry/repository which contains them.
A package is a subset of the signals in the repository and provides the definition of what instrumentations should be implementing including the requirement level of the signal is. |
Pull request dashboard statusWaiting on reviewers · refreshed 2026-08-04 14:25 UTC Review the latest changes. Status above doesn't look right?
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #872 +/- ##
=====================================
Coverage 81.5% 81.5%
=====================================
Files 130 130
Lines 11688 11688
=====================================
+ Hits 9527 9529 +2
+ Misses 2161 2159 -2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Hi @thompson-tomo — just a friendly reminder that this pull request is waiting on you. There are still items that need your attention. See the dashboard status comment for the full list. You don't need to push a code change to hand it back — replying to move each discussion forward is enough, whether that's answering a question, explaining why no change is needed, or asking a follow-up. The dashboard then automatically routes it back to reviewers. If you believe this pull request is incorrectly routed as waiting on the author, comment |
progresses #406
This seeks to define the concept of instrumentations/packages as a way to group telemetry signals and specifying their requirement. This also serves as a way to standardise usage of instrumentation scopes.