In the Maximum Queue Size field, specify the maximum number of entries the queue can hold. Specify numerals only (for example, do not include commas or periods).

Choose a value that accommodates your system’s average volume for log entries. If your logging volume has sudden spikes, the queue can usually catch up by writing the pending entries during lulls. Make sure the Integration Server host machine has enough disk space or memory to accommodate the largest possible size of the queue as specified in this field, as well as the requirements of other applications the Integration Server is hosting. The queue’s insertion of logged data into a database is constrained by the database’s availability and connections limit.

If the queue reaches its maximum, the logger writes the log entries to a file called FailedAudit_yyyymmdd_hhmmss.log in the Integration Server_directory \instances\instance_name\logs directory. You can scan the file to find events that were not logged.

If a logger uses a JDBC functional alias for which fail-fast mode is configured, the queue for the loggers must be large enough to hold all the audit logging records it may receive while the audit logging database is unavailable. For more information about fail-fast mode for audit logging, see Queue Size Considerations for Fail-Fast Mode.