Common Error Table.

 When error happens, exception handling processes notify support team, raise tickets with remedy, and sometimes use log4j to log error messages in the server. In addition to these, it is good to have common error table to log the error. It helps us to analyze system health directly integrating with other tools.

 Following can be the fields of common error table.

Error key: This is the primary key of the table. This can be a sequence.

Program Name: Name of the program. This is applicable where under a single program there are multiple projects.

Project Name: Name of the project under the program.

Process Name: Name of the process producing audit log.

Event Name: Name of the Event /Message/Entity

MessageId: The MessageId uniquely identify the message. This can be used for reconciliation purpose.  This can be optional.

Source: Source System name.

Target: Target System name.

Error Code: This field will contain error code

Error Message: Detail error messages

Error Summary: Brief description of error

Create-timestamp: Timestamp when error occurs

Incident number: Error can be linked with remedy ticket number when a ticket is raised automatically in remedy.

Connector name: Name of the connectors causing error. This can be optional

Attribute1, Attribute2, Attribute3: You can store any important information in these fields like  ids , number etc to  troubleshoot issues