MapR 5.0 Documentation : Example Log Entries for Audited maprcli Command Executions, REST API Calls, and Actions in MCS

The execution of any maprcli command, REST API call, or action in MCS on the cluster is logged in the local filesystem on the node on which the execution happened. The log file is /opt/mapr/mapr-cli-audit-log/audit.log.json. Auditing of these three types of operation is always enabled, whether or not auditing is enabled for cluster-level operations with the maprcli audit cluster command.

Typical log entries provide a timestamp of the execution, the UID of the user who ran the command, the IP address from which the user ran the command, the command itself, and the status of the execution. Status codes are 0 for success and 1 for failure. The error messages field provides the reasons for failures..

Below are some typical log entries:

"","command":"volume info","arguments":{"name":"mapr.opt"},"status":
1,"errors": ["Volume lookup of mapr.opt failed, No such volume"]}
"","command":"alarm add","arguments":{"baseService":"1","alarm": 
"serviceName":"GatewayService","terse":"nagwsd"},"status":1,"errors":["Terse name of 
nagwsd already exists in the system.","Alarm NODE_ALARM_SERVICE_GATEWAY_DOWN already 
exists in the system."]}
"","command":"volume create","arguments":{"name":"mapr.hbase","path":"/hbase", 
"replicationtype":"low_latency"},"status":1,"errors":["Volume Name mapr.hbase, Already In Use"]}