open-telemetry / open-telemetry/opentelemetry-ruby
Support Declarative configuration
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
In early 2026 Declarative configuration initial stable version was released and as such we should be looking to add support for it.
This is more than just reading just config from a file but a new approach to managing the configuration layer which is designed to be changing over time.
The support status is documented at https://github.com/open-telemetry/opentelemetry-configuration/blob/main/language-support-status.md
The steps I foresee:
- generate types based on json schema
- config loader using types
- use types in providers
- add a diff engine to determine what has changed
- reload only affected components
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 language-support-status.md in the linked opentelemetry-configuration repository to understand the stable declarative configuration requirements. Then break down the proposed work into schema-generated types, a typed loader, provider integration, change detection, and component reloading. Done means the Ruby SDK supports the full configuration lifecycle, including reloading only affected components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100