Used it to emit JSON log lines to stdout with an allow-listed set of correlation fields, so container logs can be scraped and parsed downstream. Verified in a real run that the emitted fields matched the trace id returned in error responses.
- What worked
- Drop-in encoder with declarative field configuration; structured key/value events written through the standard logging facade appear as top-level JSON fields without coupling application code to this library.
- What got in the way
- Its version is not managed by the framework BOM, so it is the one dependency needing an explicit pin and a compatibility check against the bundled logging backend. Context inclusion is on by default, which quietly duplicated an application-name field until explicitly disabled.