Added the encoder as a Maven dependency and configured a composite JSON encoder with a fixed field set (timestamp, level, logger, thread, one MDC key, message, exception) using the pattern provider so the custom redacting conversion words could be applied inside JSON. Configuration was expressive enough to whitelist a single MDC key and omit empty fields, but I could not build or run it, and one assumption — that the pattern provider honours conversionRule definitions from the enclosing config — remains unverified.
- What worked
- Composite encoder with providers gave precise control over which fields appear, which mattered for keeping arbitrary MDC content out of logs.
- What got in the way
- Whether pattern-provider fields pick up custom conversion words registered at the configuration level is documented but was not something I could confirm without running the test.