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

Reactor Netty: emit actual HTTP client spans spans on connection errors #9063

Merged
merged 3 commits into from
Aug 2, 2023

Conversation

mateuszrzeszutek
Copy link
Member

Continuation of #8111

@mateuszrzeszutek mateuszrzeszutek requested a review from a team as a code owner July 27, 2023 13:59
ERROR_ONLY,
DISABLED;

public static NettyInstrumentationFlag enabledOrErrorOnly(boolean b) {
Copy link
Member

Choose a reason for hiding this comment

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

this method name confused me, but I can't think of a better one...

Copy link
Member Author

Choose a reason for hiding this comment

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

I couldn't either - if anyone has a suggestion, I'm all ears

Copy link
Contributor

Choose a reason for hiding this comment

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

What do you think about calling it fromBoolean(..)?

Copy link
Member Author

Choose a reason for hiding this comment

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

What do you think about calling it fromBoolean(..)?

I'm not too fond of this, because it's a conversion of 2-value type to 3-value type -- and the simple fromBoolean doesn't really say what happens to the 3rd value.

Comment on lines -114 to +116
false,
false,
NettyConnectionInstrumentationFlag.DISABLED,
NettyConnectionInstrumentationFlag.DISABLED,
Copy link
Contributor

Choose a reason for hiding this comment

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

Why does this one not use the config?

Copy link
Member Author

Choose a reason for hiding this comment

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

It's a library instrumentation, I think it just can't implement the connection telemetry stuff.

Copy link
Contributor

@breedx-splk breedx-splk left a comment

Choose a reason for hiding this comment

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

Had a small question and a couple nits, but this looks good. Thanks for following up after the other work! 👍🏻

Comment on lines 133 to 137
if ("http://localhost:61/".equals(uri.toString())
|| "https://192.0.2.1/".equals(uri.toString())) {
return emptySet();
attributes.remove(SemanticAttributes.NET_PROTOCOL_NAME);
attributes.remove(SemanticAttributes.NET_PROTOCOL_VERSION);
}
Copy link
Member

Choose a reason for hiding this comment

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

nice

false,
connectionTelemetryEnabled
? NettyConnectionInstrumentationFlag.ENABLED
: NettyConnectionInstrumentationFlag.DISABLED,
Copy link
Member

Choose a reason for hiding this comment

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

is it not ERROR_ONLY because we capture those spans already in reactor-netty instrumentation?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, exactly that

@trask trask merged commit 527c4b3 into open-telemetry:main Aug 2, 2023
45 checks passed
@mateuszrzeszutek mateuszrzeszutek deleted the reactor-netty-part-2 branch August 2, 2023 17:19
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.

None yet

3 participants