@clickzetta/cz-cli-darwin-arm64 0.5.16 → 0.5.17

package/bin/skills/lakehouse-doc-en/references/langchain-plug-installation.md

@@ -23,7 +23,7 @@ pip install -e ".[dev]"
 ## Dependency Requirements
 
 ### Python Version
-- Python 3.9 or higher
+- Python 3.10 or higher
 
 ### Core Dependencies
 The following dependencies are installed automatically with the package:

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

@@ -10,29 +10,28 @@ In Singdata Lakehouse, every account has a unique identifier used to distinguish
 
 The account name is your unique identifier within Singdata Lakehouse and cannot be changed once generated. You can find your account name in the prompt shown after registration or on the Management Center home page.
 
-:-: ![](.topwrite/assets/image\_1739329828430.png =780)
+
 
 ^
 
-:-: ![](.topwrite/assets/image\_1739329908616.png =783)
 
 ### Login URL
 
 In Singdata products, each account has its own dedicated login URL. The login URL follows the format: `<your_account_name>.accounts.singdata.com`.
 
-:-: ![](.topwrite/assets/image\_1739329970639.png =799)
+
 
 ### Service Instance Name
 
 Singdata Lakehouse is a multi-cloud big data platform that supports creating service instances across different regions of multiple cloud providers. Each service instance provisioned generates a unique identifier within that region and carves out a logical area within the infrastructure resources to provide Lakehouse services. The service instance name (`instance_name`) is the unique identifier for a service instance. It is automatically generated when you provision the instance and consists of an 8-character random string. You can find your service instance name in the service instance URL or on the right side of the service instance home page.
 
-:-: ![](.topwrite/assets/image\_1740540520113.png =807)
+
 
 ### Account Registration Phone Number
 
 The account registration phone number is the phone number you provided when creating the account and adding the first user. The initial account phone number is the same as the phone number of the first user under the account. Account administrators can change the registration phone number in the Management Center. Keep your registration phone number safe — in Singdata products, each registration phone number corresponds to only one account, and it is the sole credential for account recovery.
 
-:-: ![](.topwrite/assets/image\_1739330026163.png =806)
+
 
 ^ ^
 
@@ -127,7 +126,6 @@ Example:
 
 In some SQL clients (such as DBeaver), JDBC drivers, or Python/Java library configuration files, you need to configure connection parameters. For example, when configuring the DBeaver driver:
 
-:-: ![](.topwrite/assets/image\_1740549280083.png =361)
 
 In the JDBC connection string, use the service instance name (`instance_name`), for example:
 
@@ -161,16 +159,13 @@ When configuring the Python SDK, use the service instance name (`instance_name`)
 
 When you log in to Singdata with a user that has the account administrator role, you can manage your account in the Management Center. On the "Account Home" page, you can view basic account information and the account login URL. You can also click the "Modify" button next to the registration phone number to change it. Note that on the "Account Center" page you will see two separate phone number fields: "Registration Phone" under "Account Info" — this is the phone number bound to the account and can be used to retrieve the account name; and "Registration Phone" under "User Info" — this is the phone number bound to the currently logged-in user and can be used for MFA verification, username recovery, and password recovery for that user. Be sure to distinguish between the two.
 
-![](.topwrite/assets/image\_1740550879753.png)
 
 
 ### Changing the Account Registration Phone Number
 
 To change the account registration phone number, you must be logged in as a user with the account administrator (`account_admin`) role. In the "Account Center", click the modify button next to "Registration Phone" under "Account Info". After verifying the old phone number, you can enter and save the new phone number.
 
-:-: ![](.topwrite/assets/image\_1740551806201.png =765)
 
-:-: ![](.topwrite/assets/image\_1740551835302.png =438)
 
 ### Changing the Account Name or Service Instance Name
 

package/bin/skills/lakehouse-doc-en/references/medallion-lakehouse-from-scratch.md

@@ -716,5 +716,6 @@ With 20/22 validations passing (the 2 warnings are source data quality issues, n
 - Spark SQL syntax migration: [Spark SQL Syntax Migration Guide](migration-spark-sql.md)
 - Volume usage guide: [Volume Usage Guide](zettapark-volume-guide.md)
 - Data type compatibility: [Data Type Compatibility Reference](migration-sql-compatibility.md)
-- Custom functions: [SQL Function](create-sql-function.md) · [External Function](om-external-function.md)
+- Custom functions: [SQL Function](create-sql-function.md) · [External Function](create_external_function.md)
+- Spark Connector: [Spark Connector Usage](spark-connector-use.md)
 - Spark Connector: [Using Spark Connector](spark-connector-use.md)

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

@@ -1,45 +1,82 @@
-# Metrics and Answer Builder Configuration
+# Metrics and Answer Builder
 
-## Constructing Metrics: 
+When AI answers questions involving calculation logic, without pre-defined formulas, the model may generate different SQL each time, resulting in inconsistent metric definitions. Metrics and Answer Builder solve exactly this problem — they lock in the calculation logic so the model can reference it directly instead of inferring it on the fly.
 
-In **Left Navigation Bar: Data** -> **Metrics**, you can click "+ **New Metric**" to add new metrics. Metrics can be generated using aggregation or custom code methods.
+**When to use Metrics vs Answer Builder**?
+
+| Scenario                                                      | Recommended    | Reason                                                                  |
+| ------------------------------------------------------------- | -------------- | ----------------------------------------------------------------------- |
+| Single-table aggregation, e.g., SUM, AVG, COUNT               | Metrics        | Simple to configure; supports aliases and period-over-period comparison |
+| Requires multi-table JOIN                                     | Answer Builder | Metrics do not support multiple tables; a full SQL template is needed   |
+| Has complex filter conditions (e.g., count only valid orders) | Answer Builder | Filter logic goes in the WHERE clause of the SQL template               |
+| Detail query (non-aggregate, returns row-level data)          | Answer Builder | Metrics only support aggregate calculations                             |
+
+***
+
+## Creating Metrics
+
+In the left navigation bar, go to **Data** -> **Metrics** and click + **New Metric**. Both aggregation and custom code methods are supported.
 
 ![](.topwrite/assets/b.jpg =558)
 
 ^
 
-## Creating Answer Builder: 
+A single metric template can define multiple metrics, and each metric can have multiple aliases, allowing the model to understand different names for the same concept (e.g., "average order value" and "spend per customer").
+
+> ⚠️ **Note**: In the Default Domain, duplicate metric names and aliases are allowed. In other user-created Domains, metric names (including aliases) must be unique.
+
+### Analysis Method
 
-The Answer Builder is used to define metrics with complex calculation logic and to provide SQL templates for detailed queries. In **Left Navigation Bar: Data** -> **Answer Builder**, you can click "+ **New Answer Builder**" and follow the steps to fill in the code.
+Each metric must specify an analysis method, which affects the period-over-period calculation logic:
 
-* SQL Template for Answer Builder: `${dims}` and `${filters}` are fixed syntax representing dimension and filter condition variables. The selectable columns for these variables are defined in the **Filters** and **Dims** sections below the template.
+| Analysis Method     | Period-over-Period Algorithm                                               | Applicable Scenario                                     |
+| ------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------- |
+| Additive metric     | (Current period value - Previous period value) / \|Previous period value\| | Absolute numeric metrics, e.g., revenue, order count    |
+| Proportional metric | Current period value - Previous period value                               | Percentage metrics, e.g., market share, conversion rate |
 
-```SQL
+Example: If market share is 30% this year and 20% last year, the proportional method gives a year-over-year result of +10% (not +50%).
+
+***
+
+## Creating an Answer Builder
+
+In the left navigation bar, go to **Data** -> **Answer Builder** and click + **New Answer Builder**.
+
+The core of an Answer Builder is a SQL template. `${dims}` and `${filters}` are fixed placeholders representing dimensions and filter conditions respectively; they are dynamically filled in by the AI when answering questions.
+
+```sql
 SELECT  
   ${dims},
   sum(op.payment_value) as total_sales_bz,
   avg(op.payment_value) as avg_sales_bz
 FROM datagpt_ws.public.v_gpt_orders AS o  
 LEFT JOIN datagpt_ws.public.v_gpt_order_items AS oi 
-    ON o.order_id = oi.order_id  LEFT JOIN datagpt_ws.public.v_gpt_products AS p
-    ON oi.product_id = p.product_id  LEFT JOIN datagpt_ws.public.v_gpt_customers AS c
-    ON o.customer_id = c.customer_id  LEFT JOIN datagpt_ws.public.v_gpt_payments AS op
-    ON o.order_id = op.order_id  LEFT JOIN datagpt_ws.public.v_gpt_sellers AS os ON oi.seller_id = os.seller_id
-where ${filters}
-group by ${dims}
+    ON o.order_id = oi.order_id
+LEFT JOIN datagpt_ws.public.v_gpt_products AS p
+    ON oi.product_id = p.product_id
+LEFT JOIN datagpt_ws.public.v_gpt_customers AS c
+    ON o.customer_id = c.customer_id
+LEFT JOIN datagpt_ws.public.v_gpt_payments AS op
+    ON o.order_id = op.order_id
+LEFT JOIN datagpt_ws.public.v_gpt_sellers AS os
+    ON oi.seller_id = os.seller_id
+WHERE ${filters}
+GROUP BY ${dims}
 ```
 
-* **Filters and Dims Variable Definition**: Note: Columns not appearing in Filter and Dims here will not be used as filter conditions and dimensions for the issue. (This is related to the **Usage** field configuration of the table columns in **Data** -> **Tables**: columns configured as FILTER and DIM in the **Usage** field will be selected by default here, and the final configuration will be based on this page)![](.topwrite/assets/20250219-115158.jpeg =736)
+### Configuring Filters and Dims
 
-### Configure Metric Aliases and Analysis Methods:
+Below the SQL template, you need to define which columns can be used as filter conditions (Filters) and dimensions (Dims). Columns not selected here will not be used as filter conditions or dimensions for questions.
 
-In a metric template, multiple metrics can be defined. Each metric can specify multiple aliases.
+:-: ![](/.topwrite/assets/image_1780906414361.png =686)
 
-> ⚠️ **Note**: In the system Default Domain, duplicate metrics and aliases are allowed; in other user-created Domains, duplicate metric names (including aliases) are not allowed.
+> 💡 **Tip**: In the column configuration under **Data** -> **Tables**, setting a column's **Usage** field to FILTER or DIM will cause it to be selected by default here. The final configuration is governed by the settings on the Answer Builder page.
 
-### **Analysis Methods**:
+## Related Documentation
 
-* **Additive Metrics**: The algorithm for period-over-period comparison is: (current period value - previous period value) / absolute value of previous period value.
-* **Proportional Metrics**: The algorithm for period-over-period comparison is: current period value - previous period value. For example, if this year's market share is 30% and last year's was 20%, then the year-over-year growth is 10%.
+* [Answer Accuracy Improvement](answer-accuracy-improve.md) — The role of Metrics and Answer Builder in the overall accuracy improvement strategy
+* [Data Source Management](datagpt_data_source.md) — Configure the data table sources that metrics depend on
+* [Row-Level Permissions](row_level_permission.md) — Control the data range accessible to different users
+* [Conversational Data Analytics (Analytics Agent)](datagpt_introduction.md) — Return to feature overview
 
-![](.topwrite/assets/20250219-115256.jpeg)
+^

package/bin/skills/lakehouse-doc-en/references/migrate-spark-data-engineering-best-practices-to-lakehouse.md

@@ -188,7 +188,7 @@ Set the value for each parameter:
 
 :-: ![](.topwrite/assets/image_1737534633567.png =562)
 
-For how to obtain parameter values, please refer to [this article](https://uat-doc.singdata.com/JDBC-Driver).
+For how to obtain parameter values, please refer to [this article](jdbc-driver.md).
 
 ^
 

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

@@ -1,4 +1,4 @@
-# Introduction to MindsDB
+# Connecting MindsDB to Singdata Lakehouse
 
 > ⚠️ **Note:** If your goal with MindsDB is to call AI models on your data, Singdata Lakehouse provides native AI capabilities — no need to deploy or maintain a MindsDB service:
 >

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

@@ -6,55 +6,57 @@ The monitoring and alerting system is a powerful feature set that allows users t
 
 ## 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.                                          |
+| 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)
+![](/.topwrite/assets/image_1780674124352.png =715)
 
 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    |
+| 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   |
+| 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.                       |                                                                                                                                                                      |
+![](/.topwrite/assets/image_1780674143790.png =677)
+
+^
+
+| 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
 
@@ -62,7 +64,9 @@ Trigger conditions consist of monitoring items, metric calculation methods, thre
 
 **Metric-Based Monitoring Configuration**
 
-![](.topwrite/assets/226957dd01/0d872f1cb6d11f16e4a48c9a6466ac9d43eb8606.png =548)
+\*\*\*\*![](/.topwrite/assets/image_1780674178425.png =577)
+
+^
 
 For metric monitoring, after defining the calculation method and threshold, two trigger methods are supported.
 
@@ -72,7 +76,7 @@ Check Interval: Users define that when the threshold is touched a cumulative N t
 
 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.
 
@@ -99,48 +103,49 @@ The alert event list displays all alert information generated after monitoring r
 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)
+
+![](/.topwrite/assets/image_1780674232157.png =701)
 
 #### 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 |
+| 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/image_1780674263546.png =700)
 
-![](.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  |                                                                                                                          |
+![](/.topwrite/assets/image_1780674286569.png =677)
+
+| 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
 
@@ -150,19 +155,19 @@ Configuration management allows users to configure personal information and Webh
 
 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
 
@@ -174,4 +179,4 @@ For monitoring alerts on task instance run failures, after the Operations Center
 
 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

@@ -4,41 +4,41 @@ This document describes the specific definitions and scope of "Event" and "Metri
 
 ## 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.                                                 |
+| 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). |
+| 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). |
 
 ^