Log information for mid tier response time
The following information is generated with active link logging when you select the Yes option for the Timings (Web) logging type:
- Time that a request was sent from the browser to the mid-tier server.
- Time that the mid-tier server received a request.
- Time that an API request was sent from the mid-tier server.
- Time that the mid-tier server received an API response.
- Time that a response was sent from the mid-tier server to the browser.
- Time that the browser received a response.
The timestamp displayed is based on the local system's clock.
The log file uses the following tag to display the mid-tier response time:
- HTTP – Logs time of request or response between client (browser) and mid-tier server.
If you also enable AR System server logging option in the Mid Tier Configuration Tool, you can compare the Timings (Web) log with the server side log. The server log uses the following tags to display mid-tier response times:
- MTT – Logs time of request or response received or sent by mid-tier server.
- CLAT – Logs time of request or response between mid-tier server and AR System server.
For information about configuring the Mid Tier, see Configuring the mid tier.
The following example shows a table refresh performed by a change field action.
ActiveLink: Refresh Table
True actions:
action 0
ARACTTableRefresh(536870917)
<HTTP> /* Tuesday, August 19, 2008 10:47:46 AM.791 */+HTTP call
<MTT > /* Tue Aug 19 2008 10:47:46.806 */+MidTier GetTableEntryList
<CLAT> /* Tue Aug 19 2008 10:47:46.806 */+API call, Procedure #73
ARGetListEntryWithFields -- schema a from Mid-tier (protocol 14)
at IP address 172.23.54.86
<CLAT> /* Tue Aug 19 2008 10:47:46.806 */-API call, Procedure #73
<MTT > /* Tue Aug 19 2008 10:47:46.806 */-MidTier
<HTTP> /* Tuesday, August 19, 2008 10:47:46 AM.822 */-HTTP call
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*