-
Notifications
You must be signed in to change notification settings - Fork 879
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
Split Webflux into client and server #12852
Conversation
79beda9
to
15400e8
Compare
6679d4f
to
de56007
Compare
import org.springframework.web.reactive.function.client.ExchangeFilterFunction; | ||
|
||
/** Entrypoint for instrumenting Spring Webflux HTTP clients. */ | ||
public final class SpringWebfluxClientTelemetry { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same question as with armeria, do we want client and server instrumentation in separate packages as with ktor
...o/opentelemetry/instrumentation/spring/webflux/v5_3/SpringWebfluxClientTelemetryBuilder.java
Outdated
Show resolved
Hide resolved
...o/opentelemetry/instrumentation/spring/webflux/v5_3/SpringWebfluxServerTelemetryBuilder.java
Outdated
Show resolved
Hide resolved
* SPDX-License-Identifier: Apache-2.0 | ||
*/ | ||
|
||
package io.opentelemetry.instrumentation.spring.webflux.old.v5_3; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to move this to a non-conflicting package so both @SpringBootApplication
classes wouldn't be seen and conflict
SpringWebfluxTelemetry*
classes have been deprecated and split intoSpringWebfluxClientTelemetry*
andSpringWebfluxServerTelemetry*
Part of #12846
See #12867 for change log migration notes entry