diff --git a/spring-cloud.html b/spring-cloud.html index 9e4c24ef..126fb373 100644 --- a/spring-cloud.html +++ b/spring-cloud.html @@ -600,7 +600,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
`@StreamListener and Message Conversion@StreamListener and Message Conversion`@StreamListener and Message Conversion@StreamListener and Message ConversionThe @StreamListener annotation provides a convenient way for converting incoming messages without the need to specify the content type of an input channel.
During the dispatching process to methods annotated with @StreamListener, a conversion will be applied automatically if the argument requires it.
http:path when received an http request on a given path
controller-method-name when received by a Controller with a method name conrollerMethodName
async for asynchronous operations done via wrapped Callable and Runnable.
spring.sleuth.rxjava.schedulers.ignoredthrea
Since we want the span names to be precise we’re using a TraceHandlerInterceptor that either wraps an
+ existing HandlerInterceptor or is added directly to the list of existing HandlerInterceptors. The
+ TraceHandlerInterceptor adds a special request attribute to the given HttpServletRequest. If the
+ the TraceFilter doesn’t see this attribute set it will create a "fallback" span which is an additional
+ span created on the server side so that the trace is presented properly in the UI. Seeing that most likely
+ signifies that there is a missing instrumentation. In that case please file an issue in Spring Cloud Sleuth.
If your controller returns a Callable or a WebAsyncTask Spring Cloud Sleuth will continue the existing span instead of creating a new one.