Cerbi.Serilog.GovernanceAnalyzer 1.3.4

Cerbi.Serilog.Governance

Real-time governance enforcement for Serilog using Cerbi — the structured logging validator for .NET.

Requirements

• .NET 9.0 or higher (also compatible with .NET 8.0+)
• Serilog 4.x

Features

• Block non-compliant log events (required / forbidden fields, enum validation)
• Optional enrichment with governance metadata (profile, violations, relaxed flag)
• TagOnlyMode for non-blocking observability
• Works with any Serilog sinks + other enrichers/filters
• Relax() bypass tagging (still observable)
• High-throughput score shipping with batching, retry logic, and ArrayPool optimizations

Performance Characteristics

Throughput Modes

Standard Mode (Default)

• Validates + enriches: ~50K-100K events/sec
• Score shipping: 100-1K events/sec
• Suitable for: Most production workloads

High-Throughput Mode

• Validates + enriches: ~100K-200K events/sec
• Score shipping: 10K-50K events/sec
• Optimizations: ArrayPool, reduced allocations, aggressive batching
• Suitable for: High-volume APIs, streaming services

Optimization Techniques

The library uses several performance optimizations:

• Lock-free enqueuing via ConcurrentQueue
• ArrayPool<T> for batch collection (zero allocations)
• Batch serialization - serialize once, retry with same payload
• Background worker - non-blocking score shipping
• ConfigureAwait(false) throughout async paths
• AggressiveInlining on hot path methods

Install

dotnet add package Cerbi.Serilog.Governance

Requires runtime packages (pulled transitively): Cerbi.Governance.Core, Cerbi.Governance.Runtime.

Config File (cerbi_governance.json)

{
  "EnforcementMode": "Strict",
  "LoggingProfiles": {
    "Orders": {
      "RequireTopic": false,
      "AllowedTopics": ["Orders", "Users"],
      "FieldSeverities": {
        "userId": "Required",
        "email": "Required",
        "password": "Forbidden"
      },
      "FieldEnums": { "Status": ["Pending", "Approved", "Rejected"] },
      "AllowRelax": true
    }
  }
}

One-Line Setup

using Cerbi.Serilog.Governance;

Log.Logger = new LoggerConfiguration()
  .CerbiGovernance(o =>
  {
    o.Profile = "Orders";            // profile key
    o.ConfigPath = "cerbi_governance.json"; // path
    // o.TagOnlyMode = true;           // uncomment for no blocking
  })
  .WriteTo.Console()
  .CreateLogger();

High-Throughput Configuration

For applications handling 10K+ events/second, configure aggressive batching and tuning:

Log.Logger = new LoggerConfiguration()
  .CerbiGovernance(o =>
  {
    o.Profile = "Orders";
    o.TagOnlyMode = true; // Recommended: avoid blocking on hot path
    o.AppName = "HighThroughputAPI";
    o.Environment = "Production";
    
    // High-throughput score shipping settings
    o.ScoreShipping = new ScoreShippingOptions
    {
      Enabled = true,
      LicenseAllowsScoring = true,
      Endpoint = "https://governance.cerbi.io/v1/scores",
      ApiKey = "your-api-key",
      
      // Optimized for high throughput
      BatchSize = 250,                            // Larger batches = fewer HTTP calls
      FlushInterval = TimeSpan.FromSeconds(1),    // Lower latency
      MaxQueueSize = 50_000,                      // Handle traffic bursts
      MaxRetryAttempts = 2                        // Fail faster under load
    };
  })
  .WriteTo.Console()
  .CreateLogger();

Throughput Tuning Guide

Memory Impact: Each queued event ≈ 200-500 bytes. MaxQueueSize=100K ≈ 20-50 MB.

Filtering Only

.Filter.WithCerbiGovernanceFiltering(o => { o.Profile = "Orders"; })

Enrichment Only

.Enrich.WithCerbiGovernanceTagging(o => { o.Profile = "Orders"; })

Relaxed Logging

Log.ForContext("userId", "abc123")
   .Relax() // bypass enforcement, tagged GovernanceRelaxed=true
   .Information("Non-compliant log allowed in relax mode");

TagOnlyMode

Use when you want visibility but no blocking (e.g. staging or high-throughput production):

o.TagOnlyMode = true;

Performance Note: TagOnlyMode is recommended for high-throughput scenarios to avoid blocking on the validation path.

Benchmarks

Run benchmarks to measure performance on your hardware:

dotnet run -c Release -p BenchmarkSuite1/BenchmarkSuite1.csproj

Typical results (AMD Ryzen 9 / Intel i9):

• Enricher (valid event): 500-800 ns/op
• Filter (valid event): 400-600 ns/op
• Filter (blocked event): 600-900 ns/op

Monitoring & Diagnostics

Queue Metrics

Monitor queue depth for health:

var healthCheck = new CerbiGovernanceHealth(scoreShipper);
var queueDepth = healthCheck.GetQueueDepth(); // Monitor this metric

Dropped Events

Events are dropped silently when MaxQueueSize is exceeded. Enable diagnostics to track:

using Serilog.Debugging;
SelfLog.Enable(msg => Console.WriteLine($"[Cerbi] {msg}"));

CI Version Override

Set VERSION env (Directory.Build.props maps it):

dotnet pack ClassLibrary1/Cerbi-Serilog-Governance.csproj -c Release -p:Version=1.2.15

Roadmap

• Caller type / [CerbiTopic] support when runtime exposes evaluation API
• Structured violation detail enrichment toggle
• Adaptive batching based on queue depth

Contributing

Open issues / PRs. Keep changes minimal & benchmark if performance related.

License

MIT

See Also

• CerbiStream (integrated governance API)
• Cerbi.Governance.Runtime (core validator)