You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I add a @NewSpan annotation on a method of an interface, then I will expect the implementation class to start a new span if that method is called.
Actual Behaviour
The implementation class method does not start a new span when called. It does work if I place the annotation on the method of the implentation class directly.
Steps To Reproduce
Create an interface (Interface A) with a method annotated with @NewSpan.
Create a class (Class A) and implement the interface. Annotate the class with @singleton.
Create another class (Class B) with a method which is annotated with @NewSpan. Annotate the class with @singleton.
Start the application and let it inject Interface A and Class B.
Call the methods.
The call to Interface A does not start a new span. The call to Class B does start a new span.
Downgrade micronaut-tracing-zipkin and micronaut-tracing-core to 4.1.1. Now both calls create new spans.
Expected Behavior
When I add a @NewSpan annotation on a method of an interface, then I will expect the implementation class to start a new span if that method is called.
Actual Behaviour
The implementation class method does not start a new span when called. It does work if I place the annotation on the method of the implentation class directly.
Steps To Reproduce
micronaut-tracing-zipkin
andmicronaut-tracing-core
to 4.1.1. Now both calls create new spans.Environment Information
Example Application
https://github.com/joellp/micronaut-tracing-issue
Version
3.7.3
The text was updated successfully, but these errors were encountered: