Stratara.ServiceDefaults.AspNetCore
3.1.5
See the version list below for details.
dotnet add package Stratara.ServiceDefaults.AspNetCore --version 3.1.5
NuGet\Install-Package Stratara.ServiceDefaults.AspNetCore -Version 3.1.5
<PackageReference Include="Stratara.ServiceDefaults.AspNetCore" Version="3.1.5" />
<PackageVersion Include="Stratara.ServiceDefaults.AspNetCore" Version="3.1.5" />
<PackageReference Include="Stratara.ServiceDefaults.AspNetCore" />
paket add Stratara.ServiceDefaults.AspNetCore --version 3.1.5
#r "nuget: Stratara.ServiceDefaults.AspNetCore, 3.1.5"
#:package Stratara.ServiceDefaults.AspNetCore@3.1.5
#addin nuget:?package=Stratara.ServiceDefaults.AspNetCore&version=3.1.5
#tool nuget:?package=Stratara.ServiceDefaults.AspNetCore&version=3.1.5
Stratara.ServiceDefaults.AspNetCore
License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.
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.15.3)
- OpenTelemetry.Instrumentation.AspNetCore (>= 1.15.2)
- Stratara.ServiceDefaults (>= 3.1.5)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Added
- **Configurable snapshot strategy** (`Stratara.Abstractions`, `Stratara.Infrastructure`) — the
snapshot cadence is no longer hard-coded. A new `Stratara.Abstractions.EventSourcing.ISnapshotStrategy`
decides, per stream, whether the event-sourcing runtime should write a snapshot:
`bool ShouldSnapshot(Type aggregateType, long currentVersion, long lastSnapshotVersion)`.
`AddEventSourcing()` registers the default `VersionThresholdSnapshotStrategy` (snapshot every 50
versions — identical to the previous behaviour) via `TryAddSingleton`, so existing consumers see no
change. To take over the policy, register your own singleton `ISnapshotStrategy` (it overrides the
default whether registered before or after `AddEventSourcing()`): vary the threshold per aggregate
type, construct `new VersionThresholdSnapshotStrategy(threshold)` for a different uniform cadence, or
register `NoSnapshotStrategy` to disable snapshotting entirely. This replaces the previously
hard-coded `UseSnapshots`/`SnapshotRange` constants in the default snapshot service, which were not
actually configurable despite the documentation implying they were.
- **`AddDomainEventTypesFromAssemblyContaining<T>()`** (`Stratara.Abstractions`) — registers *only* the
domain event types consumed by an assembly's aggregate `Apply(TEvent)` methods in the trusted-type
resolver, without registering the aggregate types themselves and without pulling any projection / saga
/ command-handler classes into DI. Use it in a host that only needs to deserialize event payloads off
the message bus or event stream — typically a dedicated projection or saga worker — but must not wire
the handler classes (and their runtime dependencies) that `AddProjectionsFromAssemblyContaining<T>`
would register. Complements the existing `AddAggregatesFromAssemblyContaining<T>` (which additionally
registers the aggregate types) and `AddTrustedType<T>` (single type).