Operations management is a tool provided by this product that helps users efficiently manage and maintain various tasks. This document introduces the specific features of operations management.
Please ensure that your account has operations or management permissions.
This feature is supported in the on-premises deployment mode starting from version V2.64.0 of this product.
Users can utilize features such as the task dashboard, operations support, intelligent diagnostics, and resource governance to monitor task progress and status in real time, standardize management of task processes, and quickly identify and resolve issues encountered during task operations.
Operations management currently includes three main features: task dashboard, task operations, and resource governance.
Please log in via the BytePlus Console (Portal) login page. You need to ensure that your account has operations or management permissions.
Task dashboard, task operations, or resource governance. After logging in, you can navigate to the operations management page by clicking System Management in the upper right corner of the page.
Today's task overview page includes the following information:
The historical task insights page contains the following information:
Explanation of search criteria:
Search criteria | Note |
|---|---|
ID / Name | Enter the unique identifier ID or name of the task instance for an exact search. |
Project | Select or enter the project name to filter task instances belonging to a specific project. |
Owner | Select or enter the username of the task owner to filter their task instances. |
Source | Select the task source. Options: dataset, visual modeling. |
Instance status | The default is Failed.
|
Data connection | Filter based on the data connection resources used by the task. |
Trigger mode | Select or enter a trigger mode to filter task instances. Includes routine triggers and backfill triggers.
|
Scheduling frequency | Select the scheduling cycle for the task. Options: minute-level, hour-level, day-level, week-level, month-level, day-level (according to trading calendar), day-level (the day after trading calendar). warning The trading calendar feature is currently only supported in self-hosted deployments of version V2.83.0 and above. To enable this feature, contact BytePlus technical support. |
Start time | Specify a time range to filter task instances that start running within this period. The default is the entire current day. For example, if today is 2025-09-12, the default start time is 2025-09-12 00:00:00 to 2025-09-12 23:59:59. |
Business date | Filter based on the business date (data date) of the data processed by the task. The default is from seven days before the current date to the current date. For example, if today is 2025-09-05, the default business date is 2025-09-05 00:00:00 to 2025-09-12 23:59:59**** |
Queue | Select the resource queue specified at task runtime to filter tasks that consume specific computing resources. For an introduction to queues, see Queue Configuration warning Starting from version V2.87.0, filtering by "queue" is supported. |
The idle dataset management page contains the following information:
The idle Excel/CSV file management page contains the following information:
tip
After deletion, downstream resources associated with these data connections will become unavailable. To restore these data connections, re-upload the Excel/CSV file.
(1) View logs after receiving an alert
First, go to the task board page and click the failed card. The system will automatically redirect to the task operations page and search for failed instances.
Then, select the failed instance and click Log to view the detailed log of the failed task.
(2) Determine whether the alert is caused by a large task backlog
First, on the task board page, click the running card, and then check the resources used by the running instance.
If the resource usage accounts for a large proportion of the entire queue, check the execution duration of the instance. If the duration is long, it indicates that the alert is caused by this task instance, and you need to handle and adjust the task model.
(3) Determine whether the alert is caused by excessive backtracking
If there are many backtracking instances on your task board and the number of slow tasks is zero, it can be confirmed that the alert is caused by excessive backtracking.
In this case, on the task operations page, select [Backtracking] as the trigger method and [Queued] as the instance status to find the details of the specific backtracking task instances.
(4) View detailed information of running tasks
To view detailed information of running tasks, such as dataset, project, owner, and more, directly click the running card on the task board to view the detailed metadata of the running instance. You can also click the [Jump] button to go directly to the dataset or visual modeling task page, and view the task operation log by clicking the [Log] button.
(1) Supplement instance records and rerun tasks
When instance records are missing or the cluster is migrated, you need to supplement the instance records and rerun the tasks. This can be done through custom rerun.
(2) Recover projects by priority
When a task fails and it is necessary to restore the tasks of project 1 with high priority before restoring project 2, you can complete this operation by following the steps below.
Step 1: Click Custom Rerun, select the business date, set the rerun type to Project, enter 1 for Id, select [high-quality] for Priority, and then submit.
Step 2: Click Custom Rerun, select the business date, set the type to Project, select project 2 for Id, select [Ordinary] for Priority, and then submit.
(3) Batch rerun
To perform a batch rerun for specific datasets or visual modeling tasks. First, click the [Custom Rerun] button, select the business date, and set the type to Dataset or Visual Modeling Task. Then, enter the batch Ids separated by English commas in the Id column, and finally click OK.
(4) Terminate backtracking tasks
When task resources are limited, you may need to prioritize routine tasks and terminate all backtracking tasks at once. You can complete this operation by following the steps below.
Step 1: For Task Maintenance, set the trigger mode to [Backtracking], set the instance status to [Queued], select all instances, and click Terminate.
Step 2: For Task Maintenance, set the trigger mode to [Backtracking], set the instance status to [Running], select all instances, and click Terminate.
(5) View the time for queued consumption tasks
When task queuing is normal, you can view the [Queued] card on the Task Dashboard page, which displays the estimated time.
(6) Rerun all failed tasks
First, click the Run Failed button on the Task Dashboard page. The system will redirect to the Task Maintenance page and display all failed tasks for today.
Next, select all failed tasks, and then choose Batch Rerun.
Scenario: Clean up datasets that have been idle for more than 90 days when disk space is limited.
First, on the Idle Datasets page, enter 90 for Idle Days, and then filter the results. Second, after selecting all, you can choose to pause synchronization.
Finally, after refreshing the page, the scheduling type of all selected tasks on the previous page has already been changed to manual.