API log


The API log traces all API calls run on the server, regardless of their origin.

By default, the log file is named arapi.log. Each line of an API log file begins with <API>.

All AR System operations are logged, including the activity of Developer Studio and applications that you have developed.

Each API transaction includes a time stamp and the user name. The entry details include information about the API calls encountered and some information about parameters passed.

The following example shows a portion of an API log file:

<API > <TrID: 7HXA4gCaRJWg_ttOjK_5pQ:0147531> <TID: 0000000500> <RPC ID: 0000105271> <Queue: Fast      > <Client-RPC: 390620   > <USER: Remedy Application Service                   > <Overlay-Group: 1         > /* 2025-04-18T17:02:56.795+0000 */ -GSI              OK
<API > <TrID: 7HXA4gCaRJWg_ttOjK_5pQ:0147532> <TID: 0000000501> <RPC ID: 0000105272> <Queue: Fast      > <Client-RPC: 390620   > <USER: Remedy Application Service                   > <Overlay-Group: 1         > /* 2025-04-18T17:02:56.796+0000 */ +GSI     ARGetServerInfo -- as user Remedy Application Service from Unidentified Client (protocol 29) at IP address 172.19.0.7 using RPC // :q:0.0s null
<API > <TrID: 7HXA4gCaRJWg_ttOjK_5pQ:0147532> <TID: 0000000501> <RPC ID: 0000105272> <Queue: Fast      > <Client-RPC: 390620   > <USER: Remedy Application Service                   > <Overlay-Group: 1         > /* 2025-04-18T17:02:56.796+0000 */ -GSI              OK

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*