-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[pkg/ottl] Promote OTTL to Beta Stability #28892
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
Comments
From the stability levels documentation and referenced issues, it sounds good to me. 👍 |
Pinging code owners for pkg/ottl: @TylerHelmuth @kentquirk @bogdandrutu @evan-bradley. 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. |
Is there any update on this? |
@edmocosta is actively working on #29017 and has been for quite some time as it has been a hard one to solve in a backwards compatible way. This is likely the last big thing before beta. |
I've removed #29016 from the beta requirements list. We will look into it at a later time. |
#### Description OTTL has been a well-received part of the collector for several years now. Its functionality (especially the end-user facing parts) have been well tested and change infrequently. #### Link to tracking issue Closes open-telemetry#28892
Uh oh!
There was an error while loading. Please reload this page.
Component(s)
pkg/ottl
Is your feature request related to a problem? Please describe.
OTTL has seen extensive use via the transform processor, filter processor, tail sampling processor, routing processor, count connector, and routing connector. Although there is a few items to address, breaking changes are slowing down. I believe the package is close to Beta stability.
Items to address:
This is an initial list, but not exhaustive - it may change over time.
The text was updated successfully, but these errors were encountered: