History Service - logging improvement

Current Situation

• The History Service observes and filters events emitted by the JS7 Proxy.
• Information about these events is currently not available in the logs.

Desired Behavior

• At TRACE level, all events, including those filtered out, should be logged to the JOC service-history-debug.log file.

Maintainer Notes

• Current behaviour:
  • The reactive Flux logs are currently split across two log files (the cause appears to be the different thread contexts):
    • joc-debug.log
    • service-history-debug.log
  • Flux log lines can be identified by the logger name.
    • Expected logger name: a fixed prefix plus the controller ID, e.g.: history-flux-<controllerId>
      • In joc-debug.log log file:

        ... TRACE JS7 Proxy-3 history-flux-myControllerId - onNext(EventAndState(Stamped(1756297448426000 ProxyStarted), ...

      • In service-history-debug.log log file:

        ... TRACE history-9-1 history-flux-myControllerId - request(256) Flux.log ...

    • Note:
      • In some environments/JVM versions, the logs may display h.x instead of the full logger name, even though the logger is correctly set.

        ... TRACE history-9-1 h.x - request(256) Flux.log ...

      • h.x is internal Flux shorthand for operators.

• Planned behaviour:
  • Always provide informative logger names as a fixed prefix plus controller ID, independent of environment or JVM version.
  • Ensure logs can consistently be directed to a single log file.

Test Instructions

• Configure JOC to use TRACE level
  • Edit resources/log4j2.xml and set RootLogLevel, JocLogLevel and ServiceHistoryLogLevel to TRACE.
• Configure and run a workflow
• Check both debug log files according to the Maintainer Notes / Current behaviour