Skip to content

Commit 947fb2a

Browse files
authored
Update durable-functions-diagnostics.md
1 parent 32f42d9 commit 947fb2a

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

articles/azure-functions/durable/durable-functions-diagnostics.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -539,26 +539,28 @@ Clients will get the following response:
539539
> The custom status payload is limited to 16 KB of UTF-16 JSON text because it needs to be able to fit in an Azure Table Storage column. You can use external storage if you need larger payload.
540540
541541
## Distributed Tracing
542-
Distributed Tracing tracks requests and shows how different services interact with each other. In Durable Functions, it also correlates orchestrations and activities together. This is helpful to understand where an application is having an issue or where an exception was thrown. This feature is supported for all languages and storage providers.
542+
543+
Distributed Tracing tracks requests and shows how different services interact with each other. In Durable Functions, it also correlates orchestrations and activities together. This is helpful to understand how much time steps of the orchestration take relative to the entire orchestration. It is also usefult to understand where an application is having an issue or where an exception was thrown. This feature is supported for all languages and storage providers.
543544

544545
> [!NOTE]
545-
> This is a preview feature so there are some features that are not supported. For example, Durable entities are not supported yet.
546+
> Distributed Tracing V2 requires a minimum version of [Durable Functions v2.12.0](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.DurableTask/2.12.0). Also, Distributed Tracing V2 is in a preview state and therefore some Durable Functions patterns are not instrumented and unsupported with distributed tracing. For example, Durable Entities operations are not instrumented and traces will not show up in Application Insights.
546547
547548
### Setting up Distributed Tracing
549+
548550
To set up distributed tracing, please update the host.json and set up an Application Insights resource.
549551

550552
#### host.json
551553
```
552554
"durableTask": {
553555
"tracing": {
554-
"DistributedTracingEnabled": true,
556+
"distributedTracingEnabled": true,
555557
"Version": "V2"
556558
}
557559
}
558560
```
559561

560562
#### Application Insights
561-
Create an Application Insights resource and set the connection string as a value for `APPLICATIONINSIGHTS_CONNECTION_STRING`.
563+
If the Function app is not configured with an Application Insights resource, then please configure it following the instructions [here](../configure-monitoring.md#enable-application-insights-integration).
562564

563565
### Inspecting the traces
564566
In the Application Insights resource, navigate to **Transaction Search**. In the results, check for `Request` and `Dependency` events that start with Durable Functions specific prefixes (e.g. `orchestration:`, `activity:`, etc.). Selecting one of these events will open up a Gantt chart that will show the end to end distributed trace.

0 commit comments

Comments
 (0)