ISSUE-1660 Auto configuration for OpenTelemetry HTTP retry attributes #1748
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
alexliahushau
requested review from
Joyfolk,
fatroom,
gpradeepkrishna and
lukasniemeier-zalando
as code owners
Member
|
Hi Alex, can you give more details on what is the ISSUE-1660? |
fatroom
added
the
minor
Contributor
Author
|
Member
|
👍 |
1 similar comment
Contributor
Author
|
👍 |
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.
This PR introduces auto-configuration for OpenTelemetry HTTP retry attributes, providing seamless integration and enhanced observability for HTTP client retry behavior in Spring-based applications.
Summary of Changes:
Why is this change necessary?
This feature simplifies the process of enabling HTTP retry observability for Spring applications by leveraging Spring Boot's auto-configuration mechanism. Developers using the Spring ecosystem can now gain actionable insights into HTTP retry behavior without requiring manual setup. This contributes to better debugging, performance monitoring, and alignment with OpenTelemetry standards.
Related Issue: