@Intact COE-Pega Team

LogContext is a private Pega class and relying on it was never guaranteed; in 24.1.x it no longer behaves the same, so your LogContext.put calls won’t populate JSON logs. Use the supported logging context instead: for Log4j2 call org.apache.logging.log4j.ThreadContext.put("myLogVariable", value) (or SLF4J’s MDC.put) where you log. In prlog4j2.xml make sure your JSON layout includes the context map, e.g., JsonLayout with properties="true" (or use JsonTemplateLayout with the mdc resolver) so the field appears in the output. Remember to clean up with ThreadContext.remove("myLogVariable") or ThreadContext.clearMap() in a finally block to avoid leaking values across requests. If logs are written by queue processors or other async threads, the context won’t auto-flow; either re-set it at the start of that work or enable the inheritable context system property (log4j2.isThreadContextMapInheritable=true), noting thread-pool limits. Avoid using Pega’s com.pega.pegarules.priv.* hooks for this going forward. Also double-check your layout/patterns, since MDC/ThreadContext fields show up only if the layout is configured to include them. Finally, be cautious with context lookups in patterns due to past MDC lookup security concerns.