CerbiStream / In-process governance
Govern logs before
they leave the process.
CerbiStream is Cerbi's in-process logging library for .NET. It applies governance at emission time, then sends the governed event into the logging and observability path you already use. It is one enforcement mechanism in the same lifecycle: Scanner discovers risk; CerbiShield manages policy, rollout, and evidence when your teams need ongoing centralized operation.
A policy decision, up close
Keep the context.
Change the exposure.
Inspect the same fictional event before policy, with masking, and with an intentional developer override using Relax.
Illustrative policy example · synthetic fields.
Not a product screen or live evaluation.
- application
- checkout-example
- operation
- order.created
- customer.email
- [MASKED]
- trace_id
- example-trace-001
OutcomeRedacted
The configured masking rule protects the email field. Application, operation, and trace context remain useful for debugging.
Available now · CerbiStream 2.0.126
Faster governance without changing how your team logs.
The latest .NET release does the same representative governance work in about one quarter of the measured time while creating far less temporary memory pressure. Existing destinations and caller metadata stay in place.
About 4.2×
faster in the controlled full-governance SDK benchmark
About 79%
less temporary managed allocation per measured event
No rewrite
for your observability destination or metadata model
Measured with the same ten-field event, Release build, and no-op destination before and after optimization. This isolates SDK work; it is not an application-capacity or network-throughput guarantee.
CerbiStream + runtime SDKs
CerbiStream is one product. The other loggers keep their own integrations.
Use CerbiStream when you want Cerbi's .NET logging library. If an application already uses another logger, use the dedicated Cerbi governance SDK or adapter for that logger instead. They share the governance model, but they are not renamed CerbiStream.
Cerbi's .NET logging library
CerbiStream and add it to the .NET logging pipeline. This is the CerbiStream product itself.Dedicated Cerbi governance integrations for the logging frameworks you already use.
Microsoft.Extensions.Logging · Serilog · NLog
Dedicated Cerbi governance integrations for the logging frameworks you already use.
Log4j2 · Logback
Dedicated Cerbi governance integrations for the logging frameworks you already use.
Winston · Pino
Dedicated Cerbi governance integrations for the logging frameworks you already use.
Zap · Zerolog · slog
Dedicated Cerbi governance integrations for the logging frameworks you already use.
Python logging · structlog
Architecture
In-process governance is the common boundary.
CerbiStream and the dedicated logger SDKs enforce policy inside the application. The exact integration changes by logger and runtime; the goal does not: govern the event before the first telemetry network hop.
CerbiStream setup
Add CerbiStream when CerbiStream is the logger path you want.
This setup is specific to CerbiStream. Existing Serilog, NLog, MEL, Java, Node.js, Go, and Python applications use their corresponding Cerbi integration instead.
dotnet add package CerbiStream
builder.Logging.AddCerbiStream();For an existing logger or another runtime, use the matching Cerbi SDK from the integrations catalog.
Policy
Keep the rules explicit and versioned.
Governance profiles define required fields, disallowed fields, severities, and enforcement behavior in a file that can live with the application and move through normal source-control review.
{
"Version": "1.0.0",
"LoggingProfiles": {
"production": {
"RequiredFields": [
"timestamp",
"message",
"correlationId"
],
"DisallowedFields": [
"ssn",
"creditCard",
"password"
],
"FieldSeverities": {
"password": "Forbidden"
}
}
}
}CerbiStream build-time check
Catch CerbiStream policy drift before runtime.
CerbiStream.GovernanceAnalyzer can surface governance diagnostics during the normal .NET build so CI can catch missing or disallowed fields before deployment.
$ dotnet build
CerbiStream.GovernanceAnalyzer findings:
[CS-GOV-001] Missing required field: correlationId
[CS-GOV-002] Disallowed field detected: password
Diagnostics follow the active governance profile.
Use an in-process Cerbi integration whenYou control the application and want policy before the first telemetry network hop.
- Use CerbiStream or the dedicated SDK for the logger and runtime already in the application.
- Policy should execute before telemetry leaves the process.
- You want to keep the downstream observability destinations already in place.
Use Gateway whenThe estate already emits OTLP and application-by-application integration is the wrong boundary.
- Workloads already emit OpenTelemetry.
- You want a customer-hosted central boundary.
- Lower-friction estate adoption matters more than in-process proximity.
Start
Choose the in-process path that fits the service.
Install CerbiStream for the Cerbi logging path, or keep the logger already in the application and add its dedicated Cerbi governance integration.
Package access
Go straight to the package you use.
CerbiStream is the Cerbi logger. Existing logger families use their own Cerbi integration. These links point directly to the public registry pages already used across the Cerbi site.
Full package catalog.NET
NuGetCerbi's .NET logging product.
dotnet add package CerbiStreamNuGetGovernance integration for Microsoft.Extensions.Logging.
dotnet add package Cerbi.MEL.GovernanceNuGetRuntime governance integration for Serilog.
dotnet add package Cerbi.Serilog.GovernanceAnalyzer --version 1.5.0NuGetCerbi governance support for NLog projects.
dotnet add package Cerbi.NLog.GovernanceAnalyzerNuGetASP.NET Core governance integration.
dotnet add package Cerbi.AspNetCore.GovernanceNuGetJava
Maven CentralNode.js
npmPython
PyPI · pre-releaseScanner / CI
Go source implementations exist for Zap and Zerolog. Released versions and public installation endpoints are unverified in this guide; see Go Setup in the docs for source references.