elsa-core/src/modules/Elsa.Diagnostics.StructuredLogs.Persistence.Relational/README.md

# Elsa Diagnostics Structured Logs Relational Persistence

This package contains the reusable relational storage layer for diagnostics structured logs. It is provider-neutral: concrete packages supply the connection factory, SQL dialect, and FluentMigrator runner wiring.

To add a new relational provider such as SQL Server or PostgreSQL:

1. Reference this package from the provider package.
2. Implement `IRelationalStructuredLogConnectionFactory`.
3. Implement `IRelationalStructuredLogDialect` for identifier quoting, parameter prefixing, and result limiting.
4. Implement `IStructuredLogSchemaMigrator` using FluentMigrator with the provider-specific runner.
5. Register those services and call `AddRelationalStructuredLogPersistence`.

The core `Elsa.Diagnostics.StructuredLogs` package must remain unaware of provider packages. Provider-specific SQL and migration runner dependencies belong in provider packages.

`StructuredLogWriteBuffer` reports dropped durable writes through the core `IStructuredLogStorageDiagnostics` contract. The core endpoint `GET /diagnostics/structured-logs/storage` returns that provider-neutral count for Studio and other diagnostics clients.
[codex] Add structured log SQLite persistence (#7445) * Add structured log persistence spec * Clarify structured log persistence spec * Plan structured log persistence implementation * Regenerate structured log persistence tasks * Address structured log persistence analysis findings * Add structured log SQLite persistence * Address structured log persistence review * Harden structured log write buffer shutdown * Start structured log SQLite migrations before buffer 2026-05-13 13:57:06 +00:00			`# Elsa Diagnostics Structured Logs Relational Persistence`

			`This package contains the reusable relational storage layer for diagnostics structured logs. It is provider-neutral: concrete packages supply the connection factory, SQL dialect, and FluentMigrator runner wiring.`

			`To add a new relational provider such as SQL Server or PostgreSQL:`

			`1. Reference this package from the provider package.`
			2. Implement `IRelationalStructuredLogConnectionFactory`.
			3. Implement `IRelationalStructuredLogDialect` for identifier quoting, parameter prefixing, and result limiting.
			4. Implement `IStructuredLogSchemaMigrator` using FluentMigrator with the provider-specific runner.
			5. Register those services and call `AddRelationalStructuredLogPersistence`.

			The core `Elsa.Diagnostics.StructuredLogs` package must remain unaware of provider packages. Provider-specific SQL and migration runner dependencies belong in provider packages.
[codex] Expose structured log storage diagnostics (#7446) * Expose structured log storage diagnostics * Address structured log diagnostics review * Fix checked storage diagnostics aggregation 2026-05-13 14:32:23 +00:00
			`StructuredLogWriteBuffer` reports dropped durable writes through the core `IStructuredLogStorageDiagnostics` contract. The core endpoint `GET /diagnostics/structured-logs/storage` returns that provider-neutral count for Studio and other diagnostics clients.