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
TelemetryClientinstance 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: