text: **13.8 Audit log**
  
  The audit log is useful when analyzing past configuration events, especially when trying to 
  determine, for example, how a volume ended up being shared by two hosts, or why the 
  volume was overwritten. The audit log is also included in the svc_snap support data to aid in 
  problem determination. 
  
  The audit log tracks action commands that are issued through a Secure Shell (SSH) session, 
  management GUI, or Remote Support Assistance. It provides the following entries: 
  
  (cid:2) Identity of the user who issued the action command 
  (cid:2) Name of the actionable command 
  (cid:2) Time stamp of when the actionable command was issued on the configuration node 
  (cid:2) Parameters that were issued with the actionable command 
  
  The following items are not documented in the audit log: 
  
  (cid:2) Commands that fail are not logged. 
  (cid:2) A result code of 0 (success) or 1 (success in progress) is not logged. 
  (cid:2) Result object ID of node type (for the**addnode**command) is not logged. 
  (cid:2) Views are not logged. 
  
  Several specific service commands are not included in the audit log: 
  
  (cid:2) dumpconfig 
  (cid:2) cpdumps 
  (cid:2) cleardumps 
  (cid:2) finderr 
  (cid:2) dumperrlog 
  (cid:2) dumpintervallog 
  (cid:2) svcservicetak dumperrlog 
  (cid:2) svcservicetask finderr 