Skip to content

Commit 2944c51

Browse files
Merge pull request #234059 from hhunter-ms/hh-84426
[Profiler] Add paragraph to await_time section
2 parents 7b67194 + 1673e01 commit 2944c51

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

articles/azure-monitor/profiler/profiler-data.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: Generate load and view Application Insights Profiler data
33
description: Generate load to your Azure service to view the Profiler data
44
ms.contributor: charles.weininger
55
ms.topic: conceptual
6-
ms.date: 07/15/2022
7-
ms.reviewer: jogrima
6+
ms.date: 04/11/2023
7+
ms.reviewer: charles.weininger
88
---
99

1010
# View Application Insights Profiler data
@@ -117,6 +117,12 @@ Methods such as **SqlCommand.Execute** indicate that the code is waiting for a d
117117

118118
However, logically, the thread that did the **AWAIT** is "blocked", waiting for the operation to finish. The **AWAIT\_TIME** statement indicates the blocked time, waiting for the task to finish.
119119

120+
If the **AWAIT_TIME** appears to be in framework code instead of your code, the Profiler could be showing:
121+
- The framework code used to execute the **AWAIT**
122+
- Code used for recording telemetry about the **AWAIT**
123+
124+
You can uncheck the **Framework dependencies** checkbox at the top of the page to show only your code and make it easier to see where the **AWAIT** originates.
125+
120126
### Blocked time
121127

122128
**BLOCKED_TIME** indicates that the code is waiting for another resource to be available. For example, it might be waiting for:

0 commit comments

Comments
 (0)