Skip to content

Commit 8c782bc

Browse files
kainawrothkainawroth
committed
More testing
1 parent 9e025be commit 8c782bc

1 file changed

Lines changed: 16 additions & 98 deletions

File tree

‎support/azure/azure-monitor/app-insights/telemetry/troubleshoot-app-service-issues.md‎

Lines changed: 16 additions & 98 deletions
Original file line numberDiff line numberDiff line change
@@ -203,37 +203,27 @@ If you're missing telemetry, follow these steps to confirm that autoinstrumentat
203203

204204
---
205205

206-
## Default website deployed with web apps doesn't support automatic client-side monitoring
206+
## Language-specific troubleshooting
207207

208-
### [ASP.NET](#tab/net)
208+
### Default website deployed with web apps doesn't support automatic client-side monitoring
209+
210+
### [ASP.NET](#tab/net-1)
209211

210212
When you create a web app with the ASP.NET runtimes in App Service, it deploys a single static HTML page as a starter website. The static webpage also loads an ASP.NET-managed web part in IIS. This page allows for testing codeless server-side monitoring but doesn't support automatic client-side monitoring.
211213

212214
If you want to test out codeless server and client-side monitoring for ASP.NET in an App Service web app, we recommend following the official guides for [creating an ASP.NET Framework web app](/azure/app-service/quickstart-dotnetcore?tabs=netframework48). Afterwards, use the instructions in the current article to enable monitoring.
213215

214-
### [ASP.NET Core](#tab/aspnetcore)
216+
### [ASP.NET Core](#tab/aspnetcore-1)
215217

216218
When you create a web app with the ASP.NET Core runtimes in App Service, it deploys a single static HTML page as a starter website. The static webpage also loads an ASP.NET-managed web part in IIS. This behavior allows for testing codeless server-side monitoring but doesn't support automatic client-side monitoring.
217219

218220
If you want to test out codeless server and client-side monitoring for ASP.NET Core in an App Service web app, we recommend following the official guides for [creating an ASP.NET Core web app](/azure/app-service/quickstart-dotnetcore). Afterwards, use the instructions in the current article to enable monitoring.
219221

220-
## [Java](#tab/java)
221-
222-
N/A
223-
224-
## [Node.js](#tab/nodejs)
225-
226-
N/A
227-
228-
## [Python](#tab/python)
229-
230-
N/A
231-
232222
---
233223

234-
## APPINSIGHTS_JAVASCRIPT_ENABLED and urlCompression not supported
224+
### APPINSIGHTS_JAVASCRIPT_ENABLED and urlCompression not supported
235225

236-
### [ASP.NET](#tab/net)
226+
### [ASP.NET](#tab/net-1)
237227

238228
If you use `APPINSIGHTS_JAVASCRIPT_ENABLED=true` in cases where content is encoded, you might get errors like:
239229

@@ -244,7 +234,7 @@ An error occurs because the `APPINSIGHTS_JAVASCRIPT_ENABLED` application setting
244234

245235
For the latest information on the Application Insights agent/extension, see the [release notes](https://github.com/MohanGsk/ApplicationInsights-Home/blob/master/app-insights-web-app-extensions-releasenotes.md).
246236

247-
### [ASP.NET Core](#tab/aspnetcore)
237+
### [ASP.NET Core](#tab/aspnetcore-1)
248238

249239
PHP and WordPress sites aren't supported. There's currently no officially supported SDK/agent for server-side monitoring of these workloads. To track client-side transactions on a PHP or WordPress site, add the client-side JavaScript to your webpages using the [JavaScript SDK](/azure/azure-monitor/app/javascript-sdk).
250240

@@ -256,23 +246,11 @@ The following table provides an explanation of what these values mean, their und
256246
| `AppAlreadyInstrumented:true` | The presence of `Microsoft.ApplicationsInsights` DLL in the app folder from a previous deployment can also cause this value. | Clean the app folder to ensure that these DLLs are removed. Check both your local app's bin directory and the *wwwroot* directory on the App Service. (To check the wwwroot directory of your App Service web app, select **Advanced Tools (Kudu**) > **Debug console** > **CMD** > **home\site\wwwroot**). |
257247
| `IKeyExists:false` | This value indicates that the instrumentation key isn't present in the app setting `APPINSIGHTS_INSTRUMENTATIONKEY`. Possible causes include accidentally removing the values or forgetting to set the values in automation script. | Make sure the setting is present in the App Service application settings. |
258248

259-
### [Java](#tab/java)
260-
261-
N/A
262-
263-
### [Node.js](#tab/nodejs)
264-
265-
N/A
266-
267-
### [Python](#tab/python)
268-
269-
N/A
270-
271249
---
272250

273-
## PHP and WordPress aren't supported
251+
### PHP and WordPress aren't supported
274252

275-
### [ASP.NET](#tab/net)
253+
### [ASP.NET](#tab/net-1)
276254

277255
PHP and WordPress sites aren't supported. There's currently no officially supported SDK/agent for server-side monitoring of these workloads. To track client-side transactions on a PHP or WordPress site, add the client-side JavaScript to your webpages using the [JavaScript SDK](/azure/azure-monitor/app/javascript-sdk).
278256

@@ -286,7 +264,7 @@ The following table provides an explanation of what these values mean, their und
286264
| `AppContainsDiagnosticSourceAssembly**:true`| This value indicates that the extension detected references to `System.Diagnostics.DiagnosticSource` in the application and backs off.| For ASP.NET, remove the reference. |
287265
| `IKeyExists:false` | This value indicates that the instrumentation key isn't present in the app setting `APPINSIGHTS_INSTRUMENTATIONKEY`. Possible causes might be that the values were accidentally removed, or you forgot to set the values in the automation script. | Make sure the setting is present in the App Service application settings. |
288266

289-
### [ASP.NET Core](#tab/aspnetcore)
267+
### [ASP.NET Core](#tab/aspnetcore-1)
290268

291269
PHP and WordPress sites aren't supported. There's currently no officially supported SDK/agent for server-side monitoring of these workloads. To track client-side transactions on a PHP or WordPress site, add the client-side JavaScript to your webpages using the [JavaScript SDK](/azure/azure-monitor/app/javascript-sdk).
292270

@@ -298,23 +276,11 @@ The following table provides an explanation of what these values mean, their und
298276
| `AppAlreadyInstrumented:true` | The presence of `Microsoft.ApplicationsInsights` DLL in the app folder from a previous deployment can also cause this value. | Clean the app folder to ensure that these DLLs are removed. Check both your local app's bin directory and the *wwwroot* directory on the App Service. (To check the wwwroot directory of your App Service web app, select **Advanced Tools (Kudu**) > **Debug console** > **CMD** > **home\site\wwwroot**). |
299277
| `IKeyExists:false` | This value indicates that the instrumentation key isn't present in the app setting `APPINSIGHTS_INSTRUMENTATIONKEY`. Possible causes include accidentally removing the values or forgetting to set the values in automation script. | Make sure the setting is present in the App Service application settings. |
300278

301-
### [Java](#tab/java)
302-
303-
N/A
304-
305-
### [Node.js](#tab/nodejs)
306-
307-
N/A
308-
309-
### [Python](#tab/python)
310-
311-
N/A
312-
313279
---
314280

315281
## System.IO.FileNotFoundException after 2.8.44 upgrade
316282

317-
### [ASP.NET](#tab/net)
283+
### [ASP.NET](#tab/net-2)
318284

319285
The 2.8.44 version of autoinstrumentation upgrades Application Insights SDK to 2.20.0. The Application Insights SDK has an indirect reference to `System.Runtime.CompilerServices.Unsafe.dll` through `System.Diagnostics.DiagnosticSource.dll`. If the application has [binding redirect](/dotnet/framework/configure-apps/file-schema/runtime/bindingredirect-element) for `System.Runtime.CompilerServices.Unsafe.dll` and if this library isn't present in the application folder, it might throw `System.IO.FileNotFoundException`.
320286

@@ -329,43 +295,11 @@ To resolve this issue, remove the binding redirect entry for `System.Runtime.Com
329295

330296
As a temporary workaround, you could set the app setting `ApplicationInsightsAgent_EXTENSION_VERSION` to a value of `2.8.37`. This setting triggers App Service to use the old Application Insights extension. Temporary mitigations should only be used as an interim.
331297

332-
### [ASP.NET Core](#tab/aspnetcore)
333-
334-
N/A
335-
336-
### [Java](#tab/java)
337-
338-
N/A
339-
340-
### [Node.js](#tab/nodejs)
341-
342-
N/A
343-
344-
### [Python](#tab/python)
345-
346-
N/A
347-
348298
---
349299

350-
## Duplicate telemetry
351-
352-
### [ASP.NET](#tab/net)
353-
354-
N/A
355-
356-
### [ASP.NET Core](#tab/aspnetcore)
357-
358-
N/A
359-
360-
### [Java](#tab/java)
300+
### Duplicate telemetry
361301

362-
N/A
363-
364-
### [Node.js](#tab/nodejs)
365-
366-
N/A
367-
368-
### [Python](#tab/python)
302+
### [Python](#tab/python-3)
369303

370304
Only use autoinstrumentation on App Service if you aren't using manual instrumentation of OpenTelemetry in your code, such as the [Azure Monitor OpenTelemetry Distro](/azure/azure-monitor/app/opentelemetry-enable?tabs=python) or the [Azure Monitor OpenTelemetry Exporter](/python/api/overview/azure/monitor-opentelemetry-exporter-readme).
371305

@@ -375,25 +309,9 @@ If you're seeing unexpected charges or high costs in Application Insights, this
375309

376310
---
377311

378-
## Django apps
379-
380-
### [ASP.NET](#tab/net)
312+
### Django apps
381313

382-
N/A
383-
384-
### [ASP.NET Core](#tab/aspnetcore)
385-
386-
N/A
387-
388-
### [Java](#tab/java)
389-
390-
N/A
391-
392-
### [Node.js](#tab/nodejs)
393-
394-
N/A
395-
396-
### [Python](#tab/python)
314+
### [Python](#tab/python-3)
397315

398316
If your app uses Django and is either failing to start or using incorrect settings, make sure to set the `DJANGO_SETTINGS_MODULE` environment variable. See the [Django Instrumentation](/azure/azure-monitor/app/codeless-app-service#django-instrumentation) section for details.
399317

0 commit comments

Comments
 (0)