Using Actuate logging and monitoring APIs : About the usage log : Understanding a usage log entry
 
Understanding a usage log entry
Each usage log entry is a comma-separated list containing up to 40 fields of information about an event. The following example describes a delete user event:
3272649170,5,1,3272649170,3272649170,-,-,0,Administrator,3,
enl2509,enl2509,enl2509,User,testUser,-,-,-,-,-,-,-,-,-,-,
2,0,0,0,0,0,0,0,0,0,0,0,0,0,0
The usage log organizes the entry fields into the following information groups:
*Fields 1 through 10 contain general information:
*Fields 1, 4, and 5 contain the log file time stamp, start time, and finish time. The time is in seconds since 00:00:00, Jan. 1, 1901, GMT.
*Field 2 contains the event type. The numeric values in Table 11‑1 indicate the event types.
Table 11‑1 Event types and the corresponding event values
Event type
Event value
ReportGeneration
1
ReportPrinting
2
ReportViewing
3
ReportDeletion
4
Admin
5
Query
6
Search
7
*Field 3 contains the event result. The value for the event result is either 1 or 0, indicating success or failure.
*Fields 6 through 8 contain report output information, indicating the file name, version, and file size. The report output group information appears only with report events. A dash indicates a field is not used.
*Fields 9 and 10 contain execution information, indicating the user name and the BIRT iHub subsystem where the operation executed. The numeric values in Table 11‑2 indicate the BIRT iHub subsystems.
Table 11‑2 BIRT iHub subsystems and the corresponding ID numbers 
Subsystem
ID number
ReportEngine
1
ViewEngine
2
EncycEngine
3
IntegrationEngine
4
Cache
5
*Fields 11 through 25 contain operational information in string format, including the Encyclopedia volume, BIRT iHub, and cluster names. Fields 26 through 40 contain operational information in numeric format.
The values in these fields depend on the value for the event type in field 2. Table 11‑3 summarizes some of the information available for each event type at Standard level.
Table 11‑3 Examples of information that is available about the different types of events
Event type
Event value
Operation data available
Report generation
1
String fields 11 through 21 display the following information:
– ,executable name, executable version, volume name, server name, cluster name, resource group name, node running request, page count, job name, request ID
 
A dash indicates a field is not used.
Numeric fields 26 through 29 display the following information:
number of pages,submit time, job type, job priority
Report printing
2
String fields 11 through 18 display the following information:
page numbers printed, volume name, printer name, server name, cluster name, node sent to, file type, server request id
 
Numeric fields 26 through 29 display the following information:
number of pages printed, submit time, job type, job priority
Report viewing
3
String fields 11 through 18 display the following information:
output format, report page numbers, volume name, server name, cluster name
 
Numeric field 26 displays the number of pages viewed.
Administrative
5
String fields 11 through 13 display the following information:
volume name, server name, cluster name
 
Numeric field 26 displays an operation ID for an administration event. The following list provides the event name for each operation ID:
*1 Create
*2 Delete
*3 Modify
*4 Login
Actuate Integration service
6
String fields 11 through 14 display the following information:
volume name, server name, cluster name, server request id
 
Numeric fields 26 and 27 display the following information:
request wait time, request generation time
Search
7
String fields 11 through 15 display the following information:
report format, page numbers, volume name, server name, cluster name
 
Numeric field 26 displays the number of pages viewed.