fix(otel): Explicitly specify memory_limiter value #7110
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
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.
This PR addresses the error "references processor 'memory_limiter' which is not configured". The issue arose from a change in how null values are interpreted for the different property values while using the open telemetry helm charts. Previously, setting it to null would use the default value. However, there was an inconsistency where some queries would be disabled when set to null, while others would use the default value.
To resolve this, the PR explicitly specifies the default value for the
memory_limiterproperty. This approach ensures consistent behavior across all queries and serves as a potential fix for the error.Reference:
open-telemetry/opentelemetry-helm-charts#1272
open-telemetry/opentelemetry-helm-charts#1275