open-telemetry / open-telemetry/weaver
[Project Tracking] Prototype and Proposal for Milestone 1 - Fully resolved registry / telemetry schema
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 486
- Forks
- 108
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 40
Description
From our OTEP plan, we have the first milestone to achieve:
Introduce a registry section with a list of fully resolved attributes, metrics, and other telemetry signals from the existing semantic convention registry. Upon implementation, the OpenTelemetry project's telemetry schema will include a registry of all standardized attributes, metrics, and signals as defined by the semantic conventions.
This is a meta issue tracking progress towards a prototype and proposal:
Tasks
- #10
- #9
- #8
- #3
- #186 (see #400)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked OTEP plan and reviewing the completed tasks (#10, #9, #8, #3, and #186/#400). Determine whether any work remains for the Milestone 1 prototype and proposal, and document completion by confirming that the registry covers the standardized attributes, metrics, and other telemetry signals described there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability-sre, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100