Skip to main content

Azure Application Insights - Tracking Operations in a Console App

If you are using the Application Insights SDK inside your ASP.NET (Core) application, every incoming HTTP request will start an operation context and will allow you track this request including any dependencies called along the way. But if you are using a console application(as a batch job for example) , there isn't the concept of an incoming request so the SDK doesn't track a lot out-of-the-box.

Configure your Console app to use Application Insights

Let me show you how you can still track operations in a Console App.

  • Start by adding the Microsoft.ApplicationInsights.WorkerService nuget package to your console app:

dotnet add package Microsoft.ApplicationInsights.WorkerService

  • Now you can add the bootstrapping logic to configure App Insights for your console app:
  • The code above will build up the required services and allows you to resolve a TelemetryClient instance that we’ll use in the next part.
    • Remark: Notice the FlushAsync method at the end to make sure that all telemetry data is sent to Azure.

Track operations manually

To track operations manually we need to invoke the StartOperation() method on the TelemetryClient instance.

The StartOperation() method returns an IOperationHolder<> that will stop the operation once disposed. It is also possible to explicitly call the StopOperation() method.

Every call that we do inside the using block will be linked to the same operation:

If you look at how the data arrives in Application Insights, you see that is nicely correlated.

Here is the Transaction Search view:

And here is the same operation queried using KQL:

 

More information:

Labels:

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

.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

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