Distinguish between informational log entries and error log entries. Informational log entries provide status information on how requests in the system are fulfilled. Error log entries provide information on exceptions thrown in the system. Each error log entry has an error code.
The following snippet presents example informational log entries about the creation of a document:
(#|2022-06-15T10:49:25.717Z|INFO|461|IMA9_INV_00137|IMA9-CLS-{45c516d0-bae2-4514-aa71-8e03c2ab6a00}|unnamedTenant1|powerUser|Document created revision id 'd2c7dba7-ec98-11ec-a5d3-0242ac110104' document id 'd2c7dba8-ec98-11ec-a5d3-0242ac110104' |#)
Figure 575: Example – informational log entries
The following table describes the most relevant information which is available in an informational log entry, with example values based on the log entries above:
|
Example Value |
Description |
|---|---|
|
2022-06-15T10:49:25.717Z |
timestamp This is a timestamp in the local time zone. |
|
INFO |
log level For related details on log levels in ImageMaster see the AdminClient user manual [UM AdminClient]. |
|
IMA9-CLS-{45c516d0-bae2-4514-aa71-8e03c2ab6a00} |
request ID The request ID can span over several log messages indicating that they belong to the same request. The ID can originate from a web service as specified in the SOAP header (see chapter “Header “requestId””). The prefix of the request ID (here: IMA9-CLS) indicates the component that issued the request (see Request ID prefixes in log messages). |
|
IMA9_INV_00137 |
log ID The log ID identifies the log API call location in the source code that triggered the log message. The IDs in log messages are often used by the support team to analyze system behavior in detail. The prefix of the log ID (here: IMA9_INV) indicates the component that generated the log message (see Log ID prefixes in log messages). |
|
Table 360: Informational log entry in detail |
|
The following log entry indicates an issue. An exception was thrown during a createDocument request (based on code DOC-00044) because a mandatory attribute has not been supplied in the createDocument request:
(#|2022-06-01T14:07:43.399Z|INFO|464|com.tsystems.ima.integrationws.ImaExceptionHelper|IMA9-INV-{704f8f86-3c6c-4dd0-b2f1-1c6f10997e2b}||powerUser|DOC-00044: attribute constraint 02bd2ad2-e1b3-11ec-b5c5-0242ac111203 (checker=MinOccurs) for attribute MyDocumentType.someAttr violated: Attribute has less than 1 values
com.tsystems.ima.domain.business.impl.DocumentExceptionImpl: DOC-00044: attribute constraint 02bd2ad2-e1b3-11ec-b5c5-0242ac111203 (checker=MinOccurs) for attribute MyDocumentType.someAttr violated: Attribute has less than 1 values
at com.tsystems.ima.core.business.RevisionChecks.checkAttributeReferences(RevisionChecks.java:149)
Figure 576: Example – issue indicated by a code in a log entry
The error codes of common error log entries are listed in the appendix and in the IntegrationService web service references.