From 4446b76e415dc5f5be318d562d75393c48e534e2 Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Fri, 29 Sep 2023 15:47:03 +0200 Subject: [PATCH] Added clarification for Reactive Suppliers you must fallback to Spring Integration instrumentation for reactive suppliers. related commit https://github.com/spring-cloud/spring-cloud-function/commit/a32d239c1f51e52535f7e4de033c008bd78e7be9 --- docs/src/main/asciidoc/integrations.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/src/main/asciidoc/integrations.adoc b/docs/src/main/asciidoc/integrations.adoc index 5e3a366b4..94ad7db40 100644 --- a/docs/src/main/asciidoc/integrations.adoc +++ b/docs/src/main/asciidoc/integrations.adoc @@ -459,6 +459,8 @@ For a reactive `Consumer>>` remember to manually close the span } ---- +For Sleuth to work with a reactive `Supplier` (e.g. `Supplier>>`) you must fall back to Spring Integration based instrumentation by setting `spring.sleuth.integration.enabled` to `true`. + You can disable Spring Cloud Stream integration by setting the value of `spring.sleuth.function.enabled` to `false`. If you want to fully control the life cycle of spans within the reactive messaging context of Spring Cloud Stream