Skip to main content

Azure Application Insights–MassTransit integration

One of the features that Application Insights has to offer is ‘Dependency Tracking'. It allows you to monitor components that are called by your application. This can be a service called using HTTP, or a database, or a file system. Application Insights measures the duration of dependency calls, whether its failing or not, along with additional information like name of dependency and so on. You can investigate specific dependency calls, and correlate them to requests and exceptions.

Automatically tracked dependencies

Out-of-the-box the following dependencies are tracked automatically:

Dependencies Details
Http/Https Local or Remote http/https calls.
WCF Calls Only tracked automatically if Http-based bindings are used.
SQL SQL Calls made with SqlClient.
Azure storage Calls made with Azure Storage Client.
EventHub Client SDK   EventHub Client SDK Version 1.1.0 and above.
ServiceBus Client SDK ServiceBus Client SDK Version 3.0.0 and above.
Azure Cosmos DB Only tracked automatically if HTTP/HTTPS is used. TCP mode won't be captured by Application Insights.

Setup dependency tracking for MassTransit

To extend dependency tracking and track calls to MassTransit we need to configure the built-in DependencyTrackingTelemetryModule and include an extra ‘MassTransit’ diagnostic source:

After adding this code, you should see the MassTransit calls show up as dependencies in your Telemetry data:

And here are the details:

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:

Angular --deploy-url and --base-href

As long you are running your Angular application at a root URL (e.g. ) you don’t need to worry that much about either the ‘--deploy-url’ and ‘--base-href’ parameters. But once you want to serve your Angular application from a server sub folder(e.g. ) these parameters become important. --base-href If you deploy your Angular app to a subfolder, the ‘--base-href’ is important to generate the correct routes. This parameter will update the <base href> tag inside the index.html. For example, if the index.html is on the server at /angularapp/index.html , the base href should be set to <base href="/angularapp/"> . More information: --deploy-url A second parameter that is important is ‘--deploy-url’. This parameter will update the generated url’s for our assets(scripts, css) inside the index.html. To make your assets available at /angularapp/, the deploy url should

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.