open-telemetry / open-telemetry/opentelemetry-php
[opentelemetry-php-contrib] OtelSdkBundle roadmap questions
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 912
- Forks
- 232
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 4
Description
Hi, I'd like to use OtelSdkBundle to start adopting opentelemetry.
Currently there is abandoned package open-telemetry/contrib-sdk-bundle which suggests using open-telemetry/symfony-sdk-bundle.
This package directs to a read-only repository containing two bundles:
open-telemetry/contrib-sdk-bundleopen-telemetry/contrib-symfony-instrumentation-bundle
The first one open-telemetry/contrib-sdk-bundle in its readme mentions the uprising Instrumentation bundle (I guess the second one) which will add instrumentation for symfony project.
I have a few questions:
- Is there any timeline for a stable release? When we can expect to see version 1.0.0?
- What is the scope for the stable version for
open-telemetry/contrib-sdk-bundle? - Is there any publicly available roadmap where we can track development progress?
- What is the scope for the stable version of
open-telemetry/contrib-symfony-instrumentation-bundle? - In terms of backward compatibility: should we expect any breaking changes before version 1.0.0? I know that semantic versioning allows breaking changes before stable release but I'm asking about Your plans/policy. Do You have a large refactor in mind that could lead to breaking change in the public API?
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 OtelSdkBundle and Symfony instrumentation bundle references named in the issue, along with the linked read-only repository. The issue provides no implementation files, tests, or acceptance criteria; done would require an agreed roadmap and compatibility policy to be documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, symfony
- Domain
- observability
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100