Skip to main content

Help! My Application Insights telemetry stopped working.

I want to start this blog post by stating that I have a new hero and his name is Stijn. Let me explain why…

I recently upgraded an older .NET Full Framework application to the latest Application Insights NuGet package. This to make the switch from the obsolete instrumentationkey to the newer connectionstring approach.

After upgrading our packages.config file (yes, this project is so old) looked like this:

Looking good right? Unfortunately, the same could not be said about our telemetry itself as our Application Insights logs remained awfully empty.

I doublechecked all the config files, reinstalled the nuget packages, tried to explicitly force to flush the telemetry data, everything I could think of I tried. But nothing worked.

I handed the problem over to another team member (Stijn, my new hero) and he found the solution. After debugging the Application Insights code he arrived at a no-op method:

This method should have all the logic to read the configuration information and configure Application Insights for this ASP.NET MVC application. But as the method is empty, nothing is happening.

The root cause

After upgrading, the NuGet package manager silently switched from the .NET Framework 4.6 version to the .NET Standard version of Application Insights. Here's the problem: the .NET Standard version doesn't read configuration from your app.config or web.config files and provides only a void (no-op) implementation.

This means our application was running with Application Insights "installed" but completely non-functional—no telemetry, no logging, nothing.

The solution

To solve the problem, we changed the hintpath in the csproj that originally pointed to the .NET Standard version:

And updated it to the .NET46 version:

That fixed the problem. Great!

Thank you Stijn! I would never have found this one…

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.

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

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...