Hi,
We've been trying to set up codeless monitoring of our ASP .NET application using Application Insights following the directions for monitoring an Azure VM:
https://learn.microsoft.com/en-us/azure/azure-monitor/app/azure-vm-vmss-apps
We've successfully configured the extension on the VM, but see almost no telemetry reported in the Application Insights resource we've set up in the Azure portal.
The now no longer recommended Application Insights Status Monitor (https://learn.microsoft.com/en-us/azure/azure-monitor/app/monitor-performance-live-website-now) worked a bit better for us.
I've noticed that the old monitor used to inject the app insights SDK .dlls and an applicationinsights.config file into our deployed web app. Are these artifacts still required when using the Azure extension?
Is there something else we should be looking for to ensure that our application is actually connected to app insights?
We're currently testing with the default instrumentationKeyMap in our extension configuration:
"instrumentationKeyMap": {
"filters": [
{
"appFilter": ".*",
"machineFilter": ".*",
"virtualPathFilter": ".*",
"instrumentationSettings" : {
"connectionString": "InstrumentationKey=<our-application-insights-instrumentation-key>"
}
}
]
}
Are there any examples or documentation available that demonstrate how to properly configure the machineFilter and appFilter options with values other than "match everything"?
Thanks for any ideas!