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/durable-task-sdks/java/opentelemetry-tracing/README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,33 +27,33 @@ This launches:
27
27
### 2. Run the sample
28
28
29
29
```bash
30
-
./gradlew runOpenTelemetryTracingPattern
30
+
./gradlew run
31
31
```
32
32
33
33
This starts the worker, schedules an `OrderProcessingOrchestration`, and waits for it to complete.
34
34
35
35
## Viewing Traces
36
36
37
37
1. Open the Jaeger UI at **http://localhost:16686**
38
-
2. Select the **durable-worker** service from the dropdown
38
+
2. Select the **DistributedTracingSample** service from the dropdown
39
39
3. Click **Find Traces**
40
-
4. Click on a trace to see the span tree — you'll see spans for each activity (`ValidateOrder`, `ProcessPayment`, `ShipOrder`, `SendNotification`)
40
+
4. Click on the trace with **5 Spans**— you'll see the parent `create_orchestration:OrderProcessingOrchestration` with child activity spans nested underneath
You can also view the orchestration status in the DTS Dashboard at **http://localhost:8082**.
49
49
50
50
## What You'll See
51
51
52
-
The Jaeger UI shows traces for each activity in the orchestration, including timing and any errors. This helps you:
52
+
The Jaeger UI shows a single trace for the entire orchestration with nested child spans for each activity. Each span includes `durabletask.task.name`, `durabletask.type`, and `durabletask.task.task_id` tags. This helps you:
53
53
54
-
- Identify slow activities
54
+
- Identify slow activities within an orchestration
55
55
- See the sequential flow of function chaining
56
-
- Correlate traces across distributed services
56
+
- Correlate the full orchestration lifecycle in one trace
Copy file name to clipboardExpand all lines: samples/durable-task-sdks/java/opentelemetry-tracing/src/main/java/io/durabletask/samples/OpenTelemetryTracingPattern.java
Copy file name to clipboardExpand all lines: samples/durable-task-sdks/python/opentelemetry-tracing/README.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,9 +36,19 @@ This sample demonstrates how to add OpenTelemetry distributed tracing to a Durab
36
36
-**Jaeger UI:**http://localhost:16686 (search for service `durable-worker`)
37
37
-**DTS Dashboard:**http://localhost:8082
38
38
39
+
## Viewing Traces
40
+
41
+
Open the [Jaeger UI](http://localhost:16686), select the `durable-worker` service, and click **Find Traces**. You'll see one trace per activity — `validate_order`, `process_payment`, `ship_order`, and `send_notification`:
Click on any trace to see span details including tags, duration, and OpenTelemetry metadata:
46
+
47
+

48
+
39
49
## What You'll See
40
50
41
-
The Jaeger UI shows the complete trace for each orchestration — the parent orchestration span with child spans for each activity, including timing and any errors. This helps you:
0 commit comments