You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: samples/README.md
+11-13Lines changed: 11 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,39 +39,37 @@ docker run -d --name jaeger \
39
39
40
40
## What the Sample Does
41
41
42
-
The `TracingPattern` sample:
42
+
The `TracingPattern` sample demonstrates the **Fan-Out/Fan-In** pattern with distributed tracing:
43
43
44
44
1. Configures OpenTelemetry with an OTLP exporter pointing to Jaeger
45
45
2. Connects a worker and client to the DTS emulator using a connection string
46
-
3. Creates a parent span (`create_orchestration:TracingOrchestration`) and schedules an orchestration
47
-
4. The orchestration chains three activities (`Reverse`, `Capitalize`, `AddSuffix`) and a sub-orchestration (`ChildOrchestration`)
46
+
3. Creates a parent span (`create_orchestration:FanOutFanIn`) and schedules an orchestration
47
+
4. The orchestration fans out 5 parallel `GetWeather` activities (Seattle, Tokyo, London, Paris, Sydney), fans in the results, then calls `CreateSummary` to aggregate
48
48
5. The SDK automatically propagates trace context through the full execution chain
49
49
50
50
## Screenshots
51
51
52
52
### Jaeger — Trace Search Results
53
53
54
-
Shows the trace from `durabletask-java-tracing-sample` service with 10 spans covering the full orchestration lifecycle.
54
+
Shows the trace from `durabletask-java-tracing-sample` service with spans covering the full fan-out/fan-in orchestration lifecycle.
0 commit comments