GET method to obtain logs of a task run from the
As a task run log could be huge with its raw formatting, analyzing it could be time-consuming. Therefore, it is recommended to use the approach explained in the previous section for this live monitoring.
Before you begin
Generate access tokens:
- For users, generate a personal access token by following Generating a Personal Access Token.
- For service accounts, generate a service access token by following Generating a service account token.
Once generated, a service account token expires after 30 minutes. If it expires, generate a new token using the POST method at the endpoint
https://api.<env>.cloud.talend.com/security/oauth/token. For more information about generating a token, see Generating a service account token.
- The user or the service account to be used must have the Author, the Viewer and the Executor permissions for the workspace to which the task to be monitored belongs.
- You must know the ID of the task run you need to monitor.
This ID is available on the Task execution log page, reading as Task execution ID. Or you can obtain this ID via a
GETcall from the
About this task
In this example, Talend API Tester is used to issue API requests. For further information about Talend API Tester, see Talend Cloud API Tester User Guide.
- Open Talend API Tester in your browser and select GET from the Method list.
In the field next to the Method drop-down list, enter the
endpoint to be used:
- In the HEADERS area, click Add header and in the name field that is displayed, enter Authorization and in the value field, enterBearer and your personal access token or service account access token. Enter a whitespace to separate Bearer and the token.
- Click Send to issue your request.
- Click the Save button to save this request in your repository on Talend API Tester.
You can then integrate this API call in your own monitoring system to continuously get and analyze the latest information of this run, so that your monitoring system can send notifications accordingly and timely.
Note that the
isoDatefield appears only in the logs of the tasks running on a engine v2.11.11 and onwards.