-
Notifications
You must be signed in to change notification settings - Fork 947
Add business metric support for all flexible checksums #6505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
zoewangg
requested changes
Oct 23, 2025
...main/java/software/amazon/awssdk/core/internal/http/pipeline/stages/ApplyUserAgentStage.java
Outdated
Show resolved
Hide resolved
zoewangg
reviewed
Oct 24, 2025
...-core/src/main/java/software/amazon/awssdk/core/internal/useragent/BusinessMetricsUtils.java
Outdated
Show resolved
Hide resolved
...-core/src/main/java/software/amazon/awssdk/core/internal/useragent/BusinessMetricsUtils.java
Outdated
Show resolved
Hide resolved
...-core/src/main/java/software/amazon/awssdk/core/internal/useragent/BusinessMetricsUtils.java
Show resolved
Hide resolved
...c/main/java/software/amazon/awssdk/core/internal/http/pipeline/stages/HttpChecksumStage.java
Outdated
Show resolved
Hide resolved
zoewangg
approved these changes
Oct 27, 2025
|
|
This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
no-api-surface-area-change
Indicate there is no API surface area change and thus API surface area review is not required
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.



Add business metrics tracking support for all flexible checksum algorithms and configurations.
Motivation and Context
This change implements business metrics tracking for flexible checksum operations. This enables to track the adoption of flexible checksum algorithms (CRC32, SHA256, etc.) and configurations (WHEN_SUPPORTED, WHEN_REQUIRED) for telemetry and usage analysis.
Modifications
Testing
Added
FlexibleChecksumBusinessMetricTestfunctional tests to verify User-Agent header contains correct flexible checksum algorithm and configuration metrics.Screenshots (if appropriate)
Types of changes
Checklist
mvn installsucceedsscripts/new-changescript and following the instructions. Commit the new file created by the script in.changes/next-releasewith your changes.License