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

Make ServiceTalkWireLogger consistent with LoggingHandler #1309

Merged
merged 1 commit into from
Jan 11, 2021

Conversation

idelpivnitskiy
Copy link
Member

Motivation:

ServiceTalkWireLogger is a rework if netty's LoggingHandler which allows
us to control logging of user data. However, the output format was a bit
different from netty, making it harder to compare netty and ST logs. Also,
it has a few minor issues with the output.

Modifications:

  • Align output format with LoggingHandler;
  • Make internal methods static when possible;
  • Do not print extra new line when buffer is empty;
  • Log how Channel's writability changed;
  • Do not log localAddress when it's null;

Result:

Output of ServiceTalkWireLogger and LoggingHandler is aligned.

Motivation:

`ServiceTalkWireLogger` is a rework if netty's `LoggingHandler` which allows
us to control logging of user data. However, the output format was a bit
different from netty, making it harder to compare netty and ST logs. Also,
it has a few minor issues with the output.

Modifications:

- Align output format with `LoggingHandler`;
- Make internal methods `static` when possible;
- Do not print extra new line when buffer is empty;
- Log how `Channel`'s writability changed;
- Do not log `localAddress` when it's `null`;

Result:

Output of `ServiceTalkWireLogger` and `LoggingHandler` is aligned.
@idelpivnitskiy idelpivnitskiy merged commit b55a4e8 into apple:main Jan 11, 2021
@idelpivnitskiy idelpivnitskiy deleted the ServiceTalkWireLogger branch January 11, 2021 20:27
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