diff --git a/src/docs/asciidoc/70-observability.adoc b/src/docs/asciidoc/70-observability.adoc
new file mode 100644
index 00000000..bf469bf6
--- /dev/null
+++ b/src/docs/asciidoc/70-observability.adoc
@@ -0,0 +1,26 @@
+[[observability]]
+= Observing Application Modules
+:imagesdir: images
+
+The interaction between application modules can be intercepted to create Micrometer spans to ultimately end up in traces you can visualize in tools like https://zipkin.io/[Zipkin].
+To activate the instrumentation add the following runtime dependency to your project:
+
+[source, xml]
+----
+<dependency>
+  <groupId>org.springframework.modulith</groupId>
+  <artifactId>spring-modulith</artifactId>
+  <version>{projectVersion}</version>
+  <scope>runtime</scope
+</dependency
+----
+
+This will cause all Spring components that are part of the application module's API being decorated with an aspect that will intercept invocations and create Micrometer spans for them.
+A sample invocation trace can be seen below:
+
+.A sample module invocation trace
+image::observability.png[]
+
+In this particular case, triggering the payment changes the state of the order which then causes an order completion event being triggered.
+This gets picked up asynchronously by the engine that triggers another state change on the order, works for a couple of seconds and triggers the final state change on the order in turn.
+
diff --git a/src/docs/asciidoc/images/observability.png b/src/docs/asciidoc/images/observability.png
new file mode 100644
index 00000000..f0aa9de0
Binary files /dev/null and b/src/docs/asciidoc/images/observability.png differ
diff --git a/src/docs/asciidoc/index.adoc b/src/docs/asciidoc/index.adoc
index aeacb2a7..95e6c54c 100644
--- a/src/docs/asciidoc/index.adoc
+++ b/src/docs/asciidoc/index.adoc
@@ -25,6 +25,8 @@ include::50-moments.adoc[]
 
 include::60-documentation.adoc[]
 
+include::70-observability.adoc[]
+
 include::90-appendix.adoc[]
 
 :leveloffset: -1