open-telemetry / open-telemetry/opentelemetry-python
View should avoid warning if conflict involves multiple description properties
Open
Nobody has claimed this yet.
metrics
sdk
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
From the spec:
If the potential conflict involves multiple description properties, setting the description through a configured View SHOULD avoid the warning.
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
The issue names no source file or test; start with the OpenTelemetry metrics SDK's View handling and the linked specification section on duplicate instrument registration conflicts. Trace how conflicts involving multiple description properties produce warnings. Done means a configured View that sets the description avoids that warning, with the behavior covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100