Troubleshooting workflows by activating workflow logging in a browser

To turn workflow logging on and off in a browser, in the Preference Server field on the General Settings page of Remedy Mid Tier Configuration Tool, you must specify a server. This server hosts the AR System User Preference records.

Two logging types are available:

• Active link
• Remedy Mid Tier response time

To activate workflow logging for a browser

1. Search for the user's entry in the AR System User Preference form.
   For information about the AR System User Preference form, see AR System User Preference form.
2. Click the Logging tab.
3. In the Client section, select Yes next to types of logging you want to perform:
   • Active Links
   • Timings (Web), which logs the mid tier response time
4. Click Save.
   The browser client active link log appears in a separate browser window, so you do not need to define the log file path. After the preferences are changed, log out of any active mid tier session and log on again to obtain the new preference setting.

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 when a request was sent from the browser to the mid tier.
• Time when mid tier received a request.
• Time when an API request was sent from mid tier.
• Time when the mid tier received an API response.
• Time when a response was sent from mid tier to browser.
• Time when the browser received a response.

The timestamp displays local system time.

The log file uses the following tags to display the mid tier response time:

• HTTP – Logs time of request or response between client (browser) and mid tier.
  If you also enable the AR System server logging option in the Remedy Mid Tier Configuration Tool, you can compare the timings (web) log with the server log. 
• MTT – Logs time of request or response received or sent by mid tier.
• CLAT – Logs time of request or response between mid tier and the AR System server.

For information about configuring the Remedy 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, 2019 10:47:46 AM.791 */+HTTP call
<MTT > /* Tue Aug 19 2019 10:47:46.806 */+MidTier GetTableEntryList
<CLAT> /* Tue Aug 19 2019 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 2019 10:47:46.806 */-API call, Procedure #73
<MTT > /* Tue Aug 19 2019 10:47:46.806 */-MidTier
<HTTP> /* Tuesday, August 19, 2019 10:47:46 AM.822 */-HTTP call

Related topic

Log information for active links