When real-time compute tasks fail or behave unexpectedly in production, you need a single place to check task status, review logs, and take corrective action. The Real-time Computing Nodes page in Operation Center provides that view: a live list of all real-time compute tasks in the production environment, with controls to start, stop, undeploy, and configure alerts — and direct access to runtime logs for diagnosing failures.
Limits
Only tasks submitted from EMR Spark Streaming and Flink SQL Streaming nodes are supported.
Go to the Real-time Computing Nodes page
-
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose Data Development and O\&M \> Operation Center. On the page that appears, select the desired workspace from the drop-down list and click Go to Operation Center.
-
In the left-side navigation pane of the Operation Center page, choose Real-time Node O\&M \> Real-time Computing Nodes.
View and manage real-time compute tasks
The Stream Task page lists all real-time compute tasks in the production environment.
Search and filter tasks
Search by task ID (exact match) or task name (fuzzy match). Narrow results using these filters: Status, Cluster Type, Cluster Name, Task Type, and Responsible Person.
All active filter conditions apply simultaneously. Only tasks matching all specified criteria are displayed.
Task list fields
| Field | Description |
|---|---|
| Node Name | Name of the task. Click the name to open the task details panel. |
| Node ID | Unique ID of the task. |
| Status | Current task state. See Task states below. |
| Start running | Time when the task started running. |
| End Running | Time when the task stopped running. |
| Runtime | Total running duration, in seconds. |
| Task type | Node type that submitted the task (EMR Spark Streaming or Flink SQL Streaming). |
| Cluster Type | Type of cluster running the task (E-MapReduce or Flink). |
| Cluster Name | Name of the associated cluster. |
| Deployed At | Time when the task was deployed, in yyyy-MM-dd HH:mm:ss format. |
| Responsible Person | Owner of the workspace the task belongs to. |
Sort tasks in ascending or descending order by Starting running, End Running, or Runtime.
Task states
| State | Description | What to do |
|---|---|---|
| Not Running | The task has not started. | — |
| Generating | The task is being initialized. | — |
| Pending (Resources) | The task is waiting for cluster resources to become available. | Check cluster capacity. |
| Starting | The task is starting up. | — |
| Running | The task is running normally. | — |
| Stopped | The task was stopped manually using Terminate. | — |
| Failed | The task encountered an error and stopped. | Open the task details panel and check the Runtime Log tab for error details. |
| Restarting | The task is being restarted after a failure or manual restart. | — |
| Undeploying | The task is being undeployed. | — |
Perform operations on tasks
| Operation | Description |
|---|---|
| Start | Start the task. |
| Terminate | Stop the task. |
| Undeploy | Undeploy the task. |
| Monitoring Setting | Configure alert rules for the task. If the task fails, the system sends an alert to the specified contacts via text message, email, mobile phone, DingTalk chatbot, or webhook URL. |
For information about configuring an email address and mobile phone number for alert contacts, see What can I do if I am unable to receive alert notifications after I configure an alert in Operation Center? For information about configuring a DingTalk chatbot and obtaining a webhook URL, see Scenario practices: Send alert notifications to a DingTalk group.
Perform batch operations
Select multiple tasks, then click Start, Terminate, Undeploy, or Monitoring Setting to apply the operation to all selected tasks at once.
View task details
On the Stream Task page, click a task name to open its details panel.
The panel has four tabs:
| Tab | What it shows | When to use |
|---|---|---|
| Details | Basic task configuration and metadata. | Review task settings and deployment information. |
| Runtime Log | Logs generated during task execution, including errors and processing events. | Diagnose task failures and unexpected behavior. |
| Operation Log | A record of manual operations performed on the task, such as start, stop, and deploy actions. | Review who performed which operations and when. |
| Code | The source code of the task. | Inspect the task logic. |