Audit Logs
This section discusses how to work with audit logs User Interface (UI) page.
The Audit log provides a comprehensive and informative view of the execution of a specific task. It makes it easy for users to find the information they need and troubleshoot problems. This is also useful for pulling audit reports such as who updated a certain record, any access controle rules violation, etc.

LogApi class is used for logging. In turn, it makes use of the information in the context to log a few information such as flowExecId, taskExecId, transactionId, etc.
Types of Logging
Standard logging: Log basic information using log4j to the console. These show up in the stackdriver logs in the cloud).
Audit logging: It logs into DB and also to the console. It has an additional level called “critical” (maps to error for the log4j logging). These logs are collected in the MySql DB. These should be used for important business-level signals.
Standard logging along with Result response: It is similar to basic logging, but it also returns a result object. This is useful to log and construct a Result object (for critical, errors, it constructs a “failed” result, for others it constructs “success”). This should be used when you want to log a message and also return the same message in a Result object. This avoids making two calls one to log and another to construct a Result object.
Audit logging along with Result response: t is similar to audit logging, but it also returns a result object. This should be used when you want to audit log the message and also return the same message in a Result object. This avoids making two calls one to log and another to construct a Result object.
Complete Logging API
Last updated
Was this helpful?