-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Consider deprecating the opencensus exporter and receiver #36791
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I have not heard back on this plan yet. I will move to open a first PR to deprecate the components and publish a deprecation and removal schedule for review by approvers. |
I support deprecating both. 6 months seem like a reasonable time period to migrate off to me. |
Component(s)
exporter/opencensus, receiver/opencensus
Describe the issue you're reporting
The OpenCensus functionality has been around for a bit but is now superceded by OTLP.
I propose that we start deprecating those components, and set a deadline for removal.
The calendar would work as follows:
This will give time to anyone using the components to make plans. We can make the duration of the deprecation longer based on community input.
Please provide your feedback as comments and reactions. Before we proceed, I would like to make sure we receive a healthy number of 👍 from approvers and maintainers of the repository.
The text was updated successfully, but these errors were encountered: