Skip to main content

Cloudbrew 2022–Advanced telemetry with Azure Monitor Application Insights

This weekend I had the honor to speak at CloudBrew, a 2 day conference organized by AZUG, the Belgium Microsoft Azure User Group.

I really enjoyed the conference; great sessions, nice location, good food. I had the time to chat up with some other community members.

Advanced telemetry with Azure Monitor Application Insights

I did a session about Application Insights:

You've added the Application Insights NuGet or NPM package to your application, but now what? This demo-driven session will show you how to get the maximum out of Application Insights and achieve true insights in your application behavior and performance. Profiling, dependency tracking, snapshots, extensibility, availability,... no feature remains untouched.

In case you are looking for my slides, they can be found here: https://github.com/wullemsb/presentations/tree/main/CloudBrew%20-%202022

During my presentation I used 2 demo applications. They are both an adaption of the eShopOnWeb reference application.

One application shows how to implement the Application Insights SDK in an ASP.Net Core Razor Pages and Blazor application:

https://github.com/wullemsb/presentations/tree/main/CloudBrew%20-%202022/eShopOnWeb%20-%20AppInsights

The other application shows how to implement OpenTelemetry in your ASP.NET Core application and send this telemetry data to Application insights:

 https://github.com/wullemsb/presentations/tree/main/CloudBrew%20-%202022/eShopOnWeb%20-%20OpenTelemetry

I’ve written a list of related blog posts(and more will come). Check them all out here: https://bartwullems.blogspot.com/search?q=application+insights

Labels:

Popular posts from this blog

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

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
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