Using Actuate logging and monitoring APIs : About the error log : Understanding an error log entry
 
Understanding an error log entry
Each error log entry is a comma-separated list containing up to 12 fields about an error-related event. The following example describes an error in a submit job event:
3272648796,2,3230,SubmitJob,Administrator,"Invalid start time or end time.",enl2509,enl2509,enl2509,-,-,-
The error log organizes the entry fields into the following information groups:
*Fields 1 through 9 contain general information:
*Field 1 contains the log file time stamp. The time is in seconds since 00:00:00, Jan. 1, 1901, GMT.
*Field 2 contains the error severity level, an integer between 1 and 4. The numeric values in Table 11‑4 indicate the level.
*Field 3 contains the Error ID code.
Table 11‑4 Error severity levels and the corresponding values 
Error severity level
Value
Information
1
Warning
2
Severe
3
Fatal
4
*Field 4 contains the Service name, indicating the subsystem where the error occurred such as the Factory, Encyclopedia, View, or Request service.
*Field 5 indicates the Encyclopedia volume user.
*Field 6 contains the error message.
*Field 7 contains the Encyclopedia volume name.
*Field 8 contains the BIRT iHub cluster name.
*Field 9 contains the BIRT iHub node name.
*Depending on the error, fields 10 through 12 can contain information such as a file name and ID number. A dash indicates a field is not used.
Table 11‑5 summarizes some of the information available in fields 10 through 12 for an error log entry at Standard level.
Table 11‑5 Information that is available for error log entries at the Standard level 
Type of error
Operation data available
Cluster master failover
Fields 10 and 11 display the following data:
*Original cluster master
*New cluster master
Encyclopedia volume user activity
Fields 10 through 12 can contain error parameters such as the following items:
*Object name
*ID number
Volume failover
Fields 10 and 11 contain the following data:
*Primary server
*Backup server used
Volume online or offline
Fields 10 and 11 contain the following data:
*Volume name
*Operation type either online or offline
BIRT iHub node start or stop
Field 10 contains the BIRT iHub name
Service enable or disable
Fields 10 and 11 contain the following data:
*Server name
*List of services
Archive service error
Fields 10 through 12 contain error parameters
Encyclopedia volume job purging field 4 is Job Purge
Fields 10 through 12 contain error parameters
Encyclopedia volume health monitoring field 4 is Encyclopedia Health Monitor
Fields 10 through 12 contain error parameters