open-telemetry / open-telemetry/opentelemetry-python
opentelemetry-semantic-conventions: handle explicit buckets for metrics helpers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Helpers that creates metrics should have knowledge of the preferred bucket boundaries otherwise they do more harm than good when used.
Two that comes to mind are create_http_server_request_duration and create_http_client_request_duration.
Wondering if the explicit buckets are found in what weaver generates (or even in the spec) and if they are referenced from the metrics.
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 locating the create_http_server_request_duration and create_http_client_request_duration helpers, then inspect whether Weaver or the semantic conventions specification defines their preferred explicit bucket boundaries. Done means both helpers use the appropriate boundaries when creating metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100