-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/sapm] Consider deprecating sapmreceiver #32125
Comments
Pinging code owners for receiver/sapm: @atoulme. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Removing |
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. |
Fixes #32125 Co-authored-by: Antoine Toulme <[email protected]>
Component(s)
receiver/sapm
Describe the issue you're reporting
Consider deprecating the sapmreceiver. This receiver will be replaced by OTLP. The deprecation cycle would start a timer of at least a year before eventual removal.
The text was updated successfully, but these errors were encountered: