Stratara.ServiceDefaults.AspNetCore
4.4.8
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.ServiceDefaults.AspNetCore --version 4.4.8
NuGet\Install-Package Stratara.ServiceDefaults.AspNetCore -Version 4.4.8
<PackageReference Include="Stratara.ServiceDefaults.AspNetCore" Version="4.4.8" />
<PackageVersion Include="Stratara.ServiceDefaults.AspNetCore" Version="4.4.8" />
<PackageReference Include="Stratara.ServiceDefaults.AspNetCore" />
paket add Stratara.ServiceDefaults.AspNetCore --version 4.4.8
#r "nuget: Stratara.ServiceDefaults.AspNetCore, 4.4.8"
#:package Stratara.ServiceDefaults.AspNetCore@4.4.8
#addin nuget:?package=Stratara.ServiceDefaults.AspNetCore&version=4.4.8
#tool nuget:?package=Stratara.ServiceDefaults.AspNetCore&version=4.4.8
Stratara.ServiceDefaults.AspNetCore
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
ASP.NET Core extensions on top of Stratara.ServiceDefaults. Reference from every API host.
What's in the box
| Extension | Purpose |
|---|---|
AddDefaultHealthChecks |
Registers a self-tagged health check that always reports Healthy + tags it as live so the /alive predicate can filter on it. |
MapDefaultEndpoints |
Maps /health (full health-check report) and /alive (only the live-tagged checks). |
ConfigureAspNetOpenTelemetry |
Wires ASP.NET Core request instrumentation on metrics + tracing; filters out the health-check + aliveness endpoints from traces so they don't pollute the request stream. |
Quick start
builder.ConfigureOpenTelemetry(); // from Stratara.ServiceDefaults
builder.ConfigureAspNetOpenTelemetry(); // from this package
builder.AddDefaultHealthChecks();
builder.ConfigureSerilog(); // from Stratara.ServiceDefaults
var app = builder.Build();
app.MapDefaultEndpoints();
Dependencies
Stratara.ServiceDefaults— baseConfigureOpenTelemetryand shared endpoint constants.OpenTelemetry.Extensions.Hosting+OpenTelemetry.Instrumentation.AspNetCore.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | 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
- OpenTelemetry.Extensions.Hosting (>= 1.20.1)
- OpenTelemetry.Instrumentation.AspNetCore (>= 1.20.1)
- Stratara.ServiceDefaults (>= 4.4.8)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.4.10 | 0 | 10/26/2026 |
| 4.4.9 | 0 | 10/26/2026 |
| 4.4.8 | 173 | 10/24/2026 |
| 4.4.7 | 66 | 10/23/2026 |
| 4.4.6 | 185 | 10/22/2026 |
| 4.4.5 | 276 | 10/14/2026 |
| 4.4.4 | 282 | 10/10/2026 |
| 4.4.3 | 110 | 10/10/2026 |
| 4.4.2 | 384 | 10/2/2026 |
| 4.4.1 | 359 | 9/29/2026 |
| 4.4.0 | 125 | 9/27/2026 |
| 4.3.1 | 131 | 9/25/2026 |
| 4.3.0 | 302 | 9/23/2026 |
| 4.2.0 | 148 | 9/18/2026 |
| 4.1.1 | 87 | 9/16/2026 |
| 4.1.0 | 101 | 9/16/2026 |
| 4.0.4 | 828 | 9/14/2026 |
| 4.0.3 | 115 | 9/3/2026 |
| 4.0.2 | 604 | 9/3/2026 |
| 4.0.1 | 406 | 9/2/2026 |
A fix for hosts on the Orleans execution model. A store reader that catches up a large backlog and a singleton
work that runs long now answer their keep-alive, so neither leaves reminder errors in the silo's log. A silo that
joins while a singleton work runs long on another silo no longer fails its start. No API change, no schema change
and no migration.
### Fixed
- **A busy store reader or singleton work answers its keep-alive.** On the Orleans execution model, a projection or
saga reader that caught up a backlog for longer than the runtime's response timeout made its keep-alive tick wait
behind the catch-up, and Orleans logged `Could not deliver reminder tick` at Error, once per partition and
keep-alive period. A singleton work whose run outlasted the timeout did the same. Nothing was lost, but a large
catch-up left dozens of errors on the silo. The keep-alive and the poll now start a catch-up where none is
running and do not wait for it. A partition is still read by one catch-up at a time, and a commit during a
catch-up is still applied by it. A singleton work's keep-alive interleaves with its run, and runs still never
overlap.
- **A silo starts while a singleton work runs long.** A silo that started while a singleton work it registers ran
longer than the response timeout on another silo waited for that run in its own start. The start then failed
with a `TimeoutException`. The call a starting silo makes to each singleton work and store reader now
interleaves, so the start goes on.
- *Operate the Orleans execution model* says that a durable timer whose handler outlasts the response timeout
still makes Orleans log `Could not deliver reminder tick` for that tick, and that the line says nothing about
the timer. It also says that, outside a deploy, the line now points to an unreachable store reader or singleton
work rather than a busy one.