Skip to content
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

Log channel ID when logging error #2892

Merged
merged 4 commits into from
Dec 8, 2021
Merged

Conversation

dagnir
Copy link
Contributor

@dagnir dagnir commented Dec 7, 2021

Motivation and Context

Better logging.

Description

Testing

Added unit tests, ran integration tests.

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 force-pushed the channel-id-logging branch from 7b3f953 to 5c2528c Compare December 7, 2021 18:29
@dagnir dagnir marked this pull request as ready for review December 7, 2021 18:29
@dagnir dagnir requested a review from a team as a code owner December 7, 2021 18:29
@dagnir dagnir force-pushed the channel-id-logging branch from 1f6f2da to 300cc57 Compare December 7, 2021 23:28
Copy link
Contributor

@Bennett-Lynch Bennett-Lynch left a comment

Choose a reason for hiding this comment

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

We seem to have quite a few other Netty-based classes that could benefit from this logger. E.g., here is one I chose at random. How can we go about making sure this logger is more consistently used?

@dagnir
Copy link
Contributor Author

dagnir commented Dec 7, 2021

We seem to have quite a few other Netty-based classes that could benefit from this logger. E.g., here is one I chose at random. How can we go about making sure this logger is more consistently used?

Now that we have switched to full-fledged facade, it would be easier to do that by enforcing the use of this logger only within the Netty module.

@dagnir dagnir force-pushed the channel-id-logging branch from b1feca0 to a34d7e3 Compare December 8, 2021 17:45
@sonarqubecloud
Copy link

sonarqubecloud bot commented Dec 8, 2021

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

86.3% 86.3% Coverage
0.0% 0.0% Duplication

@dagnir dagnir merged commit f8de5b4 into aws:master Dec 8, 2021
@dagnir dagnir deleted the channel-id-logging branch December 8, 2021 19:10
aws-sdk-java-automation added a commit that referenced this pull request Feb 7, 2024
…2798c8cb1

Pull request: release <- staging/1c0c8ade-7bcb-4158-8160-4962798c8cb1
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