-
Notifications
You must be signed in to change notification settings - Fork 624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support new stable http semantic conventions for http instrumentations - transition plan #1768
Comments
Hi there! I'd love to stay in the loop and work on the actual transition if/when the time comes. So far I've been catching up on related issues. In May, a PR was merged outlining a transition helper variable, |
As discussed in the Python Sig 7/13 We will NOT be implementing the transition plan as defined here. Instead, we will be sticking with our current instrumentation releases (bumping minor versions as appropriate) until we are ready to make a stable release of our instrumentations (1.X) since all of our instrumentations are not yet stable. As for updating to the new semantic conventions, we will be updating to the frozen version v1.21 [this pr] (#1746) so as to only make a single breaking change. This will be followed by a MINOR version release as usual. Our message to users is that this will be a significant breaking change and we will assist them as needed when issues arise if they want to upgrade. |
Should #1759 have been part of this effort? I think we should discuss in the SIG next week as it was already released. |
Created a project board to track this effort. |
This message is outdated and the TC has advised the Python SIG to implement the transition plan. This issue will be used to track work related to that. |
For breaking changes that are conflicting, the new semantic conventions will take priority. The only changes that should be affected by the migration plan are attribute related changes. |
Superseded by #1986 |
Now that the community has decided to adopt ECS conventions, there is a push for stability for http semantic conventions. Part of this eventual work for languages is the eventual transition for instrumentations to update to the stable semantic conventions (which contain several breaking changes). This issue discusses the process of how languages will transition their instrumentations. The associated PR proposes a plan to do so, including bumping instrumentations to major versions. This poses a couple of problems with how we currently version our packages:
Opening this issue to discuss how we can tackle this transition and whether we want to chime in to the community if this is not feasible.
The text was updated successfully, but these errors were encountered: