After you commit and deploy a batch synchronization task to the production environment, use Operation Center to schedule, monitor, and troubleshoot it. This topic covers the O&M operations available for batch synchronization nodes: running, suspending, and resuming schedules; backfilling historical data; setting up alerts; managing resource groups; monitoring data quality; and reading run logs.
Prerequisites
Before you begin, ensure that you have:
-
A batch synchronization task created, deployed, and running as expected. For more information, see Configure a batch synchronization task by using the codeless UI and Configure a batch synchronization task by using the code editor
Before you start
Review the following constraints before performing O&M operations on a batch synchronization task.
Resource group requirements
Batch synchronization tasks are issued to a resource group for Data Integration through a resource group for scheduling. Both resource groups are required for execution. If you use an exclusive resource group for scheduling, scheduling instance charges apply. For more information, see Overview.
After deploying a batch synchronization node, go to the Auto Triggered Nodes page in Operation Center (production environment) to verify that the node code and the resource groups for scheduling and Data Integration are configured correctly.
Data source isolation (standard mode workspaces)
Workspaces in standard mode isolate data sources between environments:
-
Before deployment: the task accesses development environment databases by default.
-
After deployment: the task accesses production environment databases by default.
For more information, see Isolate a data source in the development and production environments.
Scope of this topic
The O&M operations for batch synchronization tasks are the same as for other auto triggered tasks. This topic covers common operations. For a complete reference, see Perform basic O&M operations on auto triggered tasks.
Schedule and manage tasks
DataWorks generates auto triggered instances for a deployed batch synchronization task based on the Instance Generation Mode parameter configured on the Properties tab in DataStudio. The scheduling system runs instances automatically. You can also run tasks manually for testing or data backfill.
|
Operation |
Description |
|
Run a task |
After deployment, the scheduling system runs instances automatically. View instance status on the Auto Triggered Instances page in Operation Center. For manual runs, generate test instances or data backfill instances. |
|
Freeze a task |
On the Auto Triggered Nodes page, freeze an auto triggered task to suspend scheduling. The frozen task and all its downstream tasks cannot be run. To suspend a specific instance and its downstream instances without affecting the task-level schedule, freeze the auto triggered instance instead. |
|
Unfreeze a task |
On the Auto Triggered Nodes page, unfreeze an auto triggered task to resume scheduling. Instances that were frozen along with the task resume running. To run a specific frozen auto triggered instance and its downstream instances, unfreeze that auto triggered instance. |
Whether a task runs on the current day after deployment depends on the Instance Generation Mode configuration. For more information, see Modes in which instances take effect.
Backfill historical data
Use data backfill to synchronize data from a historical time range to a specified table or partition in the destination. This is required when you need to write both incremental data and historical data to the same partition.
When a backfill runs, the system assigns the value you specify for the Data Timestamp parameter to the variable of the corresponding scheduling parameter, so each backfill instance processes the correct historical time slice.
For instructions on running a backfill and viewing backfill instances, see Backfill data and view data backfill instances (new version).
Set up alerts
Create alert rules on the Rule Management page to get notified when a task enters a specific state. To open Rule Management, go to Operation Center and choose Alarm > Rule Management in the left-side navigation pane.
Alerts are triggered when a task reaches one of the following states:
|
Alert state |
Description |
|
Completed |
The task instance finished successfully. |
|
Uncompleted |
The task instance did not finish within the scheduled window. |
|
Error |
The task instance failed. |
|
Overtime |
The task instance exceeded the configured maximum run duration. |
For more information, see Overview.
Manage resource groups
Monitor resource group usage
On the Resource page of Operation Center, view the usage of resource groups that run your nodes. If run logs show long queue wait times, consider changing to a resource group with more capacity. For more information, see Resource O&M.
Change resource groups
Before changing a resource group, verify that network connections are established between the new resource group and all required data sources. Nodes fail to run if the network connections are missing.
You can change the resource group for one or more tasks from either the production or development environment.
|
Environment |
Scope |
Entry point |
|
Production |
Multiple tasks at once |
Go to Operation Center > Auto Triggered Node O&M > Auto Triggered Nodes. Select the tasks, then click Modify Data Integration Resource Group at the bottom of the page. |
|
Development |
Single task |
In DataStudio, open the task configuration tab and click Resource Group configuration in the right-side navigation pane. |
|
Development |
Multiple tasks at once |
In DataStudio, click the icon in the toolbar. On the Node tab, select the tasks, click More, and then select Change Resource Group for Data Integration. |
After changing the resource group in the development environment, commit and redeploy the task to the production environment.
Monitor data quality
On the Data Quality page, configure monitoring rules for destination tables. Rules are triggered after the associated scheduling node runs successfully. If data quality exceptions are detected, Data Quality can fail the task and block downstream tasks based on the rule type, preventing dirty data from propagating downstream.
Make sure a network connection is established between the resource group for scheduling and the destination before configuring data quality monitoring rules.
For destinations that support monitoring rules and instructions on using Data Quality, see Overview.
View run logs
After an auto triggered instance, a data backfill instance, or a test instance completes, view its run logs on the DAG page in Operation Center. For more information, see Appendix: Use the features provided in a DAG.
For a reference on log parameters, see Analyze run logs generated for a batch synchronization task.
View sync statistics
On the O&M Dashboard page in Operation Center, go to the Data Integration tab and click the Batch Synchronization subtab. The subtab shows:
-
Node execution status distribution
-
Data synchronization progress
-
Synchronized data volume
-
Details of individual synchronization tasks
Filter tasks by Source Name, Destination Name, or Whether Internet Traffic Exists.
For more information, see View the statistics on the O&M Dashboard page.
Use LogView
LogView is in invitational preview. To use this feature, contact technical support.
LogView collects event-based data about synchronization tasks, analyzes performance, and displays the results visually. Use it to inspect data transmission rates and logs at a finer granularity than standard run logs.
To access LogView:
-
In Operation Center, choose Auto Triggered Node O&M > Auto Triggered Instances.
-
On the Instance Perspective tab, find the instance and click Perform Diagnostics in the Actions column.
-
On the page that appears, click the Data Integration tab. For more information about intelligent diagnosis, see Intelligent diagnosis.
The Data Integration tab contains three subtabs:
|
Subtab |
Description |
|
Logs |
View detailed log output for the synchronization task. |
|
Progress |
View synchronization metrics: records synchronized, bytes synchronized, record synchronization rate, and byte synchronization rate. Filter by time range to review data from the last 15 days. Click a metric value to view its trend in a chart. |
|
Instance Overview |
Available for auto triggered instances only. Compare synchronization rate, records synchronized, waiting time, and synchronization duration across different instances in the same cycle. |