open-telemetry / open-telemetry/opentelemetry-python
Add a docstring to outline metric reader and view configuration conflicts
Open
Nobody has claimed this yet.
doc
metrics
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Probably out of scope for this but should we clarify somewhere what happens when the metric reader is configured and view also matches.
Originally posted by @srikanthccv in https://github.com/open-telemetry/opentelemetry-python/pull/2832#discussion_r923971127
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 metric reader and view configuration code, along with the discussion in PR #2832 referenced by this issue. Clarify and document what happens when a metric reader is configured and a matching view is also present; done when the relevant docstring explains that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100