I have Application Insights SKD on a ASP.NET application, but i can't see data on Azure Portal, I have followed the official documentation for troubleshoot and the connectivity with dc.services.visualstudio.com seems to be fine but i can't connect to f5.services.visualstudio.com, but f5.services.visualstudio.com seems not used anymore, I can't access it inside and outside of my network.
The account have access to Performance Logs too, and I uninstalled the SCOM Monitoring Agent to prevent problems, but still no data!
Check that assemblies are included in your project
Check you have last SDK version of Application Insights installed
Check ApplicationInsights.config file exists in the root of application and instrumentation key is presented
If you resolve InstrumentationKey from web.config or from another place, debug your application and ensure the InstrumentationKey is really resolved
Check your telemetries are collecting using the Visual Studio Diagnostics Hub (developer mode must be set to TRUE - by default)
Try to send more telemetries or change the flush interval to 0
First place where you can check your telemetries is Azure Portal - Diagnostic Search blade
Try to check quotas on Azure Portal
Related
I have an Application Insights in Azure. There are some ASP.NET web applications deployed in Azure virtual machine which sends data to that Application Insights.
The problem is when I am going to 'Configure Application Insights Profiler' (under 'performance' tab and then 'configure profiler') in the Application Insights, it is showing me a message 'We detected one or more of your apps are using an older profiler agent. You must be on latest agent to get the new trigger-based profiling feature. Click here to learn more'.
When I am going to the link it is asking to check Windows Azure Diagnostics (WAD) extension version in the virtual machine location 'C:\Packages\Plugins\Microsoft.Azure.Diagnostics.IaaSDiagnostics'.
I have created a list of applications which are having the INSTRUMENTATION KEY in their web.config of the particular Application Insights. I logged into each of the virtual machines where those applications are deployed and checked the location. All of them are having the latest Windows Azure Diagnostics (WAD) extension installed on them.
At this point I have no idea about the reason of the message. Can you tell me, is there a easy way to check for which application it is showing the message?
Hi #DeveloperArnab are you still facing this issue? This is usually caused by one of your applications being on an older version of the agent or one of the apps sampling out application insights telemetry
We enabled application insights via azure portal some time ago. Everything worked great and we want to log bit extra custom information. So we will have to include appInsight SDK and create TelemetryClient and RequestTelemetry in our code now.
Ideally, we would like to enable the exact same setting as we enabled in azure portal (e.g. enable profiling, recommended collection level, sql command and disable Snapshot debugger).
However, when I look at the appinsight config file, I realised that this file is way more complicated than what azure portal offers.
Is there a way to convert what we enabled on azure portal to the config file?
Or if I delete this config file (just add the custom field in our c# RequestTelemetry instance), will appInsights use settings from azure portal automatically?
If you are using Asp.Net Application, installing SDK by default will generate the full ApplicationInsights.Config file for you, which would do same level of monitoring as Recommended level.
https://learn.microsoft.com/en-us/azure/azure-monitor/app/asp-net
And follow this to get full SQL Text:
https://learn.microsoft.com/en-us/azure/azure-monitor/app/asp-net-dependencies#advanced-sql-tracking-to-get-full-sql-query
If you are using Asp.Net Core Application, installing SDK by default will automatically configure everything in code (there is no ai.config in asp.net core apps).
https://learn.microsoft.com/en-us/azure/azure-monitor/app/asp-net-core
You dont need to do anything additional to get full SQL Text in Asp.Net Core apps.
SnapShotCollector is not enabled by default, so you dont need to do anything to disable it.
Profiler: https://learn.microsoft.com/en-us/azure/azure-monitor/app/profiler#enable-profiler-manually-or-with-azure-resource-manager
For application insights, maybe you know that there is 2 ways to apply Application Insights to your .NET web applications(For details, please refer to here).
Build time: add application insights sdk
Run time: via azure portal without adding sdk to your project.
And the screenshot below shows the difference of them(you can ignore the Note section about build-time and run-time in this article, this gives users confusion and an issue is tracking that):
And for your issues, I suggest you'd better use both of them: adding sdk and also enable/disable profiler / snapshot debugger / sql command via azure portal.
I did some tracing about sql command before, without enable from azure portal, you cannot get a details sql command info from application insights with just adding sdk. Not make some changes via config file.
And there're also described in docs like below, take profiler for example:
In the profiler doc, it says: Follow these steps even if you've included the App Insights SDK in your application at build time.
And also, it would be more difficult to change appinsight config file to meet your need, there is even no official doc about these for apply profiler / sql command via config file.
I just found a blog about how to configure snapshot debugger via appinsight config file, you can take a look and try it at your side.
I set up Application Insights on my asp.net core (2.2) app. I can see data in Azure portal when I run my application locally. However, once I deploy it to App Service in Azure, Application Insights stop working - there is no data flow at all. Are there any additional steps I am missing?
Adding to Stuart's comments- > If you edited ApplicationInsights.config, kindly check the configuration of TelemetryInitializers and TelemetryProcessors. An incorrectly-named type or parameter can cause the SDK to send no data.
Also, in the Application Insights portal, open Diagnostic Search. Data usually appears here first. Refresh to see if it helps.
If feasible, you may restart the app and check to see if that helps.
I am using application insight for measuring performance and also storing some telemetry data of my web application and it was working fine till last month.
But from last month I am unable to see any traffic in app insight. In last month just I have added one slot in my app service. I have checked instrumentation key, it's same and correct and there is no change in application settings and configuration in app service.
Could you please suggest me if any additional settings I need to take care ?
I suspect this issue is due to adding of slot because in other environment it's working fine.
You could go to Visual Studio configure Application Insights through there and then redeploy the application to slot.
For more information, you could refer to this doc: Application Insights support for Multiple Environments, Stamps and App Versions, , specifically the 'Multi Stamp Support'.
How are you enabling application insights for the App in Azure Web App? Are you using extensions or do you take nuget dependency at build time?
If using extension, please navigate to this url to find the status of application insights enablement: https://yoursitename.scm.azurewebsites.net/ApplicationInsights
Have you ensured that that instrumentation key is available in all slots? This is most likely an instrumentation key issue.
I have published an app to Windows Store. Subscribed to Azure.
It seems I can only deploy/create new Application Insights resource.
How to add/link the instrumentation key found in Windows Dev Center App Analytics / Usage page to Azure Portal / Application Insights?
If you follow the standard getting started flow for Application Insights. Use the InstrumentationKey that the AI portal provides. Specify the iKey in the ApplicationInsights.config file. If the key is in the .config file, the Windows Dev Center should pick up the key as part of the ingestion / publishing process.
As one of the comments indicated, you can use these instructions to add Application Insights Nuget to your application and insert the instrumentation key in code or in ApplicationInsights.config file.
However please note that while you can still use Application Insights for Windows Store apps, we are recommending that you onboard to this Nuget and start using HockeyApp for Windows Store apps: