Adrian Cole
Adrian Cole
Ahh so this is so that the logging internal to the library is abstracted, right? Ex this is only used by tracing code.
cc @jonathan-lo and @marcingrzejszczak
thanks, yeah this will (ideally) obviate the same code in sleuth, except using the style we are using here for kafka. Plus being this will be consistent across spring and...
pretty much done here. just will make some executor based tests and also make a integration one that uses normal kafka on one side cc @shakuzen @ImFlog
@lchayoun can you please provide a test case relating to https://github.com/spring-cloud/spring-cloud-sleuth/issues/821? meanwhile I will try to guess
Thx agreed unit tests should suffice, just something higher level helps with later bug squashing. All help appreciated! On 11 Jan 2018 11:16 am, "Artem Bilan" wrote: > *@artembilan* commented...
Started porting some of sleuth's integration tests and switched the scoping mechanism to stack based
For those following along.. this creates chained spans just like in kafka. For example, the producer span starts and stops, then the consumer span, then any processor (if there is...
Here's some insights so far: Typically we think of a producer consumer model as producer starts and stops, then consumer starts and stops (queue). However, it seems spring-messaging has synchronous...
There's a small tension as we don't know if tasks are queue in nature or not until we know types or observe behavior. For example, sometimes preSend is used for...