-
Notifications
You must be signed in to change notification settings - Fork 327
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
[Feature request] Support instrumentation of akka typed actors #679
Comments
Any plans on proceeding with this feature request? |
Is there any open-tracing solution for akka typed ?! |
Can you point me to any specific problems you have with akka-typed actors? |
@SimunKaracic docker run -d --name jaeger \
-e COLLECTOR_ZIPKIN_HTTP_PORT=9411 \
-p 5775:5775/udp \
-p 6831:6831/udp \
-p 6832:6832/udp \
-p 5778:5778 \
-p 16686:16686 \
-p 14268:14268 \
-p 14250:14250 \
-p 9411:9411 \
jaegertracing/all-in-one:1.20 and setup configs to this
public class Main {
public static void main(String[] args) {
Kamon.init();
ActorSystem.create(MainSystem.create(), MainSystem.NAME);
}
} but nothing I saw in Jaeger client at all, i saw just Jaeger query traces of itself. then I saw this issue, so i was thinking, kamon library may not working for typed, and then i ask the question ... Any extra thing I forgot to do ? |
Try adding If that doesn't work, you can try sharing the code with me so I can try and reproduce it! |
Also, actors won't start spans by themselves, they'll merely be part of the trace. |
Current examples in the documentation show context propagation with classic actors and they don't mention anything about akka-typed. So, does context propagation actually work with akka-typed? If so, how does it pass the context? |
Typed actors get transformed into untyped actors of class
Are you refering to this page? https://kamon.io/docs/latest/instrumentation/akka/context-propagation/ If you have a specific example, let me know, we want typed actors to have the same coverage as classic ones |
Yes, I was referring to that page. I think even if examples are with classic actors, it would be good to list akka-typed support as an explicit feature in the documentation. I doubt I was the only one who got the impression that Kamon only supports untyped actors. Apart from that, I don't have a concrete example of something that's not working in akka-typed and am looking forward to start using Kamon in akka-typed systems now. Thanks! |
We're updating the documentation to show a akka-typed example! |
From akka 2.6.x, akka typed actors APIs are marked as stable.
It would be really nice to provide support for typed actors.
The text was updated successfully, but these errors were encountered: