Search the log for error messages (identified by
ERROR
in the text),
and informative messages (identified by
INFO
in the text), after your
application has run for a considerable period of time in a simulated
production environment. Upon successful completion of this test, you
should be confident that your ARM API calls are correct. A sample log
is provided in
7:47:39.sss: arm_init: Application <Appl_0> User <User_0> = Appl_id <1>
17:47:39.sss: arm_getid: Application <Appl_0> User <User_0> Transaction <Tran_0>
Detail <This is transaction type 0>
17:47:39.sss: arm_getid: Application <Appl_0> User <User_0> Transaction <Tran_0>
= Tran_id <1>
17:47:39.sss: arm_getid: Application <Appl_0> User <User_0> Transaction <Tran_0>
Metric Field <1> Type <1> Name <This is a Counter32 user metric >
17:47:39.sss: arm_start: Application <Appl_0> User <User_0> Transaction <Tran_0>
= Start_handle <1>
17:47:39.sss: arm_start: Application <Appl_0> User <User_0> Transaction <Tran_0>
Start_handle <1> Metric < This is a Counter32 user metric > : <0>
17:47:40.sss: arm_update: Application <Appl_0> User <User_0> Transaction <Tran_0>
Start_handle <1> Metric < This is a Counter32 user metric > : <2>
17:47:41.sss: arm_stop: Application <Appl_0> User <User_0> Transaction <Tran_0>
Start_handle <1> Status <0>
17:47:41.sss: arm_stop: Application <Appl_0> User <User_0> Transaction <Tran_0>
Start_handle <1> Metric < This is a Counter32 user metric > : <4>
17:47:41.sss: arm_end: Application <Appl_0> User <User_0> appl_id <1>
Contents | Next section | Index |