@alicloud/cms20190101 3.1.0 → 3.1.2

package/dist/client.js

@@ -15,13 +15,23 @@ var __setModuleDefault = (this && this.__setModuleDefault) || (Object.create ? (
 }) : function(o, v) {
     o["default"] = v;
 });
-var __importStar = (this && this.__importStar) || function (mod) {
-    if (mod && mod.__esModule) return mod;
-    var result = {};
-    if (mod != null) for (var k in mod) if (k !== "default" && Object.prototype.hasOwnProperty.call(mod, k)) __createBinding(result, mod, k);
-    __setModuleDefault(result, mod);
-    return result;
-};
+var __importStar = (this && this.__importStar) || (function () {
+    var ownKeys = function(o) {
+        ownKeys = Object.getOwnPropertyNames || function (o) {
+            var ar = [];
+            for (var k in o) if (Object.prototype.hasOwnProperty.call(o, k)) ar[ar.length] = k;
+            return ar;
+        };
+        return ownKeys(o);
+    };
+    return function (mod) {
+        if (mod && mod.__esModule) return mod;
+        var result = {};
+        if (mod != null) for (var k = ownKeys(mod), i = 0; i < k.length; i++) if (k[i] !== "default") __createBinding(result, mod, k[i]);
+        __setModuleDefault(result, mod);
+        return result;
+    };
+})();
 var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
@@ -18614,6 +18624,8 @@ class DescribeSiteMonitorAttributeResponseBodySiteMonitorsOptionJson extends $te
             expectValue: 'expect_value',
             failureRate: 'failure_rate',
             header: 'header',
+            hostBinding: 'host_binding',
+            hostBindingType: 'host_binding_type',
             httpMethod: 'http_method',
             ipNetwork: 'ip_network',
             isBase64Encode: 'isBase64Encode',
@@ -18633,6 +18645,7 @@ class DescribeSiteMonitorAttributeResponseBodySiteMonitorsOptionJson extends $te
             responseFormat: 'response_format',
             retryDelay: 'retry_delay',
             screenShot: 'screen_shot',
+            scrollEnd: 'scroll_end',
             strictMode: 'strict_mode',
             timeOut: 'time_out',
             trafficHijackElementBlacklist: 'traffic_hijack_element_blacklist',
@@ -18666,6 +18679,8 @@ class DescribeSiteMonitorAttributeResponseBodySiteMonitorsOptionJson extends $te
             expectValue: 'string',
             failureRate: 'number',
             header: 'string',
+            hostBinding: 'string',
+            hostBindingType: 'number',
             httpMethod: 'string',
             ipNetwork: 'string',
             isBase64Encode: 'string',
@@ -18685,6 +18700,7 @@ class DescribeSiteMonitorAttributeResponseBodySiteMonitorsOptionJson extends $te
             responseFormat: 'string',
             retryDelay: 'number',
             screenShot: 'boolean',
+            scrollEnd: 'boolean',
             strictMode: 'boolean',
             timeOut: 'number',
             trafficHijackElementBlacklist: DescribeSiteMonitorAttributeResponseBodySiteMonitorsOptionJsonTrafficHijackElementBlacklist,
@@ -21663,13 +21679,13 @@ class Client extends openapi_client_1.default {
         return await this.createHybridMonitorNamespaceWithOptions(request, runtime);
     }
     /**
-     * Creates a Logstore group for the metrics of Simple Log Service logs.
+     * Creates a Logstore group of Hybrid Cloud Monitoring.
      *
      * @remarks
-     * # Prerequisites
+     * ## [](#)Prerequisites
      * Simple Log Service is activated. A project and a Logstore are created in Simple Log Service. For more information, see [Getting Started](https://help.aliyun.com/document_detail/54604.html).
-     * # Description
-     * In this example, a Logstore group named `Logstore_test` is created. The region ID is `cn-hangzhou`. The project is `aliyun-project`. The Logstore is `Logstore-ECS`. The response shows that the Logstore group is created.
+     * ## [](#)Description
+     * This topic provides an example on how to create a Logstore group named `Logstore_test`. The region ID is `cn-hangzhou`. The project is `aliyun-project`. The Logstore is `Logstore-ECS`. The response shows that the Logstore group is created.
      *
      * @param request - CreateHybridMonitorSLSGroupRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -21704,13 +21720,13 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new CreateHybridMonitorSLSGroupResponse({}));
     }
     /**
-     * Creates a Logstore group for the metrics of Simple Log Service logs.
+     * Creates a Logstore group of Hybrid Cloud Monitoring.
      *
      * @remarks
-     * # Prerequisites
+     * ## [](#)Prerequisites
      * Simple Log Service is activated. A project and a Logstore are created in Simple Log Service. For more information, see [Getting Started](https://help.aliyun.com/document_detail/54604.html).
-     * # Description
-     * In this example, a Logstore group named `Logstore_test` is created. The region ID is `cn-hangzhou`. The project is `aliyun-project`. The Logstore is `Logstore-ECS`. The response shows that the Logstore group is created.
+     * ## [](#)Description
+     * This topic provides an example on how to create a Logstore group named `Logstore_test`. The region ID is `cn-hangzhou`. The project is `aliyun-project`. The Logstore is `Logstore-ECS`. The response shows that the Logstore group is created.
      *
      * @param request - CreateHybridMonitorSLSGroupRequest
      * @returns CreateHybridMonitorSLSGroupResponse
@@ -24507,7 +24523,7 @@ class Client extends openapi_client_1.default {
         return await this.describeEventRuleListWithOptions(request, runtime);
     }
     /**
-     * Queries the push channels of an event-triggered alert rule.
+     * Queries event-triggered alert rules.
      *
      * @remarks
      * This topic provides an example to show how to query the details of an event-triggered alert rule named `testRule`.
@@ -24539,7 +24555,7 @@ class Client extends openapi_client_1.default {
         return $tea.cast(await this.callApi(params, req, runtime), new DescribeEventRuleTargetListResponse({}));
     }
     /**
-     * Queries the push channels of an event-triggered alert rule.
+     * Queries event-triggered alert rules.
      *
      * @remarks
      * This topic provides an example to show how to query the details of an event-triggered alert rule named `testRule`.
@@ -29363,6 +29379,7 @@ class Client extends openapi_client_1.default {
      *
      * @remarks
      * This topic provides an example on how to create a threshold-triggered alert rule for the `cpu_total` metric of an Elastic Compute Service (ECS) instance whose ID is `i-uf6j91r34rnwawoo****`. The namespace of ECS metrics is `acs_ecs_dashboard`. The alert contact group of the alert rule is `ECS_Group`. The name of the alert rule is `test123`. The ID of the alert rule is `a151cd6023eacee2f0978e03863cc1697c89508****`. The statistical method for Critical-level alerts is `Average`. The comparison operator for Critical-level alerts is `GreaterThanOrEqualToThreshold`. The threshold for Critical-level alerts is `90`. The consecutive number of times for which the metric value meets the trigger condition before a Critical-level alert is triggered is `3`.
+     * >  Statistics verification was added on August 15, 2024. Only the statistical value of the corresponding metric can be set for the Statistics parameter. For more information about how to obtain the value of this parameter, see [Appendix 1: Metrics](https://www.alibabacloud.com/help/en/cms/support/appendix-1-metrics).
      *
      * @param tmpReq - PutResourceMetricRuleRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -29454,6 +29471,7 @@ class Client extends openapi_client_1.default {
      *
      * @remarks
      * This topic provides an example on how to create a threshold-triggered alert rule for the `cpu_total` metric of an Elastic Compute Service (ECS) instance whose ID is `i-uf6j91r34rnwawoo****`. The namespace of ECS metrics is `acs_ecs_dashboard`. The alert contact group of the alert rule is `ECS_Group`. The name of the alert rule is `test123`. The ID of the alert rule is `a151cd6023eacee2f0978e03863cc1697c89508****`. The statistical method for Critical-level alerts is `Average`. The comparison operator for Critical-level alerts is `GreaterThanOrEqualToThreshold`. The threshold for Critical-level alerts is `90`. The consecutive number of times for which the metric value meets the trigger condition before a Critical-level alert is triggered is `3`.
+     * >  Statistics verification was added on August 15, 2024. Only the statistical value of the corresponding metric can be set for the Statistics parameter. For more information about how to obtain the value of this parameter, see [Appendix 1: Metrics](https://www.alibabacloud.com/help/en/cms/support/appendix-1-metrics).
      *
      * @param request - PutResourceMetricRuleRequest
      * @returns PutResourceMetricRuleResponse
@@ -29467,6 +29485,7 @@ class Client extends openapi_client_1.default {
      *
      * @remarks
      * This topic provides an example on how to create a threshold-triggered alert rule for the `cpu_total` metric of an Elastic Compute Service (ECS) instance whose ID is `i-uf6j91r34rnwawoo****`. The namespace of ECS metrics is `acs_ecs_dashboard`. The alert contact group of the alert rule is `ECS_Group`. The name of the alert rule is `test123`. The ID of the alert rule is `a151cd6023eacee2f0978e03863cc1697c89508****`. The statistical method for Critical-level alerts is `Average`. The comparison operator for Critical-level alerts is `GreaterThanOrEqualToThreshold`. The threshold for Critical-level alerts is `90`. The consecutive number of times for which the metric value meets the trigger condition before a Critical-level alert is triggered is `3`.
+     * >  Statistics verification was added on August 15, 2024. Only the statistical value of the corresponding metric can be set for the Statistics parameter. For more information about how to obtain the value of this parameter, see [Appendix 1: Metrics](https://www.alibabacloud.com/help/en/cms/support/appendix-1-metrics).
      *
      * @param request - PutResourceMetricRulesRequest
      * @param runtime - runtime options for this request RuntimeOptions
@@ -29499,6 +29518,7 @@ class Client extends openapi_client_1.default {
      *
      * @remarks
      * This topic provides an example on how to create a threshold-triggered alert rule for the `cpu_total` metric of an Elastic Compute Service (ECS) instance whose ID is `i-uf6j91r34rnwawoo****`. The namespace of ECS metrics is `acs_ecs_dashboard`. The alert contact group of the alert rule is `ECS_Group`. The name of the alert rule is `test123`. The ID of the alert rule is `a151cd6023eacee2f0978e03863cc1697c89508****`. The statistical method for Critical-level alerts is `Average`. The comparison operator for Critical-level alerts is `GreaterThanOrEqualToThreshold`. The threshold for Critical-level alerts is `90`. The consecutive number of times for which the metric value meets the trigger condition before a Critical-level alert is triggered is `3`.
+     * >  Statistics verification was added on August 15, 2024. Only the statistical value of the corresponding metric can be set for the Statistics parameter. For more information about how to obtain the value of this parameter, see [Appendix 1: Metrics](https://www.alibabacloud.com/help/en/cms/support/appendix-1-metrics).
      *
      * @param request - PutResourceMetricRulesRequest
      * @returns PutResourceMetricRulesResponse