Replace logging exporter with debug exporter #5260
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
liustanley
changed the title
liustanley
changed the title
dineshg13
approved these changes
Feb 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
The collector deployment is currently broken due to a change upstream that removed logging exporter references in contrib. I opened an issue for this here: open-telemetry/opentelemetry-helm-charts#1040.
This PR enables debug exporter and overrides logging exporter with null in order to prevent this error. This change is working correctly in dd-otel, but the CI is having issues with deploying on the Demo org and the collector pods are stuck in CrashLoopBackOff.
Link to tracking Issue:
Testing:
Documentation: