fix: correct variable in telemetry metrics backend error message #1516
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
sergiyvamz
approved these changes
Aug 25, 2025
Use telemetryMetricsBackend instead of telemetryTracesBackend in the RuntimeException when an invalid metrics backend is configured. chore(deps): bump software.amazon.awssdk:rds from 2.32.21 to 2.32.25 (aws#1509) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> docs: focus readme intro on plugin flexibility (aws#1508) docs: clarifying blue/green compatibility with current service landscape (aws#1512)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Use
telemetryMetricsBackendinstead oftelemetryTracesBackendin the RuntimeException when an invalid metrics backend is configured.Summary
Fix incorrect variable in telemetry metrics backend error message
Description
Fixed a bug in
DefaultTelemetryFactorywhere the error message for invalid metrics backend configuration was displaying the wrong variable value.Issue: When an invalid
telemetryMetricsBackendvalue was provided, the RuntimeException incorrectly showed thetelemetryTracesBackendvalue in the error message, making it confusing for users to identify which configuration was actually invalid.Fix: Changed line 64 to use
telemetryMetricsBackendinstead oftelemetryTracesBackendin the exception message.Before:
After:
Additional Reviewers
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.