Building governed logging + scoring (Cerbi): looking for feedback before Jan release
I’m building CerbiSuite: governed logging for teams that need structured logs without accidental PII/PHI leaks or schema chaos.
This week I shipped the first end-to-end scoring pipeline: CerbiStream + logger plugins emit a lightweight scoring event (violations, required field misses, redaction hits — no raw log bodies), and a new Scoring API ingests it and writes to Postgres with idempotent semantics. The goal is to make governance measurable over time (drift, coverage, risk), not “a doc people forget.”
In parallel I’ve been doing a ton of voice-of-customer work—cost sprawl, inconsistent fields across services, compliance reviews where nobody can prove what’s logged, and dashboards that break whenever one team “just adds a property.”
Targeting a January release, aligned with Microsoft as we finalize Marketplace/ISV readiness.
Feedback I’d love:
What’s the biggest failure mode you’ve seen with logging governance (cost, compliance, developer adoption, etc.)?
If you’ve tried “rules for logging” before, why didn’t it stick?
What would you expect a scoring dashboard to prove over 30/60/90 days?
Replies