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:

Popular posts from this blog

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.

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...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...