@clickzetta/cz-cli-darwin-arm64 0.3.94 → 0.3.96

package/bin/skills/lakehouse-doc-en/references/monitor_and_alert.md

@@ -0,0 +1,177 @@
+# Monitoring and Alerting
+
+## Overview
+
+The monitoring and alerting system is a powerful feature set that allows users to monitor key indicators such as task run status in real time using system built-in rules or custom rules. Once an anomaly is detected, the system sends timely alert notifications to help you ensure data flow stability and reliability.
+
+## Core Concepts
+
+| Concept   | Description                                                                          |
+| ---- | ----------------------------------------------------------------------------- |
+| Monitoring Rule | A set of configuration information containing key attributes such as specific objects and message types, informing the system which key messages to watch for. Rules configured for specific objects and specific conditions generate alert events when conditions are met. |
+| Alert Event | Based on monitoring rules, a potential event record that needs to trigger an alert notification when monitoring conditions are satisfied.                                          |
+| Notification History | The actual notification records pushed to users after alert events are generated. Alert notification delivery is influenced by the following three strategies.                                    |
+| Notification Strategy | Defines which notification channels to use, sending frequency, etc., when pushing alerts to recipients.                                          |
+
+## Monitoring Rules
+
+The monitoring rules list displays all currently configured rules. Users can filter to quickly find the needed rules.
+
+![Monitoring Rules List](.topwrite/assets/226957dd01/8d11a86d9d484c752427e010555ea2d1efbf0b50.png)
+
+For individual rules, the following operations are available:
+
+| Operation Name    | Behavior Definition                     | Authorized Personnel        |
+| ------- | ------------------------ | ------------ |
+| View Details    | Open the monitoring alert rule details page to view complete information.     | Open to all instance members    |
+| Enable/Disable   | Enable or disable the alert rule.             | Instance administrator, instance operations role |
+| Copy      | Copy the configuration attributes of the current rule to create a new rule.   | Instance administrator, instance operations role |
+| Edit      | Modify the attributes of the monitoring rule through appropriate interactive methods. | Instance administrator, instance operations role |
+| Subscribe/Unsubscribe | Add or remove the operator from the alert recipient list.         | Open to all instance members    |
+
+### System Built-in Rules
+
+The system provides some preset global monitoring rules that users can enable as needed.
+
+| Rule Name       | Rule Function          | Default Status |
+| ---------- | ------------- | ------ |
+| General Rule - Monitor Task Failure | Default rule for monitoring task instance failures. | Disabled by default   |
+
+### Create a New Monitoring Rule
+
+Click the "Create Rule" button to create custom monitoring rules based on your needs.
+
+![Create Monitoring Rule Interface](.topwrite/assets/226957dd01/d2242b08605d2a3ad9b3713d8e6e6d7ab191e066.png =493)
+
+| Category        | Parameter                                     | Description                                                                                                                                                                   |
+| --------- | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Basic Information      | Name                                     | Enter the name of the new custom rule.                                                                                                                                                        |
+| Description        | Optional. You can add a description of the current rule or note the handling procedures after receiving an alert. |                                                                                                                                                                      |
+| Trigger Condition      | Monitoring Items                                   | The specific monitoring objects. The system currently supports "Event Monitoring" and "Metric Monitoring" two modes.                                                                                                                                     |
+| Filter Condition      | Filter conditions for messages. Multiple conditions are combined with "AND".                 |                                                                                                                                                                      |
+| Alert Level      | Alert Level                                   | The alert level configuration in the universal template is as follows, and users can also customize notification methods for different levels in the notification strategy. Critical: Send via all alert channels, including phone. Severe: Send via all alert channels, including phone. Warning: In-system, email, SMS, Webhook, excluding phone. Info: In-system, email, Webhook, excluding phone and SMS. Clicking the alert level will link to the information displayed in the notification strategy list below. |
+| Monitoring Notification      | Notification Strategy                                   | Click the dropdown to select a notification strategy managed in "Notification Strategy", or click the "+" button to create a new one. For configuration details, see Notification Strategy.                                                                                                                |
+| Alert Subscription      | Dropdown to select the specific recipients to be notified for this rule.                     |                                                                                                                                                                      |
+| Webhook Notification | Select notification method. Currently supported types: DingTalk, Feishu.              |                                                                                                                                                                      |
+| Notification Start Time    | The start time for sending notifications after the monitoring rule is triggered.                       |                                                                                                                                                                      |
+| Notification End Time    | The end time for sending notifications after the monitoring rule is triggered.                       |                                                                                                                                                                      |
+
+#### Trigger Condition Rules
+
+Trigger conditions consist of monitoring items, metric calculation methods, thresholds, and trigger methods. The system currently supports "Event Monitoring" and "Metric Monitoring" two types.
+
+**Metric-Based Monitoring Configuration**
+
+![](.topwrite/assets/226957dd01/0d872f1cb6d11f16e4a48c9a6466ac9d43eb8606.png =548)
+
+For metric monitoring, after defining the calculation method and threshold, two trigger methods are supported.
+
+Continuous: Once the metric touches the threshold for N consecutive times, a monitoring alert is triggered.
+
+Check Interval: Users define that when the threshold is touched a cumulative N times within the check interval, a monitoring alert is triggered.
+
+Metric monitoring configuration: Users can define calculation methods and thresholds, and select trigger methods. For example, configure the full-incremental integrated sync task delay metric: delay time >= 50 seconds, continuous for 3 data points, alert frequency limited to once every 30 minutes.
+
+![](.topwrite/assets/226957dd01/4f091acaf0cca77057e17882d353011c0853801e.png =600)
+
+At 00:40, when the threshold is exceeded for 3 consecutive times, the first alert is triggered. From then until 01:50, it remains in the first alert stage.
+
+During the alert stage, subsequent time points are evaluated based on the alert frequency, determining whether to continue sending alerts. With the limit set to once every 30 minutes, alerts are sent at 01:10 and 01:40.
+
+Starting from 02:00, the next three metric values are all below the threshold, so the first alert recovers and no further alert notifications are triggered.
+
+If the user's trigger method is based on cumulative count within the check interval.
+
+**Event-Based Monitoring Configuration**
+
+Event monitoring generates alerts when specific events or conditions occur. Users can monitor based on operational instances or data quality validation rules within the product. Based on currently supported behaviors, event monitoring is mainly divided into two categories:
+
+Task Operations: Various periodic scheduling tasks configured in development scenarios, or real-time running task instances.
+
+Data Quality: Various table quality monitoring tasks configured in data quality.
+
+> Refer to [Monitoring Item Specification](monitoring_item_specification.md) for detailed metric definitions.
+
+#### Alert Events
+
+The alert event list displays all alert information generated after monitoring rules are triggered. Users can perform operations on alert events in the list, such as suppress or close.
+
+Suppress: Set the current alert event to not send messages for a specified number of minutes.
+
+Close: Close the current alert event and stop receiving such messages.
+![Alert Event List](.topwrite/assets/226957dd01/c8922b31a22c405c99d2ca37c0c04661f5fd9524.png =680)
+
+#### Alert Event Handling Operations
+
+| Operation                      | Definition                 | Applicable Scenario                | Scope   |
+| ----------------------- | ------------------ | ------------------- | ------ |
+| Suppress                      | Stop sending messages for the alert event within a specified time period. | A known issue is being addressed and repeated alerts are not needed temporarily. | Current alert event |
+| Close                      | Close the alert event and stop receiving such messages.    | Issue has been resolved or confirmed as a false alarm.         | Current alert event |
+| Auto Close  (not triggered by clicking on the alert event) | The system automatically closes the alert after detecting issue recovery.   | Task instance rerun succeeds, manually set to success.      | Related alert events |
+
+## Notification History
+
+Notification history records all notification messages actually delivered based on notification strategies.
+
+![Notification History List](.topwrite/assets/226957dd01/df5b643e1c5d0b495e559e67d30d3dbe9d699179.png =680)
+
+## Notification Strategy
+
+The notification strategy list displays all defined notification strategies. Users can search and filter.
+
+![Notification Strategy List](.topwrite/assets/226957dd01/34595b2465ace2f704ee53ff5906a5a81e4f85d2.png =680)
+
+![](.topwrite/assets/226957dd01/d7725ff84c1b3f1871e83dc4e23b576edad6d103.png =680)
+
+### Create a New Notification Strategy
+
+Users can click the "Create Strategy" button to create a new notification strategy based on their needs.
+
+![Create Notification Strategy Interface](.topwrite/assets/226957dd01/a17beff395adf70cdc56ab189d7dbb09e5263f8d.png =360)
+
+| Category   | Parameter       | Description                                                                                                                       |
+| ---- | -------- | ------------------------------------------------------------------------------------------------------------------------ |
+| Basic Information | Name       | The name of the notification strategy.                                                                                                                  |
+|      | Description       | Optional. You can add a description of the current rule.                                                                                                       |
+| Notification Method | Critical Alert     | Set the specific notification method for different alert levels. Supported methods: Webhook, SMS, Phone.                                                                                |
+|      | Severe Alert     |                                                                                                                          |
+|      | Warning Alert     |                                                                                                                          |
+|      | Info Alert     |                                                                                                                          |
+| Notification Time | Send Interval (minutes) | The time interval between two alerts.                                                                                                             |
+|      | Max Send Count   | The maximum number of alerts. After exceeding this count, no more alerts will be generated.                                                                                                 |
+|      | Do Not Disturb Start Time  | During the do-not-disturb period, the system will not send alerts. For example, if a task failure alert is configured and the do-not-disturb time is set from 00:00 to 08:00, no alert will be sent during that period. If at 08:00 the task is still in an abnormal state, an alert will be sent. |
+|      | Do Not Disturb End Time  |                                                                                                                          |
+
+## Configuration Management
+
+Configuration management allows users to configure personal information and Webhooks.
+
+### Personal Configuration
+
+Users can modify their phone number and email address used for receiving alerts, and set do-not-disturb periods in personal configuration.
+
+![Personal Configuration Interface](.topwrite/assets/226957dd01/d7725ff84c1b3f1871e83dc4e23b576edad6d103.png =680)
+
+### Webhook Configuration
+
+Webhook configuration is used to define Webhook channels for alert delivery. Currently supports Feishu and DingTalk.
+
+![Webhook Configuration Interface](.topwrite/assets/226957dd01/6a8bc6fc74fb8f046f7169d91fac4169aab3b968.png =680)
+
+#### Create a New Webhook Configuration
+
+Users can click the "Create Configuration" button and fill in the required parameters to create a new Webhook configuration. It is recommended to test before saving to ensure the configuration is correct.
+
+![](.topwrite/assets/226957dd01/4ce77ae787a0c4c3c8d908b7c6feb5f5beaf7241.png =300)
+
+## Other
+
+### Automatic Closure of Monitoring Alerts
+
+For monitoring alerts on task instance run failures, after the Operations Center handles the instance and it recovers successfully (such as manually setting success or rerunning the instance successfully), the corresponding alert event will be automatically set to closed. No manual closure is needed.
+
+### Webhook Alert Security Settings
+
+For IM platforms such as DingTalk, Webhook alert delivery has certain security settings. Add "Singdata" as a custom keyword in the security settings.
+
+![](.topwrite/assets/image_1748598090100.png =300)

package/bin/skills/lakehouse-doc-en/references/monitoring_and_alerting.md

@@ -0,0 +1,177 @@
+# Monitoring and Alerting
+
+## Overview
+
+The monitoring and alerting system is a powerful feature set that allows users to monitor key indicators such as task run status in real time using system built-in rules or custom rules. Once an anomaly is detected, the system sends timely alert notifications to help you ensure data flow stability and reliability.
+
+## Core Concepts
+
+| Concept   | Description                                                                          |
+| ---- | ----------------------------------------------------------------------------- |
+| Monitoring Rule | A set of configuration information containing key attributes such as specific objects and message types, informing the system which key messages to watch for. Rules configured for specific objects and specific conditions generate alert events when conditions are met. |
+| Alert Event | Based on monitoring rules, a potential event record that needs to trigger an alert notification when monitoring conditions are satisfied.                                          |
+| Notification History | The actual notification records pushed to users after alert events are generated. Alert notification delivery is influenced by the following three strategies.                                    |
+| Notification Strategy | Defines which notification channels to use, sending frequency, etc., when pushing alerts to recipients.                                          |
+
+## Monitoring Rules
+
+The monitoring rules list displays all currently configured rules. Users can filter to quickly find the needed rules.
+
+![Monitoring Rules List](.topwrite/assets/226957dd01/8d11a86d9d484c752427e010555ea2d1efbf0b50.png)
+
+For individual rules, the following operations are available:
+
+| Operation Name    | Behavior Definition                     | Authorized Personnel        |
+| ------- | ------------------------ | ------------ |
+| View Details    | Open the monitoring alert rule details page to view complete information.     | Open to all instance members    |
+| Enable/Disable   | Enable or disable the alert rule.             | Instance administrator, instance operations role |
+| Copy      | Copy the configuration attributes of the current rule to create a new rule.   | Instance administrator, instance operations role |
+| Edit      | Modify the attributes of the monitoring rule through appropriate interactive methods. | Instance administrator, instance operations role |
+| Subscribe/Unsubscribe | Add or remove the operator from the alert recipient list.         | Open to all instance members    |
+
+### System Built-in Rules
+
+The system provides some preset global monitoring rules that users can enable as needed.
+
+| Rule Name       | Rule Function          | Default Status |
+| ---------- | ------------- | ------ |
+| General Rule - Monitor Task Failure | Default rule for monitoring task instance failures. | Disabled by default   |
+
+### Create a New Monitoring Rule
+
+Click the "Create Rule" button to create custom monitoring rules based on your needs.
+
+![Create Monitoring Rule Interface](.topwrite/assets/226957dd01/d2242b08605d2a3ad9b3713d8e6e6d7ab191e066.png =493)
+
+| Category        | Parameter                                     | Description                                                                                                                                                                   |
+| --------- | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Basic Information      | Name                                     | Enter the name of the new custom rule.                                                                                                                                                        |
+| Description        | Optional. You can add a description of the current rule or note the handling procedures after receiving an alert. |                                                                                                                                                                      |
+| Trigger Condition      | Monitoring Items                                   | The specific monitoring objects. The system currently supports "Event Monitoring" and "Metric Monitoring" two modes.                                                                                                                                     |
+| Filter Condition      | Filter conditions for messages. Multiple conditions are combined with "AND".                 |                                                                                                                                                                      |
+| Alert Level      | Alert Level                                   | The alert level configuration in the universal template is as follows, and users can also customize notification methods for different levels in the notification strategy. Critical: Send via all alert channels, including phone. Severe: Send via all alert channels, including phone. Warning: In-system, email, SMS, Webhook, excluding phone. Info: In-system, email, Webhook, excluding phone and SMS. Clicking the alert level will link to the information displayed in the notification strategy list below. |
+| Monitoring Notification      | Notification Strategy                                   | Click the dropdown to select a notification strategy managed in "Notification Strategy", or click the "+" button to create a new one. For configuration details, see Notification Strategy.                                                                                                                |
+| Alert Subscription      | Dropdown to select the specific recipients to be notified for this rule.                     |                                                                                                                                                                      |
+| Webhook Notification | Select notification method. Currently supported types: DingTalk, Feishu.              |                                                                                                                                                                      |
+| Notification Start Time    | The start time for sending notifications after the monitoring rule is triggered.                       |                                                                                                                                                                      |
+| Notification End Time    | The end time for sending notifications after the monitoring rule is triggered.                       |                                                                                                                                                                      |
+
+#### Trigger Condition Rules
+
+Trigger conditions consist of monitoring items, metric calculation methods, thresholds, and trigger methods. The system currently supports "Event Monitoring" and "Metric Monitoring" two types.
+
+**Metric-Based Monitoring Configuration**
+
+![](.topwrite/assets/226957dd01/0d872f1cb6d11f16e4a48c9a6466ac9d43eb8606.png =548)
+
+For metric monitoring, after defining the calculation method and threshold, two trigger methods are supported.
+
+Continuous: Once the metric touches the threshold for N consecutive times, a monitoring alert is triggered.
+
+Check Interval: Users define that when the threshold is touched a cumulative N times within the check interval, a monitoring alert is triggered.
+
+Metric monitoring configuration: Users can define calculation methods and thresholds, and select trigger methods. For example, configure the full-incremental integrated sync task delay metric: delay time >= 50 seconds, continuous for 3 data points, alert frequency limited to once every 30 minutes.
+
+![](.topwrite/assets/226957dd01/4f091acaf0cca77057e17882d353011c0853801e.png =600)
+
+At 00:40, when the threshold is exceeded for 3 consecutive times, the first alert is triggered. From then until 01:50, it remains in the first alert stage.
+
+During the alert stage, subsequent time points are evaluated based on the alert frequency, determining whether to continue sending alerts. With the limit set to once every 30 minutes, alerts are sent at 01:10 and 01:40.
+
+Starting from 02:00, the next three metric values are all below the threshold, so the first alert recovers and no further alert notifications are triggered.
+
+If the user's trigger method is based on cumulative count within the check interval.
+
+**Event-Based Monitoring Configuration**
+
+Event monitoring generates alerts when specific events or conditions occur. Users can monitor based on operational instances or data quality validation rules within the product. Based on currently supported behaviors, event monitoring is mainly divided into two categories:
+
+Task Operations: Various periodic scheduling tasks configured in development scenarios, or real-time running task instances.
+
+Data Quality: Various table quality monitoring tasks configured in data quality.
+
+> Refer to [Monitoring Item Specification](monitoring_item_specification.md) for detailed metric definitions.
+
+#### Alert Events
+
+The alert event list displays all alert information generated after monitoring rules are triggered. Users can perform operations on alert events in the list, such as suppress or close.
+
+Suppress: Set the current alert event to not send messages for a specified number of minutes.
+
+Close: Close the current alert event and stop receiving such messages.
+![Alert Event List](.topwrite/assets/226957dd01/c8922b31a22c405c99d2ca37c0c04661f5fd9524.png =680)
+
+#### Alert Event Handling Operations
+
+| Operation                      | Definition                 | Applicable Scenario                | Scope   |
+| ----------------------- | ------------------ | ------------------- | ------ |
+| Suppress                      | Stop sending messages for the alert event within a specified time period. | A known issue is being addressed and repeated alerts are not needed temporarily. | Current alert event |
+| Close                      | Close the alert event and stop receiving such messages.    | Issue has been resolved or confirmed as a false alarm.         | Current alert event |
+| Auto Close  (not triggered by clicking on the alert event) | The system automatically closes the alert after detecting issue recovery.   | Task instance rerun succeeds, manually set to success.      | Related alert events |
+
+## Notification History
+
+Notification history records all notification messages actually delivered based on notification strategies.
+
+![Notification History List](.topwrite/assets/226957dd01/df5b643e1c5d0b495e559e67d30d3dbe9d699179.png =680)
+
+## Notification Strategy
+
+The notification strategy list displays all defined notification strategies. Users can search and filter.
+
+![Notification Strategy List](.topwrite/assets/226957dd01/34595b2465ace2f704ee53ff5906a5a81e4f85d2.png =680)
+
+![](.topwrite/assets/226957dd01/d7725ff84c1b3f1871e83dc4e23b576edad6d103.png =680)
+
+### Create a New Notification Strategy
+
+Users can click the "Create Strategy" button to create a new notification strategy based on their needs.
+
+![Create Notification Strategy Interface](.topwrite/assets/226957dd01/a17beff395adf70cdc56ab189d7dbb09e5263f8d.png =360)
+
+| Category   | Parameter       | Description                                                                                                                       |
+| ---- | -------- | ------------------------------------------------------------------------------------------------------------------------ |
+| Basic Information | Name       | The name of the notification strategy.                                                                                                                  |
+|      | Description       | Optional. You can add a description of the current rule.                                                                                                       |
+| Notification Method | Critical Alert     | Set the specific notification method for different alert levels. Supported methods: Webhook, SMS, Phone.                                                                                |
+|      | Severe Alert     |                                                                                                                          |
+|      | Warning Alert     |                                                                                                                          |
+|      | Info Alert     |                                                                                                                          |
+| Notification Time | Send Interval (minutes) | The time interval between two alerts.                                                                                                             |
+|      | Max Send Count   | The maximum number of alerts. After exceeding this count, no more alerts will be generated.                                                                                                 |
+|      | Do Not Disturb Start Time  | During the do-not-disturb period, the system will not send alerts. For example, if a task failure alert is configured and the do-not-disturb time is set from 00:00 to 08:00, no alert will be sent during that period. If at 08:00 the task is still in an abnormal state, an alert will be sent. |
+|      | Do Not Disturb End Time  |                                                                                                                          |
+
+## Configuration Management
+
+Configuration management allows users to configure personal information and Webhooks.
+
+### Personal Configuration
+
+Users can modify their phone number and email address used for receiving alerts, and set do-not-disturb periods in personal configuration.
+
+![Personal Configuration Interface](.topwrite/assets/226957dd01/d7725ff84c1b3f1871e83dc4e23b576edad6d103.png =680)
+
+### Webhook Configuration
+
+Webhook configuration is used to define Webhook channels for alert delivery. Currently supports Feishu and DingTalk.
+
+![Webhook Configuration Interface](.topwrite/assets/226957dd01/6a8bc6fc74fb8f046f7169d91fac4169aab3b968.png =680)
+
+#### Create a New Webhook Configuration
+
+Users can click the "Create Configuration" button and fill in the required parameters to create a new Webhook configuration. It is recommended to test before saving to ensure the configuration is correct.
+
+![](.topwrite/assets/226957dd01/4ce77ae787a0c4c3c8d908b7c6feb5f5beaf7241.png =300)
+
+## Other
+
+### Automatic Closure of Monitoring Alerts
+
+For monitoring alerts on task instance run failures, after the Operations Center handles the instance and it recovers successfully (such as manually setting success or rerunning the instance successfully), the corresponding alert event will be automatically set to closed. No manual closure is needed.
+
+### Webhook Alert Security Settings
+
+For IM platforms such as DingTalk, Webhook alert delivery has certain security settings. Add "Singdata" as a custom keyword in the security settings.
+
+![](.topwrite/assets/image_1748598090100.png =300)

package/bin/skills/lakehouse-doc-en/references/monitoring_item_specification.md

@@ -0,0 +1,44 @@
+# Monitoring Item Specification
+
+This document describes the specific definitions and scope of "Event" and "Metric" monitoring items available when configuring monitoring rules.
+
+## Event-Based Monitoring
+
+| Event Name               | Target Objects                                                           | Scope Description                                                                                      |
+| ------------------ | -------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
+| Scheduled Task Instance Run Failure         | Includes: Periodically scheduled task instances, backfill task instances, and manual reruns of scheduled instances. Excludes: Manually run temporary instances, real-time sync task instances. | An alert event is generated when a scheduled task instance fails due to various reasons (code logic errors, timeout, system exceptions, etc.). If the scheduled task is configured with automatic retry on error, no alert events are generated during the automatic retry process; only one alert is generated upon final failure. |
+| Scheduled Task Instance Completion Time       | Includes: Periodically scheduled task instances, manually rerun scheduled task instances, etc. Excludes: Manually run temporary instances, backfill task instances.     | An alert event is generated when the completion time of a scheduled task exceeds the expected time point (does not finish running by the specified time).                                                  |
+| Scheduled Task Instance Scheduling Duration (Including Wait Time)  | Includes: Periodically scheduled task instances. Excludes: Manually run temporary instances, backfill task instances, manually rerun scheduled task instances, etc.     | An alert event is generated when the total duration from the planned time to the end time of a scheduled task instance exceeds the threshold. This includes the time the task instance waits for upstream tasks to complete.              |
+| Scheduled Task Run Time Delay         | Includes: Periodically scheduled task instances. Excludes: Manually run temporary instances, backfill task instances, manually rerun scheduled task instances, etc.     | An alert event is generated when the actual start time of a scheduled task instance (when it enters running state) is delayed beyond the threshold compared to the planned time.                                         |
+| Task Instance Execution Duration (Excluding Wait Time)   | All task instances. Includes periodically scheduled task instances, manually run temporary instances, backfill task instances, manually rerun scheduled task instances, etc.   | An alert event is generated when the pure execution time of the instance (excluding the time waiting for upstream completion) exceeds the threshold.                                                      |
+| Dynamic Table Refresh Timeout            | Dynamic Tables                                             | An alert event is generated when a dynamic table refresh operation exceeds the set timeout period.                                                                  |
+| Streaming SQL Task Execution Failure        | Streaming SQL (Continuous Job) tasks                                        | An alert event is generated when the running status of a streaming SQL task changes from "Running" to "Failed".                                                        |
+| Quality Rule Validation Failure           | Quality Rules + Target Table: Select tables configured with quality rules. When a rule validation fails on that table, an alert history is generated.                    | An alert event is generated when the execution result of a data quality validation rule is "Failed".                                                                |
+| Quality Rule Validation Timeout           | Quality Rules                                                           | An alert event is generated when the execution result of a data quality validation rule is "Timeout".                                                                |
+| Multi-Table Real-Time Sync Task Run Failure       | Multi-table real-time sync tasks                                                       | An alert event is generated when the status of a multi-table real-time sync task changes from "Running" to "Failed".                                                         |
+| Multi-Table Real-Time Sync Task Table Enters Blacklist      | Multi-table real-time sync tasks                                                       | An alert event is generated when a table in the task is added to the blacklist due to consecutive sync failures.                                                              |
+| Multi-Table Real-Time Sync Task Single Table Full Data Sync Exception | Multi-table real-time sync tasks                                                       | An alert event is generated when an exception occurs during the full data synchronization of a single table in a multi-table real-time sync task.                                                         |
+| Multi-Table Real-Time Sync Task Single Table Incremental Data Sync Exception | Multi-table real-time sync tasks                                                       | An alert event is generated when an exception occurs during the incremental data synchronization of a single table in a multi-table real-time sync task.                                                         |
+| Full & Incremental Integrated Sync Single Table Full Data Sync Exception  | Full & incremental integrated sync tasks                                                      | An alert event is generated when an exception occurs during the full data synchronization of a single table in a full & incremental integrated sync task.                                                        |
+| Full & Incremental Integrated Sync Single Table Incremental Data Sync Exception  | Full & incremental integrated sync tasks                                                      | An alert event is generated when an exception occurs during the incremental data synchronization of a single table in a full & incremental integrated sync task.                                                        |
+| Full & Incremental Integrated Sync Task Run Failure      | Full & incremental integrated sync tasks                                                      | An alert event is generated when the status of a full & incremental integrated sync task changes from "Running" to "Failed".                                                        |
+| Full & Incremental Integrated Sync Task Target Table Schema Change Failure | Full & incremental integrated sync tasks                                                      | An alert event is generated when automatic schema evolution of the target table encounters an error.                                                 |
+
+## Metric-Based Monitoring
+
+| Metric Name               | Target Objects        | Scope Description                                                         |
+| ------------------ | ----------- | ------------------------------------------------------------ |
+| Dynamic Table Refresh Failure            | Dynamic Tables         | Number of dynamic table refresh operation failures.                                                  |
+| Full & Incremental Integrated Sync Task Delay        | Full & incremental integrated real-time sync tasks | Time delay of data synchronization.                                                    |
+| Full & Incremental Integrated Sync Task Single Table Sync Failure    | Full & incremental integrated real-time sync tasks | Statistics on single table synchronization failure count.                                                   |
+| Multi-Table Real-Time Sync Task Delay         | Multi-table real-time sync tasks    | Overall delay of multi-table real-time synchronization.                                                  |
+| Multi-Table Real-Time Sync Task Job Failover | Multi-table real-time sync tasks    | Number of failover occurrences in multi-table sync tasks.                                               |
+| Multi-Table Real-Time Sync Task Read Position Delay     | Multi-table real-time sync tasks    | Delay of data read position relative to the source.                                               |
+| Multi-Table Real-Time Sync Task Source Database Read Delay  | Multi-table real-time sync tasks    | Difference between source database data generation rate and synchronization rate.                                           |
+| Multi-Table Real-Time Sync Task Data Sync Status Exception   | Multi-table real-time sync tasks    | Monitoring of abnormal conditions in data synchronization status.                                                |
+| Queued Jobs Count              | Single SQL Job     | Sampled every 5 seconds. Counts all SQL jobs whose status is "queued" at each sampling point.                               |
+| Average Job Queue Time           | Single SQL Job     | Sampled every 5 seconds. Calculates the TP90 job queue time within each 5-second window.                                    |
+| General-Purpose / Integration Vcluster Load      | VCluster        | At each sampling point, computes the ratio of compute resources currently processing tasks to the maximum compute resources supported by that vcluster size.                 |
+| Analytics Vcluster Load          | VCluster        | At each sampling point, computes the ratio of current job concurrency to the vcluster's maximum supported concurrency (calculated as max replicas x max concurrency per replica). |
+
+^