Hi all; Is there any comprehensive documentation on connecting a Blazor server app to Application Insights? I've found the following bits and pieces: Provides some basics, but leaves a ton unanswered. Looks like a good wrapper for Blazor WASM , nothing for server :( Really comprehensive info for ASP.NET , nothing for Blazor :( thanks - dave

Hi @David Thielen , With Blazor being written on top of ASP.NET, the same logging methodologies would apply. That might be why you aren't seeing a lot of specific posts on it 🙂. You can review Application Insights logging with .NET - Azure Monitor | Microsoft Learn to use the built-in .NET logging to integrate with application insights.

Connecting Blazor server app to Application Insights

Accepted answer

Ryan Hill 29,386 Reputation points Microsoft Employee

2024-07-12T14:04:00.0266667+00:00

Hi @David Thielen,

With Blazor being written on top of ASP.NET, the same logging methodologies would apply. That might be why you aren't seeing a lot of specific posts on it 🙂.

You can review Application Insights logging with .NET - Azure Monitor | Microsoft Learn to use the built-in .NET logging to integrate with application insights.
Please sign in to rate this answer.
David Thielen 3,141 Reputation points

2024-07-12T16:25:00.3133333+00:00

@Ryan Hill - thank you, a follow up question. That link says add the following:

builder.Logging.AddApplicationInsights( configureTelemetryConfiguration: (config) => config.ConnectionString = builder.Configuration.GetConnectionString("APPLICATIONINSIGHTS_CONNECTION_STRING"), configureApplicationInsightsLoggerOptions: (options) => { } ); builder.Logging.AddFilter<ApplicationInsightsLoggerProvider>("your-category", LogLevel.Trace);

What is the AddFilter doing? I need to know in order to know what to pass as my "your-category"

thanks - dave

Ryan Hill 29,386 Reputation points Microsoft Employee

2024-07-12T19:52:45.7433333+00:00

Sure, no problem @David Thielen. Filter category basically means the runtime will inspect the namespace of what's being logged and will only allow the category that's set. Me personally, I would advise putting this as part of your appsettings.json to avoid compile/deployment changes.

Have a look at https://learn.microsoft.com/en-us/aspnet/core/fundamentals/logging/?view=aspnetcore-8.0#configure-logging for more.

David Thielen 3,141 Reputation points

2024-07-12T22:56:10.78+00:00

@ryan hill that makes sense. So it could be for example "Microsoft.AspNetCore". If so, I can understand doing that when trying to find a bug. But normally wouldn't you want all the logs? Or am I missing something here (this is new to me)?

thanks - dave

Ryan Hill 29,386 Reputation points Microsoft Employee

2024-08-08T17:59:50.0766667+00:00

@David Thielen it really depends. If you're trying to isolate a bug in your production system, then yes; you would want all the logs. But from a normal operational standpoint, it's customary to have just enough logs that provide enough traceability that allows you to investigate issues in your system. For instance, you may want to log warnings and errors of Microsoft.AspNetCore namespace but not the debug and traces. But you would want to log the majority of what's within your app's namespace.

Nonetheless, it's completely up to you how much or how little you want to log.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Connecting Blazor server app to Application Insights

0 additional answers

Your answer