Skip to content

Commit db0eb07

Browse files
Merge pull request #247422 from AaronMaxwell/aaronmax-aspnetcore-codeless-fix
Removing old ikey guidance
2 parents d93333a + 711f4d8 commit db0eb07

File tree

1 file changed

+5
-11
lines changed

1 file changed

+5
-11
lines changed
Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,14 @@
11
---
22
ms.topic: include
3-
ms.date: 09/03/2021
4-
ms.author: lagayhar
5-
author: lgayhardt
3+
ms.date: 08/04/2023
4+
ms.author: AaronMaxwell
5+
author: AaronMaxwell
66
services: azure-monitor
77
ms.subservice: application-insights
88
---
99

10-
### Connection string and instrumentation key
11-
12-
When codeless monitoring is being used, only the connection string is required. We still recommend that you set the instrumentation key to preserve backward compatibility with older versions of the SDK when manual instrumentation is being performed.
13-
1410
### What's the difference between standard metrics from Application Insights vs. Azure App Service metrics?
1511

16-
Application Insights collects telemetry for the requests that made it to the application. If the failure occurred in WebApps/WebServer, and the request didn't reach the user application, Application Insights won't have any telemetry about it.
17-
18-
The duration for `serverresponsetime` calculated by Application Insights won't necessarily match the server response time observed by Web Apps. This behavior is because Application Insights only counts the duration when the request actually reaches the user application. If the request is stuck or queued in WebServer, the waiting time will be included in the Web Apps metrics but not in Application Insights metrics.
19-
12+
Application Insights collects telemetry for the requests that made it to the application. If the failure occurs in WebApps/WebServer, and the request didn't reach the user application, Application Insights doesn't have any telemetry about it.
2013

14+
The duration for `serverresponsetime` calculated by Application Insights doesn't necessarily match the server response time observed by Web Apps. This behavior is because Application Insights only counts the duration when the request actually reaches the user application. If the request is stuck or queued in WebServer, the waiting time is included in the Web Apps metrics but not in Application Insights metrics.

0 commit comments

Comments
 (0)