Mediarq.Aspire
1.5.1
dotnet add package Mediarq.Aspire --version 1.5.1
NuGet\Install-Package Mediarq.Aspire -Version 1.5.1
<PackageReference Include="Mediarq.Aspire" Version="1.5.1" />
<PackageVersion Include="Mediarq.Aspire" Version="1.5.1" />
<PackageReference Include="Mediarq.Aspire" />
paket add Mediarq.Aspire --version 1.5.1
#r "nuget: Mediarq.Aspire, 1.5.1"
#:package Mediarq.Aspire@1.5.1
#addin nuget:?package=Mediarq.Aspire&version=1.5.1
#tool nuget:?package=Mediarq.Aspire&version=1.5.1
Mediarq.Aspire
One call from your project's own ServiceDefaults Extensions.cs wires Mediarq's OpenTelemetry
instrumentation and handler-registration health check into the .NET Aspire dashboard.
dotnet add package Mediarq.Aspire --project MyApp.ServiceDefaults
Usage
This is additive, not a replacement — call it from inside the AddServiceDefaults() method that
dotnet new aspire-servicedefaults already generated for you, alongside its own OpenTelemetry, service
discovery and resilience setup:
// MyApp.ServiceDefaults/Extensions.cs
public static IHostApplicationBuilder AddServiceDefaults(this IHostApplicationBuilder builder)
{
builder.ConfigureOpenTelemetry(); // generated by the template
builder.AddDefaultHealthChecks(); // generated by the template
builder.Services.AddServiceDiscovery();
builder.AddMediarqServiceDefaults(typeof(Program).Assembly); // <- add this
return builder;
}
That single call:
- Subscribes the tracer/meter providers to Mediarq's
Mediarqactivity source and meter (same as callingMediarq.OpenTelemetry'sAddMediarqInstrumentation()yourself), so Mediarq dispatch spans and metrics show up in the Aspire dashboard next to everything else. - Registers
Mediarq.HealthChecks' handler-registration check, so a command/query that doesn't resolve to exactly one handler surfaces as an unhealthy check in the dashboard instead of only failing at the first dispatch in production.
It does not reimplement OpenTelemetry/service-discovery/resilience wiring, health-check endpoint
mapping (/health, /alive), or anything else the Aspire template's own ServiceDefaults project already
gives you — only the Mediarq-specific pieces are added on top.
Learn more
Wiring extensions · Full README
MIT © Nicolas Rouffart
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Mediarq.HealthChecks (>= 1.5.1)
- Mediarq.OpenTelemetry (>= 1.5.1)
- OpenTelemetry.Extensions.Hosting (>= 1.16.0)
-
net8.0
- Mediarq.HealthChecks (>= 1.5.1)
- Mediarq.OpenTelemetry (>= 1.5.1)
- OpenTelemetry.Extensions.Hosting (>= 1.16.0)
-
net9.0
- Mediarq.HealthChecks (>= 1.5.1)
- Mediarq.OpenTelemetry (>= 1.5.1)
- OpenTelemetry.Extensions.Hosting (>= 1.16.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.