Maui Insights gives you a simple way to add Application Insights telemetry to your .NET Maui app.

To use it, simply call .AddApplicationInsights() with your AI connection string, and optionally call .AddCrashLogging() to also log any uncaught exceptions to Application Insights. See the example below:

using MauiInsights;

public static class MauiProgram
{
	public static MauiApp CreateMauiApp()
	{
		var builder = MauiApp.CreateBuilder();
		builder
			.UseMauiApp<App>()
			.AddApplicationInsights("<connection string>")
			.AddCrashLogging();

		return builder.Build();
	}
}

Maui Insights provides the following:

Similar to default implementations in .NET Web applications.

Whenever a page is visited, a pageView event is sent to Application Insights

When using HttpClientFactory, any Http calls are automatically tracked as dependency calls. In addition, OpenTelemetry headers are added to the request so calls can be correlated across your applications. This includes libraries like Refit.

When manually constructing HttpClient or HttpMessageHandler instances, the DependencyTrackingHandler class can be used to manually add this functionality.

When using .AddCrashLogging(), any uncaught exceptions are written to the platforms default cache directory. On the next app start, if the device has an internet connection, these crash logs are then sent to Application Insights as exceptions.

An singleton instance of TelemetryClient is registered and available for any manual telemetry

If you want to extend your telemetry, use the .AddApplicationInsights() overload that accepts a MauiInsightsConfiguration. You can either add custom keyvalue pairs which will be added to the additional properties of the telemetry, or you can implement your own instances of ITelemetryInitializer to modify any telemetry that is sent.