Stratara.Diagnostics
3.1.3
dotnet add package Stratara.Diagnostics --version 3.1.3
NuGet\Install-Package Stratara.Diagnostics -Version 3.1.3
<PackageReference Include="Stratara.Diagnostics" Version="3.1.3" />
<PackageVersion Include="Stratara.Diagnostics" Version="3.1.3" />
<PackageReference Include="Stratara.Diagnostics" />
paket add Stratara.Diagnostics --version 3.1.3
#r "nuget: Stratara.Diagnostics, 3.1.3"
#:package Stratara.Diagnostics@3.1.3
#addin nuget:?package=Stratara.Diagnostics&version=3.1.3
#tool nuget:?package=Stratara.Diagnostics&version=3.1.3
Stratara.Diagnostics
License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.
Generic observability primitives shared by all Stratara packages. Use this to emit Activity / Meter instruments under a uniform source name and stable event-ID schema.
Contents
ApplicationDiagnostics—ActivitySource("Stratara.Application")+Meter("Stratara.Service")+ tag-name constants (correlation.id,causation.id,tenant.id,user.id) + metric names (event_source.append.conflicts). These names are part of the public observability contract — renaming them breaks downstream Grafana/Tempo queries.LogEvents—[LoggerMessage]event-ID ranges per domain (ChangeSet=100_000s, BackgroundTasks=101_000s, EventStore=102_000s, …, Messaging=108_000s, Update=109_000s, Saga=110_000s). Even hundreds = info/debug,_1xx= error.LoggerScopeExtensions.BeginCreateAggregateScope/BeginUpdateAggregateScope— pre-baked logging scopes for the create/update aggregate flows.
Quick reference
using var activity = ApplicationDiagnostics.Activity.Source
.StartActivity("CreateOrder");
activity?.SetTag(ApplicationDiagnostics.TagNames.TenantId, tenantId);
ApplicationDiagnostics.Metrics.EventSourceAppendConflicts.Add(1,
new("aggregate.type", "Order"));
Dependencies
Microsoft.Extensions.Logging.AbstractionsOpenTelemetry.Api
| 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
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.8)
- OpenTelemetry.Api (>= 1.15.3)
NuGet packages (5)
Showing the top 5 NuGet packages that depend on Stratara.Diagnostics:
| Package | Downloads |
|---|---|
|
Stratara.Sessions
ASP.NET Core middleware and provider for Stratara's Actor/Subject session model. Reads tenant and user from JWT claims (or X-Tenant-Id / X-Client-Id headers) and populates the ambient ISessionContextProvider for every request. |
|
|
Stratara.Mediator
In-process mediator with DI-resolved handlers and pipeline behaviors for the Stratara framework. MediatR-style routing via typed wrapper cache, plus an authorizing decorator and a bucket-lock concurrency primitive. |
|
|
Stratara.Shared
Umbrella package for the Stratara framework — source-generated logger extensions for outbox / saga / projection / messaging, domain-event helpers, merge primitives, and the Tier-A/B abstractions surface re-exported as one transitive bundle. |
|
|
Stratara.Security
Dependency-light key-store and envelope encryption for the Stratara framework. Production IKeyStore implementation (EnvelopeFileKeyStore) with KEK-wrapped, versioned per-scope DEKs (rotation + revoke + crypto-shred), a file-backed master-key provider, and an AES-GCM blob encryptor with purpose-bound associated data. References only Stratara.Abstractions + BCL crypto — no EF Core, RabbitMQ, Redis, or cloud SDKs. |
|
|
Stratara.Validation
Vendor-neutral request validation for the Stratara framework — a mediator pipeline behavior that runs IValidator<T> implementations before the handler and throws an aggregated StrataraValidationException on failure. No FluentValidation dependency; an optional adapter is shipped separately. |
GitHub repositories
This package is not used by any popular GitHub repositories.
### Added
- **Mediator tenant-isolation behavior** (`Stratara.Mediator`) — `AddStrataraTenantIsolation()`
registers a pipeline behavior that enforces tenant isolation at the mediator entrance, before the
handler runs, for any request that opts in via the new `ITenantScopedRequest` marker
(`Stratara.Abstractions.Multitenancy`). The behavior compares the request's `TenantId` (data owner)
against the ambient session's data-owner tenant and rejects a mismatch with the new
`TenantAccessDeniedException` (translated to HTTP 403 on ASP.NET hosts). `TenantIsolationMode.Default`
enforces only the subject match (privileged cross-tenant operations pass when the endpoint promoted
the session subject to the target); `TenantIsolationMode.Strict` additionally routes every
cross-tenant operation through the new `ICrossTenantAuthorizer`, whose shipped default denies all
cross-tenant access until a consumer registers its own authorizer. Complements the existing
database-side `ApplyGlobalTenantQueryFilters` with a command-/query-entrance guard. New log-event
IDs `114_101`/`114_102`/`114_003` in `Stratara.Diagnostics`.
- **`Stratara.Abstractions.Persistence.ConcurrencyConflictException`** — provider-agnostic
wrapper for an optimistic-concurrency conflict detected during commit. Allows framework-level
code in `Stratara.Projections` (and any consumer outside the `EntityFrameworkCore` package) to
react to concurrency without taking an EF Core dependency. EF Core's `DbUpdateConcurrencyException`
(and provider equivalents) flow through this type.
### Changed
- **`EfTransaction.SaveChangesAsync`** (in `Stratara.EventSourcing.EntityFrameworkCore`) now
wraps `DbUpdateConcurrencyException` thrown by EF Core in the new
`ConcurrencyConflictException`. PostgreSQL unique-violation paths remain on `DbUpdateException`
(different semantics — duplicate-key on insert vs. stale-row on update/delete).
- **`EventSource.SaveChangesAsync`** (write-side append flow) extends its concurrency-handling
catch to the new exception type so the existing append-conflict recovery path keeps working
after the wrap. Behaviour for both EF concurrency conflicts and PostgreSQL unique violations
is unchanged.
### Fixed
- **`TenantProjection` no longer aborts the event bundle on a parallel delete race.** The two
delete handlers (`TenantDeleted`, `CustomerTenantsDeleted`) now swallow
`ConcurrencyConflictException` silently — a missing row is the desired end-state of a delete.
Before this fix, a consumer-side customer-delete cascade saga that emits both
`CustomerTenantsDeleted` and a follow-up `TenantDeleted` for the same tenants would race the
two parallel projection bundles on the same `TenantView` row; the loser threw
`DbUpdateConcurrencyException` out of `SaveChangesAsync`, which propagated through
`ProjectionWorker` and caused `RabbitMqBus` to roll back the entire bundle — including
sibling projections that had already committed. Update handlers (rename / activate /
deactivate / locale / customer-assigned) keep their current behaviour: a concurrency failure
there is a real race that propagates.