open-telemetry / open-telemetry/opentelemetry-python
Validate feasibility of supporting new attribute types
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
What
Investigate whether it is possible and acceptable to extend the OTel Python API and SDK with new attribute types.
Guidelines for evolving API/SDK: https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/4485-extending-attributes-to-support-complex-values.md#how
Prototype in OTel Go demonstrating feasibility of adding new attribute types: https://github.com/open-telemetry/opentelemetry-go/pull/6809
Why
Per https://github.com/open-telemetry/opentelemetry-specification/issues/4602
Follows https://github.com/open-telemetry/opentelemetry-specification/pull/4614
The goal is to make sure that PRs like these are acceptable for OTel Python:
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 OTel Python API and SDK alongside OTEP 4485 and the linked OTel Go prototype. Compare the referenced specification and proto changes, then document whether extending Python attributes is feasible and acceptable, including any constraints or follow-up work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100