Prefer OTEL to exporter if both enabled #4137
Merged
Conversation
This file contains hidden or 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
If both Exporter and OTel Metrics are enabled, CPK prefers OTel.
cbandy
approved these changes
Mar 19, 2025
dsessler7
pushed a commit
that referenced
this pull request
Nov 14, 2025
If both Exporter and OTel Metrics are enabled, CPK prefers OTel. See: 46ee186
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.
Checklist:
Type of Changes:
What is the current behavior (link to any open issues here)?
We had logic to prefer OTel if both were enabled, but that was dropped so we could discuss it; this reenables that behavior with the collector util func logic.
What is the new behavior (if this is a feature change)?
If both Exporter and OTel Metrics are enabled, CPK prefers OTel.
Other Information: