-
Notifications
You must be signed in to change notification settings - Fork 1.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
[exporterhelper] Reconsider the need of Go API related to ObsReport
#10592
Milestone
Comments
dmitryax
changed the title
[exporterhelper] Reconsider need of Go API related to
[exporterhelper] Reconsider the need of Go API related to Jul 11, 2024
ObsReport
ObsReport
@codeboten please let me know if it makes sense to you |
Yup, makes sense |
codeboten
pushed a commit
that referenced
this issue
Aug 7, 2024
#### Description Delete deprecated `exporterhelper.ObsReport` and `exporterhelper.NewObsReport` #### Link to tracking issue Relates to #10592
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
receiverhelper.ObsReport
is extensively used by many receivers in the contrib. However, exported API related toexporterhelper.ObsReport
is not being used because that functionality is already incapsulated into top-level helpersexporterhelper.New[Metrics|Traces|Logs]Exporter
and there is no reason to interact withexporterhelper.ObsReport
directly.Given that we want to limit exposed API before 1.0, I suggest we deprecate and remove public API in https://github.com/open-telemetry/opentelemetry-collector/blob/main/exporter/exporterhelper/obsexporter.go
The text was updated successfully, but these errors were encountered: