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

.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