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: articles/azure-functions/durable/durable-functions-troubleshooting-guide.md
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ Use the following steps to troubleshoot stuck orchestrations:
54
54
55
55
1. Try restarting the function app. This step can help if the orchestration gets stuck due to a transient bug or deadlock in either the app or the extension code.
56
56
57
-
2. Check the Azure Storage account control queues to see if any queues are growing continuously. [This query](./durable-functions-troubleshooting-guide.md#azure-storage-messaging)could indicate a problem with dequeuing orchestration messages. If the problem impacts only a single control queue, it might indicate a problem that exists only on a specific app instance, in which case scaling up or down to move off the unhealthy VM instance could help.
57
+
2. Check the Azure Storage account control queues to see if any queues are growing continuously. [This Azure Storage messaging KQL query](./durable-functions-troubleshooting-guide.md#azure-storage-messaging)can help identify problems with dequeuing orchestration messages. If the problem impacts only a single control queue, it might indicate a problem that exists only on a specific app instance, in which case scaling up or down to move off the unhealthy VM instance could help.
58
58
59
59
3. Use the Application Insights query in the [Azure Storage Messaging section](./durable-functions-troubleshooting-guide.md#azure-storage-messaging) to filter on that queue name as the Partition ID and look for any problems related to that control queue partition.
60
60
@@ -83,11 +83,11 @@ When using the default storage provider, all Durable Functions behavior is drive
83
83
84
84
Starting in v2.3.0 of the Durable Functions extension, you can have these Durable Task Framework logs published to your Application Insights instance by updating your logging configuration in the host.json file. See the [Durable Task Framework logging article](./durable-functions-diagnostics.md) for information and instructions on how to do this.
85
85
86
-
The following query is for inspecting end-to-end Azure Storage interactions for a specific orchestration instance. Edit `start` and `queryInstanceId` to filter by time range and instance ID.
86
+
The following query is for inspecting end-to-end Azure Storage interactions for a specific orchestration instance. Edit `start` and `orchestrationInstanceID` to filter by time range and instance ID.
87
87
88
88
```kusto
89
89
let start = datetime(XXXX-XX-XXTXX:XX:XX); // edit this
90
-
let queryInstanceId = "XXXXXXX"; //edit this
90
+
let orchestrationInstanceID = "XXXXXXX"; //edit this
91
91
traces
92
92
| where timestamp > start and timestamp < start + 1h
93
93
| where customDimensions.Category == "DurableTask.AzureStorage"
| where severityLevel > 1 // to see all logs of severity level "Information" or greater.
132
-
| where instanceId == queryInstanceId
132
+
| where instanceId == orchestrationInstanceID
133
133
| sort by timestamp asc
134
134
```
135
135
136
136
### Control queue / Partition ID logs
137
-
The following query searches for activity associated with an instanceId's control queue. You'll need to provide the value for the instanceID in `queryInstanceId` as well as the query's start time in `start`.
137
+
The following query searches for activity associated with an instanceId's control queue. You'll need to provide the value for the instanceID in `orchestrationInstanceID` as well as the query's start time in `start`.
138
138
139
139
```kusto
140
-
let queryInstanceId = "XXXXXX"; // edit this
140
+
let orchestrationInstanceID = "XXXXXX"; // edit this
141
141
let start = datetime(XXXX-XX-XXTXX:XX:XX); // edit this
142
142
traces // determine control queue for this orchestrator
143
143
| where timestamp > start and timestamp < start + 1h
Below is a list of the columns projected by the queries above and their respective descriptions.
175
176
176
177
|Column |Description |
177
178
|-------|------------|
178
179
|pid|Process ID of the function app instance. This is useful for determining if the process was recycled while an orchestration was executing.|
179
180
|taskName|The name of the event being logged.|
180
181
|eventType|The type of message, which usually represents work done by an orchestrator. A full list of its possible values, and their descriptions, is [here](https://github.com/Azure/durabletask/blob/main/src/DurableTask.Core/History/EventType.cs)|
181
-
|extendedSession|Boolean value indicating whether [ExtendedSessions](durable-functions-azure-storage-provider.md#extended-sessions) is enabled.|
182
+
|extendedSession|Boolean value indicating whether [extended sessions](durable-functions-azure-storage-provider.md#extended-sessions) is enabled.|
182
183
|account|The storage account used by the app.|
183
184
|details|Additional information about a particular event, if available.|
184
185
|instanceId|The ID for a given orchestration or entity instance.|
0 commit comments