Querying Scheduling Log Details
Function
This API is used to query the log details of a single scheduling.
URI
GET /v2/{project_id}/fdi/instances/{instance_id}/tasks/{task_id}/monitor-logs/{tracking_id}
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. For details about how to obtain the project ID, see Appendix > Obtaining a Project ID in the ROMA Connect API Reference. |
instance_id |
Yes |
String |
Instance ID. |
task_id |
Yes |
String |
Task ID. |
tracking_id |
Yes |
String |
Task tracing ID. |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
Yes |
String |
User token. The token can be obtained by calling an IAM API. The value of X-Subject-Token in the response header is the user token. |
Response Parameters
Status code: 200
Parameter |
Type |
Description |
---|---|---|
id |
String |
Task tracing ID. |
dirty_data_count |
Integer |
Dirty data amount. |
detail_logs |
Array of TaskMonitorDetailLog objects |
Elements on the current page of task monitoring logs. |
Parameter |
Type |
Description |
---|---|---|
id |
String |
Unique ID generated each time when a task is executed. |
status |
Integer |
Detailed task execution status. The status codes are classified as follows: 100 to 499 for the reader side, 500 to 899 for the writer side, and 900 and beyond for others.
|
position |
String |
Phase at which the current step is.
|
position_status |
String |
Status of the current step of a task.
|
stage |
String |
FDI plug-in to which the current step belongs, for example, adapter, apireader, and rdbwriter. |
dirty_data_count |
Integer |
Number of abnormal data records. |
data_count |
Integer |
Number of successful data records. |
data_size |
Number |
Size of success data. The value is a floating-point number. |
data_size_unit |
String |
Unit for measuring the size of success data. |
spend_time |
Integer |
Execution duration, in milliseconds. |
remarks |
String |
Execution details. |
step_begin_time |
Integer |
Start time of this step. The value is in the format of timestamp(ms) and uses the UTC time zone. |
step_end_time |
Integer |
End time of this step. The value is in the format of timestamp(ms) and uses the UTC time zone. |
Status code: 400
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. |
error_msg |
String |
Error message. |
Status code: 404
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. |
error_msg |
String |
Error message. |
Status code: 500
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. |
error_msg |
String |
Error message. |
Example Requests
None
Example Responses
None
Status Codes
Status Code |
Description |
---|---|
200 |
OK |
400 |
Bad Request |
404 |
Not Found |
500 |
Internal Server Error |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot