open-telemetry / open-telemetry/weaver
Re-design type definitions for attributes and event bodies
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 108
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 40
Description
Attributes and event bodies can be of a complex types. With schema v2, we could have syntax like
types:
- name: gen_ai.chat_message
definition: todo
that's reusable inside other type definitions and as an attribute/event body type.
https://github.com/open-telemetry/semantic-conventions/pull/2179 is an example where we define some types in JSON schema, but that doesn't look like the long term direction.
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 reviewing the schema v2 syntax described in the issue and the linked semantic-conventions PR #2179, which uses JSON Schema for type definitions. Determine the long-term representation for reusable complex types in attributes and event bodies; done means the design is agreed and the affected Weaver schema and generation behavior are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100