This documentation supports the 9.0 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Escalation log

The escalation log traces escalation activity on the server. It identifies the time an escalation starts, whether it passes the qualification, any actions executed, and the time the escalation stops, as well as the escalation pool. By default, the log file is named arescl.log.

Each line of an escalation log file begins with an <ESCL> prefix and includes the time of each escalation transaction. Escalation logs might have lines that indicate the escalation is going to run in some amount of time. This means the escalation was checked and was found not to require activation at that time.

The following is a sample escalation log file.

<ESCL> <TID: 0000000400> <RPC ID: 0000001731> <Queue: Fast      > <Client-RPC: 390620   > <USER: Demo (Pool 1)                                > <Overlay-Group: 1         > /* Tue Oct 13 2015 22:37:46.9260 */ Escalation Trace Log -- ON (AR Server 9.0.01 201508191530)
<ESCL> <TID: 0000000417> <RPC ID: 0000000006> <Queue: ESCALATION> <Client-RPC: 390603   > <USER: AR_ESCALATOR (Pool 1)                        > <Overlay-Group: 1         > /* Tue Oct 13 2015 22:38:15.7270 */ Checking "ASJ:ScheduleJob (Overlay Group 0)" (enabled) : ready to fire now on "AR System Job"
<ESCL> <TID: 0000000417> <RPC ID: 0000000006> <Queue: ESCALATION> <Client-RPC: 390603   > <USER: AR_ESCALATOR (Pool 1)                        > <Overlay-Group: 1         > /* Tue Oct 13 2015 22:38:15.7390 */ "ASJ:ScheduleJob (Overlay Group 0)" completed : on "AR System Job" (Elapsed time: 0.0 seconds)
<ESCL> <TID: 0000000417> <RPC ID: 0000000000> <Queue: ESCALATION> <Client-RPC: 390603   > <USER: AR_ESCALATOR (Pool 1)                        > <Overlay-Group: 1         > /* Tue Oct 13 2015 22:38:15.7400 */ Checking ASJ:ScheduleJob" (enabled) : going to fire in 60 seconds on "AR System Job"
<ESCL> <TID: 0000000417> <RPC ID: 0000000007> <Queue: ESCALATION> <Client-RPC: 390603   > <USER: AR_ESCALATOR (Pool 1)                        > <Overlay-Group: 1         > /* Tue Oct 13 2015 22:39:15.7420 */ Checking "ASJ:ScheduleJob (Overlay Group 0)" (enabled) : ready to fire now on "AR System Job"
<ESCL> <TID: 0000000417> <RPC ID: 0000000007> <Queue: ESCALATION> <Client-RPC: 390603   > <USER: AR_ESCALATOR (Pool 1)                        > <Overlay-Group: 1         > /* Tue Oct 13 2015 22:39:15.7530 */ "ASJ:ScheduleJob (Overlay Group 0)" completed : on "AR System Job" (Elapsed time: 0.0 seconds)

Tracking escalation overlays

When the server executes an escalation overlay, the escalation log uses the real name of the overlay (<escalationObjectName__o>). It also records this message:

skipping overlaid object <escalationObjectName>

When overlays are disabled on the server and the server executes an overlaid escalation object, it records this message:

skipping overlay object <escalationObjectName>__o

For information about overlay objects, see Customizing applications using overlays and custom objects.

Was this page helpful? Yes No Submitting... Thank you

Comments