The Kronikol.Extensions.BlobStorage package adds Azure Blob Storage operation tracking to your test diagrams. Instead of showing raw HTTP requests like PUT /mycontainer/myblob.txt?comp=blocklist, your sequence diagrams show classified operations like Upload: /mycontainer/myblob.txt or ListBlobs: /mycontainer.

Using a shared library or abstraction layer? If your code doesn't use the Blob Storage SDK directly — e.g. it goes through a shared storage library, wrapper, or custom abstraction — this extension won't be able to intercept the underlying calls. See Tracking Custom Dependencies for alternative approaches including RequestResponseLogger.LogPair(), TrackingProxy<T>, and MessageTracker.

The Azure Blob Storage SDK translates all operations into HTTP requests to the Azure Storage REST API. BlobTrackingMessageHandler is a DelegatingHandler that intercepts these HTTP requests, classifies each one into a Blob operation (Upload, Download, Delete, ListBlobs, etc.) using the HTTP method, URL path, and query parameters, then logs it to RequestResponseLogger with a human-readable label.

Because it logs to the same RequestResponseLogger as the standard TestTrackingMessageHandler, Blob Storage operations appear alongside your HTTP API calls in the same sequence diagram — showing the complete flow from test → API → Blob Storage.

dotnet add package Kronikol.Extensions.BlobStorage

The extension supports three verbosity levels that control how much detail appears in the diagrams:

The default is Detailed.

The classifier recognises these Blob Storage operations from the SDK's HTTP traffic:

In Summarised mode, Other operations are silently skipped.

var trackingOptions = new BlobTrackingMessageHandlerOptions
{
    ServiceName = "BlobStorage",
    CallerName = "My API",
    Verbosity = BlobTrackingVerbosity.Detailed,
    CurrentTestInfoFetcher = CurrentTestInfo.Fetcher
};

var clientOptions = new BlobClientOptions();
clientOptions.WithTestTracking(trackingOptions);

var client = new BlobServiceClient(connectionString, clientOptions);

WithTestTracking sets the Transport property on BlobClientOptions to route all HTTP requests through the tracking handler.

If you need more control over the HTTP pipeline:

var trackingOptions = new BlobTrackingMessageHandlerOptions
{
    ServiceName = "BlobStorage",
    CallerName = "My API",
    Verbosity = BlobTrackingVerbosity.Detailed,
    CurrentTestInfoFetcher = CurrentTestInfo.Fetcher
};

var trackingHandler = new BlobTrackingMessageHandler(trackingOptions);
var httpClient = new HttpClient(trackingHandler);
var transport = new Azure.Core.Pipeline.HttpClientTransport(httpClient);

var clientOptions = new BlobClientOptions
{
    Transport = transport
};

var client = new BlobServiceClient(connectionString, clientOptions);

builder.ConfigureTestServices(services =>
{
    // Replace BlobServiceClient with one that uses the tracking transport
    services.AddSingleton(sp =>
    {
        var trackingOptions = new BlobTrackingMessageHandlerOptions
        {
            ServiceName = "BlobStorage",
            CallerName = "My API",
            Verbosity = BlobTrackingVerbosity.Detailed,
            CurrentTestInfoFetcher = CurrentTestInfo.Fetcher
        };

        var clientOptions = new BlobClientOptions();
        clientOptions.WithTestTracking(trackingOptions);

        return new BlobServiceClient("UseDevelopmentStorage=true", clientOptions);
    });
});

v2.23.0+ Dual-Resolution: BlobTrackingMessageHandler accepts an optional IHttpContextAccessor? httpContextAccessor constructor parameter for resolving test identity from HTTP request headers when running inside the SUT's request pipeline. v2.26.3+: Set HttpContextAccessor on BlobTrackingMessageHandlerOptions instead — the tracker reads it automatically. See HTTP Tracking Setup#Dual-Resolution Test Identity (v2.23.0+) for details.

The following Azure Storage headers are excluded by default (they add noise without diagnostic value):

• Authorization
• x-ms-date
• x-ms-version
• x-ms-client-request-id
• x-ms-return-client-request-id
• User-Agent
• Cache-Control

Override ExcludedHeaders to customise:

new BlobTrackingMessageHandlerOptions
{
    ExcludedHeaders = ["Authorization", "x-ms-date"] // Only exclude these two
}

Every framework package provides a CurrentTestInfo static class with a Fetcher property. The syntax is identical regardless of framework - just ensure you have the correct using directive:

CurrentTestInfoFetcher = CurrentTestInfo.Fetcher

public static BlobClientOptions WithTestTracking(
    this BlobClientOptions options,
    BlobTrackingMessageHandlerOptions trackingOptions,
    HttpMessageHandler? innerHandler = null)

Configures BlobClientOptions to use BlobTrackingMessageHandler. Sets options.Transport to an HttpClientTransport backed by an HttpClient wrapping the tracking handler. The optional innerHandler parameter sets the inner handler (defaults to HttpClientHandler).

BlobTrackingMessageHandler implements ITrackingComponent and auto-registers with TrackingComponentRegistry on construction. At report generation time, unused components are automatically detected and surfaced as console warnings and in the diagnostic report (when DiagnosticMode=true). This never throws or fails tests.

See Diagnostics and Debugging for full details on the TrackingComponentRegistry API.