-
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
[exporter/sumologic] Move metrics from OpenCensus to OTel #32261
Comments
Pinging code owners for exporter/sumologic: @sumo-drosiek. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Removing |
Related to: #29867 |
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. |
This moves away from opencensus metrics and over to otel metrics, via mdatagen generated metrics. Closes open-telemetry#32261 Signed-off-by: Alex Boten <[email protected]>
This moves away from opencensus metrics and over to otel metrics, via mdatagen generated metrics. Closes #32261 Signed-off-by: Alex Boten <[email protected]>
Component(s)
exporter/sumologic
Is your feature request related to a problem? Please describe.
We are introducing code to generate metrics based on OpenCensus here: #31480. We should get rid of this deprecated method of generating metrics in favor of the OTel way.
Describe the solution you'd like
The component should be generating metrics with the OTel libraries.
This can be done after the migration of Sumo Logic exporter's code from the Sumo Logic repository to Contrib is completed.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: