Stratara.ServiceDefaults 4.7.0

Prefix Reserved
dotnet add package Stratara.ServiceDefaults --version 4.7.0
                    
NuGet\Install-Package Stratara.ServiceDefaults -Version 4.7.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Stratara.ServiceDefaults" Version="4.7.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.ServiceDefaults" Version="4.7.0" />
                    
Directory.Packages.props
<PackageReference Include="Stratara.ServiceDefaults" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Stratara.ServiceDefaults --version 4.7.0
                    
#r "nuget: Stratara.ServiceDefaults, 4.7.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Stratara.ServiceDefaults@4.7.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Stratara.ServiceDefaults&version=4.7.0
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.ServiceDefaults&version=4.7.0
                    
Install as a Cake Tool

Stratara.ServiceDefaults

Derived. The behaviour described here is specified under openspec/specs/. Those specifications are the source; this page explains and illustrates them.

License: MIT.

Cross-host observability defaults for the Stratara stack. Reference from every host (API, worker) to get OpenTelemetry + Serilog wired up with sensible defaults.

What's in the box

Extension Purpose
ConfigureOpenTelemetry Logging + metrics + tracing with HTTP, EF Core, RabbitMQ, runtime instrumentation; OTLP exporter wired up automatically when OTEL_EXPORTER_OTLP_ENDPOINT is set. Accepts optional MeterProviderBuilder / TracerProviderBuilder callbacks for host-specific extras.
ConfigureSerilog Structured logging with destructuring attributes, async console sink, OTLP sink (gRPC or HTTP/Protobuf based on OTEL_EXPORTER_OTLP_PROTOCOL), dev-mode log cleanup at {Path.GetTempPath()}/stratara-logs/{service-name}.log — the OS temp directory, so not literally /tmp on Windows or macOS.
ConfigureSerilogBootstrapLogger Sets up Log.Logger as a bootstrap logger before the host is built, so early-startup errors surface to the console.

Quick start

builder.ConfigureOpenTelemetry();
builder.ConfigureSerilog();

It deletes your development log file on start-up

In the Development environment only, configuring Serilog deletes the current log file before opening it: %TEMP%/stratara-logs/{OTEL_SERVICE_NAME}.log, where the service name falls back to Unknown when OTEL_SERVICE_NAME is unset. The intent is a clean file per debugging session rather than one that grows across dozens of restarts.

Two consequences worth knowing before they cost you an hour:

  • A crash you wanted to read is gone the moment you restart to reproduce it. Copy the file before restarting, or point the sink elsewhere for that session.
  • Two development services with no OTEL_SERVICE_NAME share Unknown.log and delete each other's. Set the variable per service.

Outside Development nothing is deleted.

Sibling packages

  • Stratara.EventSourcing.WorkerDefaults — one-stop AddBackendServices / AddXxxWorkerServices composites that wire the framework's mediator + outbox + projections + sagas stack.
  • Stratara.ServiceDefaults.AspNetCore — ASP.NET-specific extras: AddDefaultHealthChecks + MapDefaultEndpoints (/health, /alive) and ASP.NET request OTel instrumentation.

Dependencies

  • Stratara.Shared — diagnostics base (ApplicationDiagnostics.Activity.SourceName).
  • OpenTelemetry runtime + exporter packages.
  • Serilog sinks (Console, File, Async, OpenTelemetry).
  • Destructurama.Attributed for destructuring conventions.
  • Microsoft.Extensions.Http.Resilience + Microsoft.Extensions.ServiceDiscovery.

Prerelease dependencies. This package transitively pulls in two prerelease OpenTelemetry instrumentation packages that have no stable release yet: OpenTelemetry.Instrumentation.EntityFrameworkCore (beta) and RabbitMQ.Client.OpenTelemetry (RC). Both ride the stable OpenTelemetry 1.15.x core. NU5104 is suppressed in this csproj with that justification — consumers inherit the prerelease deps transitively. We will swap to GA as soon as the vendors ship stable.

Product 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on Stratara.ServiceDefaults:

Package Downloads
Stratara.ServiceDefaults.AspNetCore

ASP.NET Core extensions on top of Stratara.ServiceDefaults — default health checks, /health and /alive endpoints, and ASP.NET request OpenTelemetry instrumentation. Reference from every API host.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.7.0 3 10/30/2026
4.6.1 55 10/29/2026
4.6.0 91 10/28/2026
4.5.0 208 10/28/2026
4.4.10 166 10/26/2026
4.4.9 74 10/26/2026
4.4.8 218 10/24/2026
4.4.7 84 10/23/2026
4.4.6 177 10/22/2026
4.4.5 248 10/14/2026
4.4.4 261 10/10/2026
4.4.3 92 10/10/2026
4.4.2 362 10/2/2026
4.4.1 343 9/29/2026
4.4.0 113 9/27/2026
4.3.1 109 9/25/2026
4.3.0 279 9/23/2026
4.2.0 129 9/18/2026
4.1.1 89 9/16/2026
4.1.0 83 9/16/2026
Loading failed

A release for one person who belongs to several tenants — and, sharing one identity store, to several applications.

### Added

- **`MembershipStatus.Former`** records a member who has left. It confers nothing — no role, permission or
 cross-tenant access, never the tenant at sign-in, never a selection — and stays listed until the user's or the
 tenant's erasure removes it.
- **`AddCheckedMembershipTenantClaim<TUser>()`**, a third tenant-claim mode: the claim is stamped at sign-in, kept when
 the security-stamp validator refreshes a cookie sign-in, and checked on every request. A request whose user is no
 longer an active member of the carried tenant loses the claim and resolves to the reserved default tenant, without
 another tenant substituted. Only principals ASP.NET Identity issued are checked; an API key or a token the host
 mints keeps its tenant. The tenant changes only when the host re-issues the sign-in. Combining it with
 `AddMembershipTenantClaimsTransformation()` throws, and a claims transformation of the host's own registered
 beside it is refused at start. Use it where several applications share one identity store:
 `active_tenant` holds one selection per account, so live resolution moves every open session when any of them
 switches.
- **`EventSubject.ForUser(userId)`** and **`EventSubject.NamesAnOwner`**: a stream can be created for a user alone,
 for data that belongs to a person rather than to any of their tenants. It is recorded under the reserved default
 tenant, keeps that owner for every later event whatever tenant the session names, and its encrypted fields — at
 every level — are keyed to the person: shredded by the person's erasure, untouched by any tenant's.
 `KeySubject.User` covers those keys too, so nothing is encrypted for the person again after the erasure.

- **`StrataraIdentityStore`, an identity store several hosts can share on PostgreSQL**, with its migrations shipped
 in `Stratara.EventSourcing.EntityFrameworkCore`. It holds ASP.NET Identity's tables, passkeys included, and the
 tenant directory in the fixed schema `stratara_identity`, with the history in
 `stratara_identity.__stratara_identity_migrations`. `AddStrataraIdentityStore()` registers it on the connection
 string `identitydb` (falling back to `defaultdb`, never through a tenant-routing `IDbResolver`) with the
 directory's stores over it, and refuses a host that turns on `Stores.ProtectPersonalData`;
 `MigrateStrataraIdentityStoreAsync()` creates the database where needed and applies the migrations — hosts that
 migrate at once take turns. The account type is `IdentityUser` and cannot be extended, and the store fixes the
 ASP.NET Identity schema version and key lengths, so every host's model matches the shipped migrations. Within a
 major version the schema changes only additively. Moving an existing identity store onto it means replacing it and
 seeding with the same user and tenant ids; the new guide *Shared Identity Store* describes it.

### Changed

- **Setting a membership to a status other than `Active` clears a selection that pointed at it**, as removing it
 already did.
- **An explicit subject that names a user and no tenant is accepted** by `AppendOnBehalfOfAsync` and
 `CreateOnBehalfOfAsync`; one that names neither is refused as before. A session whose tenant resolved to the
 reserved default still gives an event no owner.
- **BREAKING (behaviour): an event or aggregate type marked `[EncryptData]` as a whole stops the host from starting.**
 `EncryptionMetadataDriftGuard` refuses every registered aggregate, and every event type a registered aggregate
 applies, that carries the attribute on the type; an event type no aggregate applies is refused when it is appended,
 before anything is written. Once its subject was erased such a payload had nothing left to deliver, and a replay or
 rebuild stopped there for good. Mark the properties instead; payloads already written as a whole are still read.
 Commands and other types may still be marked as a whole.

### Fixed

- **A user's erasure shreds their own data through a key store that cannot list its scopes.** The eraser names the
 user's keys under the reserved default tenant itself, at every level; until now only a listing reached the
 user-level one.