-
Notifications
You must be signed in to change notification settings - Fork 230
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
Debug exporter is not available in the image yet. This is the replacement for the deprecated logging exporter #2470
Comments
Someone showed me this in the helm values documentation, which might work around it:
|
I stumbled across the same issue of using the When running the current ADOT Collector (v0.36.0), you'll see the following warnings in the logs when using the
I'd love to fix them, however, users of the image can't act on those deprecations until the |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
It would be good to update the debug exporter added to the image. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
Keeping this alive, I think it is still relevant. |
Very much relevant, cant really debug right now. |
The latest version of the otel-collector chart opentelemetry-collector-0.73.1
Now includes the
debug
exporter in the values.yaml as a replacement for thelogging
exporter which is now deprecated:However, the latest version of the
aws-otel-collector
(v0.35.0 at the time of writting) does not include thedebug
exporter and fails when used with this chart:Since
config.exporters
is a map which we add all our other exporter config to, it is not easy to remove the debug key and stop the debug exporter from being added to the configmap.Since it is clear that the direction of travel is that
logging
is being replaced, can thedebug
exporter please be added now?The text was updated successfully, but these errors were encountered: