Skip to main content

Cascade Administration how to

How can I enable request logging for Cascade CMS?

Request logging is configured on the application server, not in the CMS interface:

  1. Stop Cascade CMS.
  2. Edit tomcat/conf/context.xml.

  3. Within the active <Context> element, just before the closing </Context> tag, add:

    XML 
    <Valve className="org.apache.catalina.valves.AccessLogValve"
     directory="logs" prefix="cascadecms_request." suffix=".log"
     pattern="%t %U %a %m %H %b %h %s" resolveHosts="false" />
  4. Start Cascade CMS.

With the configuration above, the request log is created in tomcat/logs as cascadecms_request.log. Its contents look similar to this:

Bash 
[13/Dec/2022:13:51:35 -0500] /ajax/navigationtree.act 127.0.0.1 GET HTTP/1.1 731 127.0.0.1 200
[13/Dec/2022:13:51:36 -0500] /render/page.act 127.0.0.1 GET HTTP/1.1 4285 127.0.0.1 200
[13/Dec/2022:13:51:36 -0500] /renderfile/355799867f0000010020a239cfb967ab/files/css/hh-standard.css 127.0.0.1 GET HTTP/1.1 485 127.0.0.1 200

Matching requests to users

The request log cannot output the Cascade CMS username. To connect a remote IP address to a user, use Audits filtered by type "Login" to see the IPs users logged in from.

Additional parameters and options are documented in the Apache Tomcat Access Log Valve reference.