Receiving Notifications When Logging Fails
You can subscribe to audit error events to notify administrators when Integration Server cannot write audit logging information to the IS Core Audit Log. Audit error events occur in the following instances:
When a SQLException is encountered while trying to insert an audit record into the audit logging database.
When
Integration Server initializes and cannot connect to the audit logging database.
When the Service logger is configured to retry failed auditing attempts, the audit error event is fired for the initial failure and each subsequent failure.
When you subscribe to an audit error event, you can supply a filter to limit the events that your event handler receives. The filter applies to the concatenated values of the destination and errorCode fields. The following table shows how you can use filters to limit the events that your event handler will receive:
This filter | Limits the events that the event handler receives to |
YourSearchTerm | Events that contain only YourSearchTerm. |
*YourSearchTerm | Events that contain YourSearchTerm at the end of the audit error event value. |
YourSearchTerm* | Events that contain YourSearchTerm at the beginning of the audit error event value. |
*YourSearchTerm* | Events that contain YourSearchTerm anywhere within the audit error event value. |
You subscribe to audit error events using pub.event:addSubscriber and then define the specifications for the audit error event handlers with the pub.event:auditError service. For more information about these services, .
You can indicate whether event handlers for audit error events are invoked synchronously or asynchronously by using the watt.server.event.audit.async server configuration parameter. For more information, see