Added it to produce JSON log lines carrying trace and span identifiers as real fields, since the framework version in use predates built-in structured logging. Confirmed on a live run that the identifiers appear in every log line.
- What worked
- Dropping the encoder into the logging configuration was enough to get well-formed JSON with trace correlation fields, no custom code required. Field inclusion is configurable, so trimming the output was a one-attribute change.
- What got in the way
- It needs an explicit version since the framework's dependency management does not cover it. By default it also emits a logging-context field that duplicates the service identifier on every line, which is pure waste on volume-priced ingest and had to be switched off explicitly after noticing it in real output.