FclEx.Logging 2.4.0

FclEx.Logging

Microsoft.Extensions.Logging helpers for FclEx.

What Is Included

• Logger factory and provider convenience helpers.
• In-memory collectors for log messages, metadata, and scopes.
• Scoped logging-property helpers.
• Operation timing helpers.
• Null logger fallbacks and cleanup utilities.
• Service registration helpers for logging-related options.

Usage Notes

• This package uses Microsoft logging abstractions.
• Serilog-specific helpers live in FclEx.Serilog.
• Use scoped properties when downstream providers need structured context for an operation.

Collecting Logs

For a standalone collector:

using FclEx.Logging;
using Microsoft.Extensions.Logging;

var logger = new CollectingLogger("example");
using (logger.PushProperty("RequestId", 42))
{
    logger.LogInformation("Processing {Count} items", 3);
}

var entry = logger.Entries[0];
// entry.Message: "Processing 3 items"
// entry.State: the original structured message state
// entry.Scopes: the active scopes, ordered from outermost to innermost
logger.Clear();

Register the collector through ILoggingBuilder when using dependency injection:

using Microsoft.Extensions.DependencyInjection;

var services = new ServiceCollection();
services.AddLogging(builder => builder
    .SetMinimumLevel(LogLevel.Trace)
    .AddCollecting());

using var serviceProvider = services.BuildServiceProvider();
var factory = serviceProvider.GetRequiredService<ILoggerFactory>();
var collector = serviceProvider.GetRequiredService<CollectingLoggerProvider>();
factory.CreateLogger("example").LogDebug("Collected message");

var entries = collector.Entries;
collector.Clear();

For an existing factory, factory.AddCollecting() returns the newly added collector. Repeated calls to the builder extension register one singleton collector; repeated calls to the factory extension add independent collectors. Factory filters apply in both cases.

Entries returns a synchronized snapshot. Later writes and Clear() do not alter earlier snapshots. A provider combines entries from every category, and its loggers share that store. Scope stack membership is captured when a message is logged, while state and scope values remain the original objects and are not deep copied. Standalone collectors maintain their own async scope context; provider-created loggers share the factory's scope context.

Collectors accept every defined level except LogLevel.None. They retain entries until explicitly cleared, including after provider disposal, so clear them between test phases or when the retained data is no longer needed.