Runtime coverage

Choose the integration.
Verify its behavior.

Cerbi is .NET-first, with Java, Node.js, and Go integrations. Sharing a governance model does not imply identical enforcement support in every adapter.

Implementation documentation for the integration you choose.
RuntimeIntegrationScope
.NETCerbiStream, MEL, Serilog, NLogApplication/runtime governance and compiler or IDE analysis through the applicable package.
JavaLogback, Log4j2Structured logging and MDC governance through the relevant filter or adapter. SLF4J usage depends on the logging backend.
Node.jsPino, WinstonGovernance-aware transport/evaluator paths. Check the adapter’s enforcement and transformation semantics.
GoZap, ZerologSource implementations exist; released versions and public installation endpoints are unverified in this guide. Verify each adapter's supported actions.

Supported Loggers

Governance for your stack. Supported loggers.

Each adapter has its own configuration and transport contract. The .NET policy examples, Logback rulesets, and Log4j2 rewrite rules are not interchangeable. Verify the selected version before connecting score delivery.

Install
dotnet add package Cerbi.Serilog.GovernanceAnalyzer --version 1.5.0
dotnet add package Serilog.Sinks.Console --version 6.0.0

Wire-up (Program.cs)

Program.cs
using Serilog;
using Cerbi.Serilog.Governance;

Log.Logger = new LoggerConfiguration()
    .CerbiGovernance(options =>
    {
        options.Profile = "Orders";
        options.ConfigPath = "cerbi_governance.json";
        options.TagOnlyMode = true; // observe before enabling filtering
    })
    .WriteTo.Console()
    .CreateLogger();
Use the Orders policy in the Serilog Governance Setup docs and copy it to the output directory. Version 1.5.0 is a runtime integration despite its package name. A missing policy passes events through. Optional ScoreShipping settings use HTTP and require a compatible endpoint and license configuration; do not supply a Service Bus connection string as an HTTP endpoint. End-to-end delivery is not established by this local setup.

Logger support matrix

Policy schemas and score transports vary by adapter. Logback 0.1.0 uses profile/mode/rules; Serilog uses the selected .NET profile. A source implementation or published artifact does not prove end-to-end delivery to your CerbiShield deployment.

Cerbi.cerbi-scanner
Verify task/version
CerbiStreamC# / .NET
CerbiStream
Verify SDK/version
SerilogC# / .NET
Cerbi.Serilog.GovernanceAnalyzer
Optional HTTP; configure and test
NLogC# / .NET
Cerbi.NLog.GovernanceAnalyzer
Verify adapter/version
MELC# / .NET
Cerbi.MEL.Governance
Verify adapter/version
LogbackJava
io.github.zeroshi:cerbi-logback-governance
Optional HTTP; configure and test

Ready to connect a logger?

Start with CerbiStream for new .NET projects, or drop in one of the framework integrations if you already have Serilog, NLog, or MEL in place.

NEXTChoose your next proof

Review a Scanner finding or logging requirement against your existing controls. If a recurring gap remains, scope one CerbiShield workload, policy, evaluation window, and evidence review.

One initial workload/Customer-hosted in Azure/Existing destinations remain
Integrations | Cerbi | Cerbi