Exception Event Fields
This section describes all the exception event fields with examples.
Field Name | Description |
---|---|
Exception Code | Represents the categorical error logged for easier identification of related errors. |
Exception ID | A unique ID that got generated for tracking an exception occurred during the execution of a program that had disrupted the normal flow of instructions. |
Exception Keys | An array of objects with custom properties (key-value pairs) that the application or component can populate helps diagnose failures. Depending on the technology stack, various properties can be helpful in these situations with a tightly coupled technology. |
Severity | The classification is used to determine the appropriate action to be taken from a support perspective.
For example, High, Medium, and Low. |
Below table describes all the attributes that are used in View log and associated with exception events.
Attribute Name | Type | Mandatory | Character Length |
---|---|---|---|
Application ID | String | Yes | 8 |
Application Name | String | Yes | 32 |
Client (Client ID) | String | Yes | 32 |
Exception Code | String | Yes | 16 |
Component ID | String | Yes | 16 |
Component Name | String | Yes | 32 |
Correlation ID | GUID | No | 36 |
Description (Detail) | String | Yes | N/A |
Event ID | GUID | No | 36 |
Exception ID | GUID | No | 36 |
Exception Keys | String | No | N/A |
Message ID | GUID | No | 36 |
Group | String | No | 32 |
Reference ID | String | No | 64 |
Severity | Enum | Yes | 32 |
Study ID | String | No | 32 |
Timestamp | Time | Yes | 16 |
Transaction ID | Guid | Yes | 36 |
Type | String | Yes | 16 |
User ID | String | No | 64 |