open-telemetry / open-telemetry/opentelemetry-python
Define a mechanism to select the measurement consumer
Open
Nobody has claimed this yet.
metrics
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Ok, but I think that we will need a mechanism to do that. Opening a corresponding issue.
Originally posted by @ocelotl in https://github.com/open-telemetry/opentelemetry-python/pull/2339#r782625333
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 discussion referenced from PR #2339, since the issue body provides no files, tests, or entry points. Clarify the requirements for selecting a measurement consumer and define what behavior would demonstrate that the mechanism is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100