This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Application Insights is a useful tool to monitor service performance whether for data analysis or debugging purpose. While it comes with Windows-based .NET Web Apps by default when creating the app from Azure Portal, it is missing on Linux platform. This article will give instructions on how to integrate App Insights with Linux .NET Web App so that we can enjoy the similar experience on Linux.
Generally speaking, with Linux .NET Web Apps, we need to leverage App Insights SDK to collect telemetries and send them over to App Insights server. After that, App Insights Portal page will be able to retrieve and display metrics and logs.
Using .NET 5 MVC app as an example, only 6 steps needed to enable server-side monitoring:
1. Create Application Insights resource via Azure Portal. Normally, make App Insights in the same region with the Web App so that data transmission can be faster.
2. Jot down the Instrumentation Key on the Overview blade of the App Insights created.
3. Add app setting “APPINSIGHTS_INSTRUMENTATIONKEY = YourAppInsightsInstrumentationKey” to your web app.
4. Add below reference in your project's .csproj file.
<PackageReference Include="Microsoft.ApplicationInsights.AspNetCore" Version="2.16.0" />
5. Add services.AddApplicationInsightsTelemetry(); to the ConfigureServices() method in your Startup class.
public void ConfigureServices(IServiceCollection services)
// The following line enables Application Insights telemetry collection.
// This code adds other services for your application.
6. Rebuild and redeploy your web app.
If client-side telemetry is also desired, there are additional 2 steps before recompiling the code:
1. In _ViewImports.cshtml, add injection:
2. In _Layout.cshtml, insert HtmlHelper at the end of the <head> section but before any other script.
A common use case is troubleshooting site slowness. Performance bottleneck can be narrowed down with the help of App Insights End-to-end transaction details. With the transaction flow in place, we can easily tell if bottleneck is with the application itself or some external dependencies like database. In other words, we can ensure our next investigation is on the right track.