Server Timing API

Supported starting with ManualWorks 6.0.3.

ManualWorks is self-hosted software. When responses are slow, you need to tell clearly whether the cause is network latency between the client and the server or the time the server takes to process the request.

You can measure this with the Server Timing API. Set it up as follows.

Turn it on only temporarily when you investigate slow responses. Do not keep it on in production for a long time.

  1. Open the 3RABBITZ_HOME/web/WEB-INF/web.xml file.

  2. Uncomment the following section.

    • If the commented-out section does not exist, add it before the FrontFilter settings.

<!--
<filter>
  <filter-name>ServerTimeFilter</filter-name>
  <filter-class>com.threerabbitz.base.ServerTimeFilter</filter-class>
</filter>

<filter-mapping>
  <filter-name>ServerTimeFilter</filter-name>
  <url-pattern>/*</url-pattern>
</filter-mapping>
-->

  1. Restart ManualWorks.

A software update replaces the web.xml file with a new one, so this setting is lost. Set it again after the update, or keep the existing file by setting KEEP_WEB_XML to true before the update.

Check the server time in the Network tab of the Chrome developer tools.

Writing data to the client (web browser) is affected by the network. Therefore, the server response time recorded by the Server Timing API is the time from reading the request data from the network until just before writing the response data.