Log the Shape, Not the Payload

Описание и применение

<p>The leak you end up paying for is rarely the request body; it is the log line the request left behind. Outbound traffic gets a threat model, a reviewer, and a deny list, while the logger gets a one-liner and a retention setting nobody remembers choosing. The workflow below keeps the debugging power and removes the second copy: every model call writes a <em>shape record</em> instead of content, and CI refuses any log file that disagrees. If you change one thing about your AI feature this quarter, change what your logs are allowed to contain.</p> <h2> A shape record answers the questions you

Задача

<p>The leak you end up paying for is rarely the request body; it is the log line the request left behind. Outbound traffic gets a threat model, a reviewer, and a deny list, while the logger gets a one-liner and a retention setting nobody remembers choosing. The workflow below keeps the debugging power and removes the second copy: every model call writes a <em>shape record</em> instead of content, and CI refuses any log file that disagrees. If you change one thing about your AI feature this quarter, change what your logs are allowed to contain.</p> <h2> A shape record answers the questions you

Результат

<p>The leak you end up paying for is rarely the request body; it is the log line the request left behind. Outbound traffic gets a threat model, a reviewer, and a deny list, while the logger gets a one-liner and a retention setting nobody remembers choosing. The workflow below keeps the debugging power and removes the second copy: every model call writes a <em>shape record</em> instead of content, and CI refuses any log file that disagrees. If you change one thing about your AI feature this quarter, change what your logs are allowed to contain.</p> <h2> A shape record answers the questions you

Доказательства

Log the Shape, Not the Payload

Источник