HULFT Integrate
On the HULFT Integrate page, you can check event logs (execution logs) of scripts that perform data integration.
You can utilize the event logs for the following purposes:
-
Recording and managing execution history of scripts
-
Improving performance of scripts
-
Investigating the causes of failures
By enabling this function for specific situations, you can record information that can be useful regardless of whether you are in the development or operation phase.
To check the event logs for HULFT Integrate, select 
> SERVICE EVENTS > HULFT Integrate in the navigation menu.
-
The user who creates a job becomes the user who executes the job (script).
-
For the names and functions of basic UI elements and other items of HULFT Square, refer to the following topic:
HULFT Integrate
On the HULFT Integrate page, you can check and export the event logs of Data Integration.
- (1) Event log list
-
Event logs are displayed in tabular form.
Selecting
copies the execution ID.The status is indicated as follows:
:
This icon indicates that Data Integration is running.
:
This icon indicates that Data Integration ended successfully.
:
This icon indicates that Data Integration ended in an error.
= Remarks =The maximum number of logs displayed in the event log list is 10,000. If the number of logs exceeds 10,000, please use a filter to narrow down the results.
- (2) Action menu
-
Select this icon to perform operations for event logs.
Selecting
shows the menu of operations below.- Detail
-
Displays detailed information about the selected event log.
- Export
-
Exports the selected event log in CSV file format.
For details on exported logs, refer to Export from Monitoring.
- Cancel script
-
Stops a script that is running.
This is displayed only when a script is running.
Event logs can be broadly categorized into two types: logs that you check on the Monitoring page and logs that are output as audit logs.
In addition, the Monitoring page provides three forms of output: event log list, details screen, and exported CSV file.
Which fields you can check varies depending on the form of output. If you want to check all the fields, export the logs from Monitoring.
Some fields have a different name in each form of output. For details on names, refer to the mapping table below.
|
(B) No. |
(C) No. |
(D) No. |
(B)Audit log |
||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
No. |
Field name |
No. |
Field name |
No. |
Field name |
No. |
Field name |
||||||
|
1 |
sequenceNumber |
2 |
|
|
1 |
Date |
1 |
Exec ID |
1 |
Date |
|||
|
2 |
execId |
|
1 |
|
2 |
Sequence No |
2 |
Status |
2 |
Log level |
|||
|
3 |
time |
1 |
|
1 |
3 |
Log level |
3 |
Project |
3 |
Log type |
|||
|
4 |
logType |
4 |
|
3 |
4 |
Log type |
4 |
Version |
4 |
Event type |
|||
|
5 |
eventType |
5 |
|
4 |
5 |
Event type |
5 |
Script |
5 |
Operation name |
|||
|
6 |
resultStatus |
9 |
2 |
7 |
6 |
Operation module |
6 |
Profile |
6 |
Message |
|||
|
7 |
operationId |
|
|
|
7 |
Operation type |
7 |
Service |
7 |
Result status |
|||
|
8 |
operationModule |
6 |
|
|
8 |
Operation name |
8 |
Executed by |
|
|
|||
|
9 |
operationType |
7 |
|
|
9 |
Result status |
|
|
|
|
|||
|
10 |
operationName |
8 |
|
5 |
10 |
Project name |
|
|
|
|
|||
|
11 |
messageLevel |
3 |
|
2 |
11 |
Project version |
|
|
|
|
|||
|
12 |
messageText |
16 |
|
6 |
12 |
Script name |
|
|
|
|
|||
|
13 |
messageErrorCode |
17 |
|
|
13 |
Executed by |
|
|
|
|
|||
|
14 |
messageErrorType |
18 |
|
|
14 |
Profile name |
|
|
|
|
|||
|
15 |
messageErrorDetail |
19 |
|
|
15 |
Integrate service name |
|
|
|
|
|||
|
16 |
projectId |
|
|
|
16 |
Message |
|
|
|
|
|||
|
17 |
projectVersion |
11 |
4 |
|
17 |
Error code |
|
|
|
|
|||
|
18 |
projectName |
10 |
3 |
|
18 |
Error type |
|
|
|
|
|||
|
19 |
scriptId |
|
|
|
19 |
Error detail |
|
|
|
|
|||
|
20 |
scriptVersion |
|
|
|
|
|
|
|
|
|
|||
|
21 |
scriptName |
12 |
5 |
|
|
|
|
|
|
|
|||
|
22 |
userId |
|
|
|
|
|
|
|
|
|
|||
|
23 |
userAccountId |
|
|
|
|
|
|
|
|
|
|||
|
24 |
executedBy |
13 |
8 |
|
|
|
|
|
|
|
|||
|
25 |
profileId |
|
|
|
|
|
|
|
|
|
|||
|
26 |
profileName |
14 |
6 |
|
|
|
|
|
|
|
|||
|
27 |
instanceId |
|
|
|
|
|
|
|
|
|
|||
|
28 |
instanceName |
15 |
7 |
|
|
|
|
|
|
|
|||
|
29 |
instancePodName |
|
|
|
|
|
|
|
|
|
|||
The fields that are displayed on each page are described below.
