Developer Packages
Start with CerbiStream, then add integrations, analyzers, runtime enforcement, or signature packs based on how your team adopts telemetry governance.
Cerbi works with existing logging frameworks and helps teams govern telemetry before ingestion. Use CerbiStream as a native logger, or add Cerbi governance to your existing framework.
Start here
- –New to Cerbi→
- –Using Serilog, MEL, or ASP.NET Core→
- –Want enforcement in CI→
- –Want runtime governance inside the app→
- –Want faster adoption→
Start Here
Recommended first installFramework Integrations
Add Cerbi governance to the frameworks teams already use.
Cerbi.AspNetCore.Governance
Add Cerbi governance to ASP.NET Core applications.
Cerbi.Serilog.Governance
Apply Cerbi governance policies to Serilog pipelines.
Build-Time Enforcement
Catch governance issues during development and CI before telemetry is emitted.
CerbiStream.GovernanceAnalyzer
Build-time governance validation for CerbiStream-based logging.
Runtime Governance
Govern telemetry inside the application process before it leaves the service.
Signature Packs
Accelerates adoptionPrebuilt signature packs help teams standardize logging faster without inventing every event shape from scratch.
Cerbi.Signatures.Security
Prebuilt security logging signatures for authentication, authorization, access violations, and sensitive actions.
Cerbi.Signatures.Api
Standard API logging signatures for requests, responses, failures, dependencies, and endpoint activity.
How to choose
- 1.Start with CerbiStream if you are adopting Cerbi directly.
- 2.Add framework integrations if you already use Serilog, MEL, or ASP.NET Core.
- 3.Add analyzers to shift governance left into development and CI.
- 4.Add runtime governance when you want in-process enforcement and tagging.
- 5.Use Signature Packs to accelerate adoption with prebuilt event shapes.
Ready to get started?
Install CerbiStream from NuGet and configure your first governance profile in minutes.