Self-Promotion
Show off what you're working on
Start new thread
Thomas Nelson

Launching soon: CerbiSuite — unified logging governance for .NET (early feedback welcome)

by•

I’m gearing up to launch CerbiSuite, a governance-first approach to .NET logging that aims to stop sensitive data before it hits your SIEM and to keep logs consistent across teams.

What it is

  • CerbiStream (OSS, MIT): structured logging for .NET with file fallback, routing, and consistent JSON output.

  • Governance profiles (JSON): define required/forbidden fields (e.g., PII/PHI), tags, severities.

  • Build-time + runtime enforcement: Roslyn analyzer + runtime validation to catch violations early and tag/redact at runtime.

  • Plays nice with your stack: route to queues/OTel/SIEMs; not tied to a specific vendor.

Who it’s for

Platform/DevOps/SRE and .NET teams that have compliance requirements (HIPAA/GDPR, etc.), messy log shape drift, or spend creep from noisy/unstructured logs.

What I’m asking from this community

  • DX feedback: are the docs, samples, and analyzer messages clear enough to adopt in a real codebase?

  • “Would you pilot this?” bar: what would you need (examples, integrations, dashboards) to try it?

  • Red flags: anything that screams “won’t fly in enterprise because X”?

Links (optional deep dives)

I’ll post the Product Hunt launch link here the morning we go live. If you’re open to trying a pre-release build or want me to tailor a sample to your setup, ping me here or email hello@cerbi.io.

Seed questions to make replies easy:

  • Would build-time + runtime governance have prevented any “we logged sensitive stuff” incidents you’ve seen?

  • Is a JSON profile the right place to centralize logging rules, or would you expect this in CI/policy engines instead?

  • What integrations would be must-have on day one (Serilog/OTel sinks, SIEMs, CI gates, etc.)?

Thanks for the eyes—blunt feedback beats polite silence.

13 views

Add a comment

Replies

Be the first to comment