Integration Server 10.7 | Audit Logging Guide | Setting Up IS Core Audit Logging | Configure Audit Logging | Configure Logging Mode (Synchronous or Asynchronous)
 
Configure Logging Mode (Synchronous or Asynchronous)
 
Configure Asynchronous Mode
In the Mode field, choose whether the logger is to write entries to the destination synchronously or asynchronously. In synchronous mode, the logger writes entries directly to the destination. In asynchronous mode, the logger writes entries to a queue, then later writes the entries from the queue to the destination. Each logger has its own queue.
You might use synchronous logging when you have an application that requires some type of auditing to succeed, and you do not want to proceed without knowing that the auditing occurred. Synchronous mode is faster for a logger writing to a database under load. In contrast, synchronous mode might be slower for a logger writing to a file under load.
When the logger tries to log in synchronous mode, one of the following occurs:
*The logger writes the entry to the destination.
*The logger cannot write the entry to the destination because of an error.
The following table describes the logger action for a specific error type.
Error Type
Action
Non-transient
Writes the entry to the FailedAudit_yyyymmdd_hhmmss.log in the Integration Server_directory \instances\instance_name\logs directory.
Transient
Switches to asynchronous mode for the entry.
When the logger tries to write an entry in asynchronous mode, one of the following occurs:
*The logger writes the entry to the destination.
*The logger cannot write the entry to the destination because of an error.
The following table describes the logger action for a specific error type.
Error Type
Action
Non-transient
Writes the entry to the FailedAudit_yyyymmdd_hhmmss.log.
Transient
Retries writing the entry to the destination at the interval specified on the Wait Between Retries field. One of the following occurs:
*The logger writes the entry to the destination on one of the retry attempts.
*Transient errors occur on the retry attempts, and the Maximum Retries value is exceeded. The logger writes the entry to the FailedAudit_yyyymmdd_hhmmss.log.
Note:
The Service logger cannot write the input pipeline to this file, and the API Gateway logger cannot write request and response payloads to the FailedAudit_yyyymmdd_hhmmss.log file.