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-monitor/profiler/profiler-troubleshooting.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,6 +74,28 @@ Search for trace messages and custom events sent by Profiler to your Application
74
74
75
75
If no records are displayed, Profiler isn't running or took too long to respond. Make sure [Profiler is enabled on your Azure service](./profiler.md).
76
76
77
+
## Profiler is on, but no traces captured
78
+
79
+
Even when the Profiler is enabled, it may not capture or upload traces, especially in these situations:
80
+
81
+
1.**No incoming requests to your application:**
82
+
You can manually invoke your application or create an [availability test](../app/availability.md), or a [load test](../../load-testing/overview-what-is-azure-load-testing.md).
83
+
84
+
1.**No incoming telemetry acknowledged by Application Insights:**
85
+
- If there is traffic coming to your application: validate that there are incoming requests showing in Application Insights [Live Metrics](../app/live-stream.md).
86
+
- If the `Incoming Requests` charts are empty (no data or showing zero): [troubleshoot Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/asp-net-troubleshoot-no-data).
87
+
- If you are hosting your .NET application on Azure App Service: [try the App Service .NET troubleshooting steps](../app/azure-web-apps-net.md#troubleshooting).
88
+
89
+
1.**Profiler setting for Sampling is turned off:**
90
+
If still no profiler traces are available, check the Profiler Sampling setting.
91
+
1. Open **Application Insights** > **Performance** blade.
92
+
1. Click on **Profiler**.
93
+
1. Click on the **Triggers** button.
94
+
1. In the Trigger Settings, ensure the **Sampling** toggle is on.
95
+
96
+
1.**Still no traces uploaded?**
97
+
[Create a support request](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview?DMC=troubleshoot), or ask [Azure community support](/answers/products/azure?product=all). You can also submit product feedback to [Azure feedback community](https://feedback.azure.com/d365community).
98
+
77
99
## Double counting in parallel threads
78
100
79
101
When two or more parallel threads are associated with a request, the total time metric in the stack viewer might be more than the duration of the request. In that case, the total thread time is more than the actual elapsed time.
0 commit comments