Stratara.Diagnostics 3.1.1

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package Stratara.Diagnostics --version 3.1.1
                    


                    

                
NuGet\Install-Package Stratara.Diagnostics -Version 3.1.1
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="3.1.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Stratara.Diagnostics" Version="3.1.1" />
                    


                            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 3.1.1
                    


                    

                
#r "nuget: Stratara.Diagnostics, 3.1.1"
#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@3.1.1
#: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=3.1.1
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Stratara.Diagnostics&version=3.1.1
                    


                            Install as a Cake Tool

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.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 (4)

Showing the top 4 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 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.

Version Downloads Last Updated
3.1.1 0 6/1/2026
3.1.0 62 5/30/2026
3.0.23 89 5/28/2026

### Fixed

- **`FileMasterKeyProvider` now rejects a master KEK that is not exactly 32 bytes at startup.**
 The KEK is used directly as an AES-256-GCM key, which accepts only 16/24/32-byte keys. The
 provider previously required merely *at least* 32 bytes, so a longer KEK (for example the
 48-byte output of `openssl rand -base64 48`, a common HKDF master-key recipe) passed both
 construction and the eager `FileKeyStoreStartupProbe`, then threw
 `CryptographicException: Specified key is not a valid size for this algorithm` on the **first**
 key creation at runtime — defeating the purpose of the boot-time probe. The provider now
 validates the decoded length is exactly 32 bytes and fails fast at boot with an actionable
 message (`Generate one with: openssl rand -base64 32`). A 32-byte KEK is unaffected.
- **`EnvelopeFileKeyStore` is now safe for multiple processes sharing one store file** (for
 example several containers bind-mounting the same host directory). Previously a process only
 read the store once at construction, so a data-encryption key created by another process after
 startup was invisible (`GetDataEncryptionKeyAsync` returned `null`, breaking decryption), and
 two processes creating keys concurrently could overwrite each other's keys or mint colliding
 versions for the same scope. Reads now reload from disk on a cache miss (guarded by the file's
 last-write time to avoid reload storms), and every mutation serializes through an exclusive
 cross-process lock file and re-reads the latest on-disk state before writing. A networked file
 system (NFS/SMB) remains unsupported — it guarantees neither atomic rename nor reliable advisory
 locks.

### Added

- **`LogEvents.KeyManagement.KeyStoreReloaded` (112_006)** — debug-level event emitted when the
 file key store reloads its state from disk to pick up keys written by another process.