kamon.instrumentation.futures.scala
ScalaFutureInstrumentation
Related Doc:
package scala
Settings for the Delayed Spans created by the traced and tracedCallback helper functions.
Traces the execution of a block of code with a Delayed Span which takes into account the scheduling time when run inside of a CallbackRunnable.
Traces the execution of a block of code with a Delayed Span which takes into account the scheduling time when run inside of a CallbackRunnable. This function is expected to be used when creating new Futures and wrapping the entire body of the Future as follows:
Future(traced("myAsyncOperationName") { // Here goes the future body. })
If the scheduling time cannot be determined this function will fall back to using a regular Span for tracking the traced operation since the only reasonable value for the scheduling time would be the start time, which would yield no wait time and the same processing and elapsed time, rendering the Delayed Span useless.
IMPORTANT: Do not use this method if you are not going to run your application with instrumentation enabled. This method contains a call to Kamon.store(...) which will only be cleaned up by the CallbackRunnable bytecode instrumentation. If instrumentation is disabled you risk leaving dirty threads that can cause incorrect Context propagation behavior.
Traces the execution of a callback on a Future with a Delayed Span which takes into account the scheduling time when run inside of a CallbackRunnable.
Traces the execution of a callback on a Future with a Delayed Span which takes into account the scheduling time when run inside of a CallbackRunnable. This function is expected to be used when creating callbacks on Futures and should wrap the entire actual callback as follows:
Future(...) .map(tracedCallback("myMapCallbackName")( // Here goes the actual callback. )) .filter(tracedCallback("myFilterCallbackName")( // Here goes the actual callback. ))
If the scheduling time cannot be determined this function will fall back to using a regular Span for tracking the traced callback since the only reasonable value for the scheduling time would be the start time, which would yield no wait time and the same processing and elapsed time, rendering the Delayed Span useless.
IMPORTANT: Do not use this method if you are not going to run your application with instrumentation enabled. This method contains a call to Kamon.store(...) which will only be cleaned up by the CallbackRunnable bytecode instrumentation. If instrumentation is disabled you risk leaving dirty threads that can cause incorrect Context propagation behavior.