Skip to content

Support core metrics for sync clients #1882

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
merged 1 commit into from
Jun 8, 2020

Conversation

dagnir
Copy link
Contributor

@dagnir dagnir commented Jun 8, 2020

Description

This commits adds collection of core metrics for sync clients.

Motivation and Context

Testing

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have read the README document
  • I have added tests to cover my changes
  • All new and existing tests passed
  • A short description of the change has been added to the CHANGELOG
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jun 8, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 9 Code Smells

92.9% 92.9% Coverage
0.0% 0.0% Duplication

warning The version of Java (1.8.0_252) you have used to run this analysis is deprecated and we will stop accepting it from October 2020. Please update to at least Java 11.
Read more here

@@ -271,4 +286,12 @@ static void validateExecutionParams(ClientExecutionParams<?, ?> executionParams)
BiFunction<T, R, T> function2) {
return (x, y) -> function2.apply(function1.apply(x, y), y);
}

private MetricCollector resolveMetricCollector(ClientExecutionParams<?, ?> params) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we move this recurring resolver to a utils class or is that inconsistent with our core coding patterns?

* Utility methods for working with metrics.
*/
@SdkInternalApi
public final class MetricUtils {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this class have a unit test file?

@dagnir
Copy link
Contributor Author

dagnir commented Jun 8, 2020

Per discussion with @zoewangg going to merge this PR now since the outstanding comments are minor so she can get started on async metrics. Will address the comments here in a follow up PR.

@dagnir dagnir merged commit 0ee0be3 into aws:sdk-metrics-development-2 Jun 8, 2020
@dagnir dagnir mentioned this pull request Jun 17, 2020
13 tasks
dagnir added a commit to dagnir/aws-sdk-java-v2 that referenced this pull request Jun 18, 2020
Follow-up on review comment on aws#1882
aws-sdk-java-automation added a commit that referenced this pull request Dec 21, 2021
…a8f6000ba

Pull request: release <- staging/e6f8c2a2-d913-4fb6-b322-03ca8f6000ba
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants