Why does logging quality usually fall apart as systems grow?
One pattern I keep seeing is that logging starts out useful, then gradually becomes inconsistent, noisy, expensive, and harder to trust. Field names drift, context goes missing, dashboards get polluted, and sometimes sensitive data ends up in places it never should have reached. The deeper problem seems to be that most teams try to fix logging after the data has already entered downstream...
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...
Founder of CerbiSuite — tackling logging chaos & governance for cloud teams
Hey everyone I’m Thomas, a principal architect-turned-founder working mostly in cloud-native backend systems (.NET, Azure, distributed apps, all the usual suspects). Over the last few years I kept running into the same mess at every company: Logs scattered across tools Observability bills creeping into “this can’t be right” territory Zero governance on what people log (PII everywhere, no...
Launching soon: CerbiSuite — unified logging governance for .NET (early feedback welcome)
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....