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
Kamon supports Context Propagation. Kamon uses AOP style code instrumentation. See #1487 for a related discussion about metrics gathering.
The question is if we could add something in Pekko itself so that we don't need to have Kamon manipulate Pekko code at runtime.
Maybe, we could allow users to opt in but when they opt in, we could include a Context object like a Map[String, String] with each message sent between actor instances.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Kamon supports Context Propagation. Kamon uses AOP style code instrumentation. See #1487 for a related discussion about metrics gathering.
The question is if we could add something in Pekko itself so that we don't need to have Kamon manipulate Pekko code at runtime.
Maybe, we could allow users to opt in but when they opt in, we could include a Context object like a
Map[String, String]
with each message sent between actor instances.https://github.com/open-telemetry/opentelemetry-java-instrumentation also supports context tracing in Pekko and Pekko HTTP and has some similarities to Kamon in the way that it uses byte-buddy to instrument our code at runtime.
Beta Was this translation helpful? Give feedback.
All reactions