Is Logging Governance Actually Needed?

Из ленты dev.to devops — кратко, чтобы не потерять.

Most teams do not think about logging governance until something bad happens. A customer ID gets logged in the wrong place. A token shows up in a debug message. A developer adds email, ssn, or authorizationHeader because they are trying to troubleshoot a production issue at 2 AM. Six months later, nobody knows which apps log what, which teams follow standards, or whether the logs are safe to send into Splunk, Datadog, Application Insights, OpenSearch, or whatever else the company uses. That is the problem Cerbi is trying to solve. Cerbi is not another logging vendor. It does not try to replace Serilog, NLog, Log4j, Logback, Pino, Winston, Zap, Application Insights, Splunk, or Datadog. The goal is simpler: Stop bad logs at the source before they become risk, cost, or garbage data. The Probl

Полный текст и контекст у первоисточника: https://dev.to/hellocerbi/is-logging-governance-actually-needed-4d3m