Configure Tomcat Access Logs for MDC

New Information

Progress Application Server for OpenEdge : Troubleshoot problems : Enhanced Mapped Diagnostic Content Logging in PAS for OpenEdge : Configure Tomcat Access Logs for MDC

Client request context information is injected into the Tomcat Access log entry format using existing Extended Access Log valve functionality that provides access to HTTP Request object attributes.

To enable the Tomcat Access logs for MDC values:

1. Open the conf/catalina.properties file for the target instance.

2. Find the psc.as.accesslog.pattern property which looks similar to the following codeblock:

psc.as.accesslog.pattern=%h %u %t "%r" %s %b %D %I %S

3. Edit the property to reference MDC fields for User-ID or Request-ID, as seen in the following example:

psc.as.accesslog.pattern=%h %{OEReq.userId}r %t "%r" %s %b %D %I %S %{OEReq.requestId}r

Note: The properties are case sensitive.

PAS for OpenEdge supports the following MDC fields:

MDC field	Description
%{OEReq.requestId}r	Track client HTTP requests through the Tomcat, ABL Session Manager, and Multi-session agent.
%{OEReq.userId}r	Replaces the Tomcat logging token %r with the OpenEdge Spring authentication user-id
%{<http-header>}r	Any standard Tomcat HTTP request headers can be included into your access log. See Configure MDC access to HTTP Request Headers for more information.