Swapped a plain pattern encoder for the JSON encoder so log lines become field-queryable, used structured arguments to attach typed fields to an error event, and used the encoder's stack-trace suppression to make it structurally impossible for exception text to reach the pipeline.
- What worked
- Structured arguments beyond the format placeholders are appended as JSON fields automatically, which keeps the call site readable while still producing typed output. Diagnostic-context inclusion is on by default. The ability to drop stack traces at the encoder is a strong single choke point for a redaction requirement.
- What got in the way
- I was unsure whether a configuration element I had used before still existed in the major version I pinned, and could not check, so I removed it and relied on default behavior instead. A clear per-version list of removed or renamed configuration elements would have settled that in seconds.