A simple tool for tracking Database and Http calls per ASP.NET Core request.
Supports .NET 10 and .NET 11.
Install the NuGet package:
Install-Package NimblePros.Metronome
dotnet add package NimblePros.MetronomeRefer to the sample in the sample directory.
builder.Services.AddMetronome();Add the middleware near the top of the pipeline. Recommended to be used only in development environment.
if (app.Environment.IsDevelopment())
{
app.UseMetronomeLoggingMiddleware();
}builder.Services.AddDbContext<ApplicationDbContext>((provider, options) =>
options.UseSqlite(connectionString) // or any other provider
.AddMetronomeDbTracking(provider)
);Use the AddDbContext overload that takes the service provider, as shown. AddDbContextPool and AddDbContextFactory aren't supported, because they build the options once and share them across requests.
Inject the scoped DbCallCounter and pass it as the first argument of a Dapper call. Calls are counted with any EF Core calls in the same request.
using NimblePros.Metronome;
public class OrdersService(IDbConnection connection, DbCallCounter counter)
{
public Task<IEnumerable<Order>> ListAsync(int customerId) =>
connection.QueryAsync<Order>(counter, "SELECT * FROM Orders WHERE CustomerId = @customerId", new { customerId });
}Available with sync and async versions: Query<T>, QueryFirst<T>, QueryFirstOrDefault<T>, QuerySingle<T>, QuerySingleOrDefault<T>, Execute, and ExecuteScalar<T>. Other Dapper methods, such as multi-mapping queries and QueryMultiple, are not tracked.
Only calls made during a request are tracked. Calls made elsewhere, such as from a hosted service, are sent as usual without being counted.
// simple named client
builder.Services.AddHttpClient("Foo")
.AddMetronomeHandler();
// strongly typed client
builder.Services.AddScoped<IPostsService, PostsService>(); // interface is optional
builder.Services.AddHttpClient<IPostsService, PostsService>()
.ConfigureHttpClient(client =>
{
client.BaseAddress = new Uri("https://my-json-server.typicode.com/typicode/demo/");
})
.AddMetronomeHandler();When hitting individual pages or endpoints, you should see the following output in the console:
info: NimblePros.Metronome.CombinedCallLoggingMiddleware[0]
Database calls: 2, Total time: 6.4678 ms
info: NimblePros.Metronome.CombinedCallLoggingMiddleware[0]
HTTP calls: 1, Total time: 222.3137 ms
In addition, the information is added to a NimblePros.Metronome response header:
NimblePros.Metronome: DbCallCount=2;DbCallDuration=6.4678ms;HttpCallCount=1;HttpCallDuration=222.3137ms
You can use this to identify slow pages or endpoints and optimize them by adding caching, combining queries, or reducing the number of HTTP calls.
If you need help doing this in an effective way across your entire application, contact NimblePros. We do this all the time.