Stratara.Diagnostics 4.4.4

Prefix Reserved
dotnet add package Stratara.Diagnostics --version 4.4.4
                    
NuGet\Install-Package Stratara.Diagnostics -Version 4.4.4
                    
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.Diagnostics" Version="4.4.4" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Diagnostics" Version="4.4.4" />
                    
Directory.Packages.props
<PackageReference Include="Stratara.Diagnostics" />
                    
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.Diagnostics --version 4.4.4
                    
#r "nuget: Stratara.Diagnostics, 4.4.4"
                    
#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.Diagnostics@4.4.4
                    
#: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.Diagnostics&version=4.4.4
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Diagnostics&version=4.4.4
                    
Install as a Cake Tool

Stratara.Diagnostics

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

License: MIT.

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, event.type, request.type, outcome, outbox.kind) + the metric instruments below. These names are part of the public observability contract — renaming them breaks downstream Grafana/Tempo queries.

Metric instruments (ApplicationDiagnostics.Metrics)

Instrument Type Tags
event_source.append.conflicts counter aggregate.type
event_source.events.appended counter event.type, aggregate.type
outbox.published counter outbox.kind (command / event)
command.duration (ms) histogram request.type, outcome
projection.events.processed counter event.type, outcome
projection.bundle.duration (ms) histogram outcome
saga.events.processed counter event.type, outcome
saga.bundle.duration (ms) histogram outcome
saga.inflight up/down counter —

Projections and sagas are real-time bus subscribers without a persisted checkpoint, so these report throughput and latency, not consumer lag.

  • LogEvents — [LoggerMessage] event-ID ranges per domain (ChangeSet=100_000s, BackgroundTasks=101_000s, EventStore=102_000s, …, Saga=110_000s, EventBundleIntegrity=111_000s, KeyManagement=112_000s, BusEnvelopeIntegrity=113_000s, TenantIsolation=114_000s, ExternalLoginProvisioning=115_000s, ApiKeys=116_000s). Even hundreds = info/debug, _1xx = error. Consumer applications start at 200_000.
  • 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.TenantIdTagName, tenantId);

ApplicationDiagnostics.Metrics.EventSourceAppendConflicts.Add(1,
    new("aggregate.type", "Order"));

Dependencies

  • Microsoft.Extensions.Logging.Abstractions
  • OpenTelemetry.Api
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 (6)

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.Shared

Umbrella package for the Stratara framework — source-generated logger extensions for command flows, domain-event helpers, merge primitives, and the Tier-A/B abstractions surface re-exported as one transitive bundle.

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.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.

Version Downloads Last Updated
4.4.4 242 10/10/2026
4.4.3 137 10/10/2026
4.4.2 573 10/2/2026
4.4.1 592 9/29/2026
4.4.0 325 9/27/2026
4.3.1 387 9/25/2026
4.3.0 571 9/23/2026
4.2.0 341 9/18/2026
4.1.1 338 9/16/2026
4.1.0 274 9/16/2026
4.0.4 1,139 9/14/2026
4.0.3 380 9/3/2026
4.0.2 794 9/3/2026
4.0.1 483 9/2/2026
4.0.0 845 8/31/2026
4.0.0-preview.1 145 8/31/2026
3.4.0 355 8/28/2026
3.3.0 511 8/25/2026
3.2.3 337 8/22/2026
3.2.2 921 8/14/2026
Loading failed

A one-fix release. On the Redis-backed replay state, a host could report a replay still active after it had ended
it, holding publication back for up to one refresh interval. Nothing else changes; no configuration or migration is
needed.

### Fixed

- **A host no longer reports a replay active after it ended the replay itself.** On the Redis-backed replay state, a
 refresh that had read the marking just before the host's own deactivation could compare its generation before the
 deactivation and write the field after it, leaving `IsReplayActive` true — and publication held back — until the
 next refresh (`ProjectionReplay:RefreshSeconds`, default 5). The comparison and the write are now one step with the
 transition. Present since 4.4.2.