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

Netty4.1: remove our handler when original handler is removed #3026

Merged
merged 9 commits into from
May 19, 2021

Conversation

laurit
Copy link
Contributor

@laurit laurit commented May 18, 2021

Resolves #1373

Copy link
Member

@trask trask left a comment

Choose a reason for hiding this comment

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

@laurit laurit changed the title Netty4.1: remove our handler when original handler is removed [Don't merge]Netty4.1: remove our handler when original handler is removed May 19, 2021
@laurit laurit changed the title [Don't merge]Netty4.1: remove our handler when original handler is removed Netty4.1: remove our handler when original handler is removed May 19, 2021
@@ -40,7 +39,7 @@
@Override
public void transform(TypeTransformer transformer) {
transformer.applyAdviceToMethod(
isMethod().and(nameStartsWith("write")),
isMethod().and(named("write").or(named("writeAndFlush"))),
Copy link
Contributor Author

Choose a reason for hiding this comment

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

epoll & kqueue channel implementations have methods starting with write that shouldn't be instrumented

@trask trask merged commit 23a40d9 into open-telemetry:main May 19, 2021
@laurit laurit deleted the netty-remove-handler branch May 19, 2021 17:20
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.

Ratpack instrumentation breaks when using pooling
3 participants