-
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
[processor/cumulativetodelta] Update stability level to beta #10004
[processor/cumulativetodelta] Update stability level to beta #10004
Conversation
#10005 should resolve the CI failures |
I would not put "stable" if we know we want to replace. |
Thats fair, but I think |
#10005 is merged. Please rebase |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor change, as suggested in #10006
| ------------------------ | --------- | | ||
| Stability | [beta] | | ||
| Supported pipeline types | metrics | | ||
| Distribution | [contrib] | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Distribution | [contrib] | | |
| Distributions | [contrib] | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed
@@ -72,3 +74,6 @@ processors: | |||
# If include/exclude are not specified | |||
# convert all cumulative sum metrics to delta | |||
``` | |||
|
|||
[beta]: https://github.com/open-telemetry/opentelemetry-collector-contrib#beta |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link was wrong @TylerHelmuth, I think it should have been:
https://github.com/open-telemetry/opentelemetry-collector#beta
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I missed that. I guess we could use of link validation checker, WDYT? I can open an issue and look for something
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pmm-sumo that would be great. the core repo has a github task: https://github.com/open-telemetry/opentelemetry-collector/blob/main/.github/workflows/check-links.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure thing! Opened an issue #10162
…lemetry#10004) * Update stability level * Updated format * Updated distribution to distributions
…lemetry#10004) * Update stability level * Updated format * Updated distribution to distributions
Description:
The cumulativetodelta processor's config was previously updated to a stable state. I'd like to bring this component's stability level in line with that change. I know this processor is also getting production exposure, and I'd like to consider it "Stable" soon, but I don't want to jump from "In Developement" to "Stable".
This processor will likely be replaced by the transform processor, but that is a long way off. In the meantime, I'd like customers to feel better about using this processor.