Skip to content

v2.1.0

Choose a tag to compare

View all tags
@eladser eladser released this 14 Jun 16:22
· 7 commits to main since this release
v2.1.0
eff6550
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Two additive features. Existing setup is unchanged, so upgrading from 2.0 needs no code changes.

OpenTelemetry tracing

Captured requests and queries are emitted as spans on an ActivitySource named AspNetDebugDashboard. Add that source to your tracer and they flow to Aspire or any OTLP backend, alongside what the dashboard stores locally:

builder.Services.AddOpenTelemetry()
    .WithTracing(t => t.AddSource("AspNetDebugDashboard").AddOtlpExporter());

The spans carry the request id, status, SQL text, and timing, back-dated to match the dashboard. They cost nothing until you add the source, so the default is fine to leave on. Turn it off with EmitActivities = false. See docs/OPENTELEMETRY.md.

MCP server

A new dotnet tool, AspNetDebugDashboard.Mcp, runs an MCP server over the dashboard's REST API so a coding agent can read recent requests, the SQL a request ran, recent failures, and performance numbers while it works on your app.

dotnet tool install --global AspNetDebugDashboard.Mcp

Eight read-only tools (recent requests, a request's SQL and logs, recent queries/exceptions/logs, performance, search). Setup in src/AspNetDebugDashboard.Mcp/README.md.

Closes #6, closes #7.

Assets 2
Loading