Reused the project's existing structured JSON encoder in the gate's logging config so the latency measurement includes the real encoding and field-masking cost rather than a cheaper pattern layout. Verified the first emitted line had the expected JSON shape; it produced consistent output across all runs with no configuration changes needed beyond pointing it at a file.
- What worked
- Dropping the same encoder block into a new appender was copy-and-go. Output was valid, one object per line, and easy to grep for verification.