open-telemetry / open-telemetry/opentelemetry-ruby
Verify Metrics configuration is spec compliant
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
There are three lines related to configuration within the spec compliance matrix:
- Configuration is managed solely by the MeterProvider
- The MeterProvider provides methods to update the configuration
- The updated configuration applies to all already returned Meters
Evaluate our current support of metrics configuration to determine whether we meet these requirements. If we do not meet these requirements, update the code as part of this issue.
For reference, here's the Metrics SDK spec for MeterProvider: Configuration
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 linked Metrics SDK spec section on MeterProvider configuration, then trace the repository's current metrics configuration and MeterProvider behavior. Compare the implementation with all three listed requirements; done when the supported behavior is spec-compliant and the relevant verification is in place.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100