Managing Data service and Route tasks in a Dynamic Engine environment in Talend Management Console
Your tasks can be processed by a Dynamic Engine associated with a Dynamic Engine environment.
You can combine Routes and Data services published from Talend Studio with a specific deployment configuration, for example context parameter values, connections, run profiles for Dynamic Engines and so on, to create tasks.
Only Microservice artifacts are supported by Dynamic Engines.
OSGi artifacts are not supported by Dynamic Engines.
In the Deployments area of the task details page, you can see the following information.
Deployment statuses
- Never deployed: The task has never been deployed.
- Deploying: Deployment request has been sent, waiting for the start of the deployment.
- Undeploying: Undeployment request has been sent, waiting for the task to be undeployed.
- Running: The Data service or Route has been started.
- Undeployed: The task has been undeployed.
- Failed: The task execution failed.
| Overall status | Current execution status | Description |
|---|---|---|
| Deploying | Sending deploy request | The deployment request has been sent to the Dynamic Engine. |
| Deploying | Downloading task artifact | The Dynamic Engine has received the deployment request and it has started to download the Data service/Route. |
| Deploying | Starting task | The Data service/Route has been downloaded and the Dynamic Engine is starting its execution. |
| Running | Executing task | The Data service/Route is running and it can receive requests. |
| Undeploying | Sending undeploy request | The undeployment request has been sent to the Dynamic Engine. |
| Undeploying | Undeploying task | The Dynamic Engine has received the undeployment request and it has started to undeploy the task. |
| Undeployed | Task has been undeployed | The task has been undeployed. |
| Failed | Task execution failed | A fatal error has occurred during the task execution. |
| Failed | Deploy failed | The task cannot be deployed. |
| Failed | Undeploy failed | The task cannot be undeployed. |
Logs
Click Logs to access the task execution logs page, where you can monitor the execution in real time.
Execution details
Task version: The version of the task currently in use. To see the task execution ID, click on the information icon.
Deployed by: The name of the user who deployed the task.
Run start time: The exact time and date when the task deployment has started.
Run end time: The exact time and date when the task has been undeployed.
Metrics
To receive metric data, the task must be in the Running status and the metric path must be defined. The numbers indicate the total requests after the last restart. If the last metric record is older than 20 minutes, it may indicate that the data service or Route does not work properly anymore.
- Requests / MIN: number of invocations in the last minute
- Requests / 5 MIN: number of invocations in the last 5 minutes
- Requests / 15 MIN: number of invocations in the last 15 minutes
- Total requests: number of invocations since the last (re)start
- Completed: number of Camel exchanges finished with a completed state
- Failed: number of Camel exchanges finished with a failed state
- Total: number of exchanges processed since last (re)start
- Last process time (sec): last exchange processing time in seconds
- Mean process time (sec): average processing time since the last (re)start in seconds
Deployment history
To view all the current and previous task deployments on the same page, click Deployment history.