Skip to main content

Azure Application Insights–Angular integration

To get the most out of Application Insights when building a Single Page Application, some specific tweaks are required. Let's walk through the steps to get Application Insights configured in your Angular application.

I expect that you already configured an Application Insights resource in the Azure Portal and have an existing Angular application.

Step 1 -  Add dependencies and configuration settings

We’ll start by adding an extra dependency ‘@microsoft/applicationinsights-web’ to our package.json:

We also update our environment.ts file to store our Application Insights instrumentation key there:

Step 2 – Create an Angular Service to wrap the Application Insights SDK

We create an Angular service that we will use as a wrapper around the Application Insights SDK. Here we inject the AppInsights class.

Notice that we set both the ‘enableCorsCorrelation’ and ‘enableAutoRouteTracking’ to true. This will correctly inject a correlation-id in our request headers and will track all route changes as navigation events.

We can further expand this service with extra methods to explicitly call specific functionality of the Application Insights SDK:

Step 3 – Consume the service in our Angular application

To consume the service as soon as the application starts, we’ll inject it in our AppComponent:

We can go one step further by creating our own ErrorHandler instance so that all client side exceptions are nicely logged in Application Insights:

Don’t forget to configure the AppModule to use this handler:

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more