Skip to content

Metric utils test #1906

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 18, 2020
Merged

Conversation

dagnir
Copy link
Contributor

@dagnir dagnir commented Jun 17, 2020

Description

Follow-up on review comment on #1882

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

@dagnir dagnir changed the base branch from master to sdk-metrics-development-2 June 17, 2020 22:39
@dagnir dagnir force-pushed the metric-utils-test branch from 9294912 to 1ce3eec Compare June 17, 2020 22:56
Follow-up on review comment on aws#1882
@dagnir dagnir force-pushed the metric-utils-test branch from 1ce3eec to b9b7faa Compare June 18, 2020 15:19
@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.

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

0.0% 0.0% 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

Comment on lines +119 to +120
verify(mockCollector).reportMetric(CoreMetric.AWS_REQUEST_ID, requestId);
verify(mockCollector).reportMetric(CoreMetric.AWS_REQUEST_ID, amznRequestId);
Copy link
Contributor

Choose a reason for hiding this comment

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

Why do we report the same metric with two different values?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Depending on the service, the Header used for the request ID can be differ between these two values. This is just to ensure we're catching both cases, I don't think a service will use both.

Copy link
Contributor

Choose a reason for hiding this comment

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

ok!

@dagnir dagnir merged commit 27fbcfd into aws:sdk-metrics-development-2 Jun 18, 2020
@dagnir dagnir deleted the metric-utils-test branch June 18, 2020 16:39
aws-sdk-java-automation added a commit that referenced this pull request Jan 22, 2022
…f9aff9e0b

Pull request: release <- staging/d48fd9ff-6141-4e4a-8e2a-8cdf9aff9e0b
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.

2 participants