I've been building AspNetDebugDashboard on and off for a while. It's my take on Laravel Telescope for ASP.NET Core: you add one NuGet package, and in Development you get a page at /_debug with every request your app handled, the EF Core queries each one ran, outgoing HttpClient calls, logs and exceptions.
The part that always bugged me was the request detail. You'd open a slow request and get tabs. 21 queries in one of them, an HTTP call in another, 393 ms at the top, and adding it up was on you. So in 2.5 the detail opens on a timeline instead.
The sample app has a report endpoint I wrote to be slow on purpose. It loads 20 orders, fetches each order's items in a loop, and then calls a shipping-rates service that takes 300 ms:
foreach (var o in orders)
o.OrderItems = await db.OrderItems.Where(i => i.OrderId == o.Id).ToListAsync();
Each bar starts where the query or call really started. The 20 item queries run one after another, so they step down the page, and since it's the same SQL every time they get grouped as ×20. The HTTP call doesn't start until they're all done. The line on top adds it up: 85 ms of SQL, 302 ms of HTTP, about 6 ms of everything else.
About those 85 ms. The sample uses SQLite, which runs in-process, and there an N+1 costs next to nothing. I added a 4 ms delay to every command so it behaves like a database on the other side of a network. Your numbers will be whatever your database gives you.
Replay
Next to copy-as-cURL there's a Replay button now. It opens the request with the method, path, headers and body filled in, you change whatever you want, and it sends it again from the browser. The new request gets captured like any other and shows up next to the original.
The report endpoint takes a ?batched=true switch that loads everything with one Include and reuses the shipping rates from the previous call. I added it to the path and hit send:
393 ms down to 6, and 21 queries down to 1. To be fair to the numbers, most of that time is the skipped HTTP call. The batching is where the 20 queries went.
Replay can't send what it never stored. Authorization isn't captured by default, so you paste it back in yourself, and a browser won't let a page set Host or Origin. Razor form posts usually come back 400 because the antiforgery token gets redacted along with anything else named "token". The troubleshooting doc has the full list.
Trying it
dotnet add package AspNetDebugDashboard
builder.Services.AddDebugDashboard();
builder.Services.AddDbContext<AppDbContext>((sp, options) =>
{
options.UseSqlServer(connectionString);
options.AddDebugDashboard(sp);
});
var app = builder.Build();
app.UseDebugDashboard();
Then open /_debug. Everything stays in a local LiteDB file, and it only turns on in Development unless you say otherwise. It runs on .NET 8 through 11. It's meant for your own machine while you work. For production you still want an APM, and if a request crosses several services, Aspire's dashboard handles that much better.
If you use a coding agent, a separate MCP package lets it read the same data, and as of 2.5 that includes the timings.
Code and issues: https://github.com/eladser/AspNetDebugDashboard
NuGet: https://www.nuget.org/packages/AspNetDebugDashboard
Release notes: https://github.com/eladser/AspNetDebugDashboard/releases/tag/v2.5.0



Top comments (0)