public interface AsyncClient
extends com.aliyun.core.utils.SdkAutoCloseable
static DefaultAsyncClientBuilder builder()
static AsyncClient create()
CompletableFuture<AddTagsResponse> addTags(AddTagsRequest request)
This topic provides an example on how to add a tag to an application group whose ID is 7301****. In this example, the key of the tag is key1 and the value of the tag is value1.
request - the request parameters of AddTags AddTagsRequestCompletableFuture<ApplyMetricRuleTemplateResponse> applyMetricRuleTemplate(ApplyMetricRuleTemplateRequest request)
In this example, the 700**** alert template is applied to the 123456 application group. For the generated alert rule, the ID is applyTemplate8ab74c6b-9f27-47ab-8841-de01dc08****, and the name is test123.
request - the request parameters of ApplyMetricRuleTemplate ApplyMetricRuleTemplateRequestCompletableFuture<BatchCreateInstantSiteMonitorResponse> batchCreateInstantSiteMonitor(BatchCreateInstantSiteMonitorRequest request)
This topic provides an example on how to create a site monitoring task named HangZhou_ECS1. The URL that is monitored by the task is https://www.aliyun.com and the type of the task is HTTP. The returned result shows that the site monitoring task is created. The name of the site monitoring task is HangZhou_ECS1 and the task ID is 679fbe4f-b80b-4706-91b2-5427b43e****.
request - the request parameters of BatchCreateInstantSiteMonitor BatchCreateInstantSiteMonitorRequestCompletableFuture<BatchExportResponse> batchExport(BatchExportRequest request)
The Cursor information is returned by calling the Cursor operation.
This topic provides an example on how to export the monitoring data of the cpu_idle metric for Elastic Compute Service (ECS). The namespace of ECS is acs_ecs_dashboard. The Cursor information is specified. A maximum of 1,000 data entries can be returned in each response.
request - the request parameters of BatchExport BatchExportRequestCompletableFuture<CreateDynamicTagGroupResponse> createDynamicTagGroup(CreateDynamicTagGroupRequest request)
This operation is available for Elastic Compute Service (ECS), ApsaraDB RDS, and Server Load Balancer (SLB).
This topic provides an example to show how to create an application group for resources whose tag key is ecs_instance. In this example, the alert contact group of the application group is ECS_Group.
request - the request parameters of CreateDynamicTagGroup CreateDynamicTagGroupRequestCompletableFuture<CreateGroupMetricRulesResponse> createGroupMetricRules(CreateGroupMetricRulesRequest request)
This topic provides an example to show how to create an alert rule for the cpu_total metric of Elastic Compute Service (ECS) in the 123456 application group. The ID of the alert rule is 456789. The name of the alert rule is ECS_Rule1. The alert level is Critical. The statistical method is Average. The comparison operator is GreaterThanOrEqualToThreshold. The alert threshold is 90. The number of alert retries is 3. The response shows that the alert rule named ECS_Rule1 is created.
request - the request parameters of CreateGroupMetricRules CreateGroupMetricRulesRequestCompletableFuture<CreateGroupMonitoringAgentProcessResponse> createGroupMonitoringAgentProcess(CreateGroupMonitoringAgentProcessRequest request)
request - the request parameters of CreateGroupMonitoringAgentProcess CreateGroupMonitoringAgentProcessRequestCompletableFuture<CreateHostAvailabilityResponse> createHostAvailability(CreateHostAvailabilityRequest request)
This topic provides an example on how to create an availability monitoring task named task1 in an application group named 123456. The TaskType parameter of the task is set to HTTP. After you start the task, the system sends alerts by using the specified email address and DingTalk chatbot.
request - the request parameters of CreateHostAvailability CreateHostAvailabilityRequestCompletableFuture<CreateHybridMonitorNamespaceResponse> createHybridMonitorNamespace(CreateHybridMonitorNamespaceRequest request)
Hybrid Cloud Monitoring is activated. For more information, see Activate Hybrid Cloud Monitoring.
This topic provides an example on how to create a namespace named aliyun. In this example, the data retention period of the namespace is set to cms.s1.3xlarge. The returned result indicates that the namespace is created.
request - the request parameters of CreateHybridMonitorNamespace CreateHybridMonitorNamespaceRequestCompletableFuture<CreateHybridMonitorSLSGroupResponse> createHybridMonitorSLSGroup(CreateHybridMonitorSLSGroupRequest request)
Simple Log Service is activated. A project and a Logstore are created in Simple Log Service. For more information, see Getting Started.
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.
request - the request parameters of CreateHybridMonitorSLSGroup CreateHybridMonitorSLSGroupRequestCompletableFuture<CreateHybridMonitorTaskResponse> createHybridMonitorTask(CreateHybridMonitorTaskRequest request)
This topic provides an example on how to create a metric import task named aliyun_task for Elastic Compute Service (ECS). The task imports the cpu_total metric to the aliyun namespace. The response shows that the metric import task is created.
request - the request parameters of CreateHybridMonitorTask CreateHybridMonitorTaskRequestCompletableFuture<CreateInstantSiteMonitorResponse> createInstantSiteMonitor(CreateInstantSiteMonitorRequest request)
You can create an instant test task only by using the Alibaba Cloud account that you used to enable Network Analysis and Monitoring.
This topic provides an example to show how to create an instant test task. The name of the task is task1. The tested address is http://www.aliyun.com. The test type is HTTP. The number of detection points is 1.
request - the request parameters of CreateInstantSiteMonitor CreateInstantSiteMonitorRequestCompletableFuture<CreateMetricRuleBlackListResponse> createMetricRuleBlackList(CreateMetricRuleBlackListRequest request)
request - the request parameters of CreateMetricRuleBlackList CreateMetricRuleBlackListRequestCompletableFuture<CreateMetricRuleResourcesResponse> createMetricRuleResources(CreateMetricRuleResourcesRequest request)
request - the request parameters of CreateMetricRuleResources CreateMetricRuleResourcesRequestCompletableFuture<CreateMetricRuleTemplateResponse> createMetricRuleTemplate(CreateMetricRuleTemplateRequest request)
request - the request parameters of CreateMetricRuleTemplate CreateMetricRuleTemplateRequestCompletableFuture<CreateMonitorAgentProcessResponse> createMonitorAgentProcess(CreateMonitorAgentProcessRequest request)
request - the request parameters of CreateMonitorAgentProcess CreateMonitorAgentProcessRequestCompletableFuture<CreateMonitorGroupResponse> createMonitorGroup(CreateMonitorGroupRequest request)
In this example, an application group named ECS_Group is created.
request - the request parameters of CreateMonitorGroup CreateMonitorGroupRequestCompletableFuture<CreateMonitorGroupByResourceGroupIdResponse> createMonitorGroupByResourceGroupId(CreateMonitorGroupByResourceGroupIdRequest request)
This topic provides an example on how to create an application group by using the resource group CloudMonitor and the alert contact group ECS_Group. The region ID of the resource group is cn-hangzhou.
request - the request parameters of CreateMonitorGroupByResourceGroupId CreateMonitorGroupByResourceGroupIdRequestCompletableFuture<CreateMonitorGroupInstancesResponse> createMonitorGroupInstances(CreateMonitorGroupInstancesRequest request)
You can add a maximum of 1,000 instances to an application group at a time. You can add a maximum of 3,000 instances of an Alibaba Cloud service to an application group. The total number of instances that you can add to an application group is unlimited.
In this example, an Elastic Compute Service (ECS) instance in the China (Hangzhou) region is added to the 3607**** application group. The instance ID is i-2ze26xj5wwy12**** and the instance name is test-instance-ecs.
request - the request parameters of CreateMonitorGroupInstances CreateMonitorGroupInstancesRequestCompletableFuture<CreateMonitorGroupNotifyPolicyResponse> createMonitorGroupNotifyPolicy(CreateMonitorGroupNotifyPolicyRequest request)
If the policy is valid, no alert notifications are sent for the application group.
This topic describes how to create a PauseNotify policy to pause alert notifications for the 7301**** application group. The StartTime parameter is set to 1622949300000 and the EndTime parameter is set to 1623208500000. This indicates that the policy is valid from 2021-06-06 11:15:00 UTC+8 to 2021-06-09 11:15:00 UTC+8.
request - the request parameters of CreateMonitorGroupNotifyPolicy CreateMonitorGroupNotifyPolicyRequestCompletableFuture<CreateMonitoringAgentProcessResponse> createMonitoringAgentProcess(CreateMonitoringAgentProcessRequest request)
request - the request parameters of CreateMonitoringAgentProcess CreateMonitoringAgentProcessRequestCompletableFuture<CreateSiteMonitorResponse> createSiteMonitor(CreateSiteMonitorRequest request)
This topic provides an example on how to create a site monitoring task named HanZhou_ECS1. The URL that is monitored by the task is https://www.aliyun.com and the type of the task is HTTPS.
request - the request parameters of CreateSiteMonitor CreateSiteMonitorRequestCompletableFuture<CursorResponse> cursor(CursorRequest request)
Hybrid Cloud Monitoring is activated. For more information, see Activate Hybrid Cloud Monitoring.
You can call this operation to obtain the Cursor information and then call the BatchExport operation to export the monitoring data.
This topic provides an example on how to define the monitoring data of a specified metric for a specified cloud service. In this example, the namespace of the cloud service is set to acs_ecs_dashboard, the metric is set to cpu_idle, the start time is set to 1641627000000, and the end time is set to 1641645000000. The number of idle CPU cores on your Elastic Compute Service (ECS) instances is measured every 60 seconds from 15:30:00, January 8, 2022 to 20:30:00, January 8, 2022. The Cursor information is returned.
request - the request parameters of Cursor CursorRequestCompletableFuture<DeleteContactResponse> deleteContact(DeleteContactRequest request)
request - the request parameters of DeleteContact DeleteContactRequestCompletableFuture<DeleteContactGroupResponse> deleteContactGroup(DeleteContactGroupRequest request)
request - the request parameters of DeleteContactGroup DeleteContactGroupRequestCompletableFuture<DeleteCustomMetricResponse> deleteCustomMetric(DeleteCustomMetricRequest request)
request - the request parameters of DeleteCustomMetric DeleteCustomMetricRequestCompletableFuture<DeleteDynamicTagGroupResponse> deleteDynamicTagGroup(DeleteDynamicTagGroupRequest request)
request - the request parameters of DeleteDynamicTagGroup DeleteDynamicTagGroupRequestCompletableFuture<DeleteEventRuleTargetsResponse> deleteEventRuleTargets(DeleteEventRuleTargetsRequest request)
request - the request parameters of DeleteEventRuleTargets DeleteEventRuleTargetsRequestCompletableFuture<DeleteEventRulesResponse> deleteEventRules(DeleteEventRulesRequest request)
request - the request parameters of DeleteEventRules DeleteEventRulesRequestCompletableFuture<DeleteExporterOutputResponse> deleteExporterOutput(DeleteExporterOutputRequest request)
request - the request parameters of DeleteExporterOutput DeleteExporterOutputRequestCompletableFuture<DeleteExporterRuleResponse> deleteExporterRule(DeleteExporterRuleRequest request)
request - the request parameters of DeleteExporterRule DeleteExporterRuleRequestCompletableFuture<DeleteGroupMonitoringAgentProcessResponse> deleteGroupMonitoringAgentProcess(DeleteGroupMonitoringAgentProcessRequest request)
request - the request parameters of DeleteGroupMonitoringAgentProcess DeleteGroupMonitoringAgentProcessRequestCompletableFuture<DeleteHostAvailabilityResponse> deleteHostAvailability(DeleteHostAvailabilityRequest request)
request - the request parameters of DeleteHostAvailability DeleteHostAvailabilityRequestCompletableFuture<DeleteHybridMonitorNamespaceResponse> deleteHybridMonitorNamespace(DeleteHybridMonitorNamespaceRequest request)
If a metric import task is created for metrics in a namespace, you cannot delete the namespace unless you delete the task first. This topic provides an example on how to delete a namespace named
aliyun. The response shows that the namespace is deleted.
request - the request parameters of DeleteHybridMonitorNamespace DeleteHybridMonitorNamespaceRequestCompletableFuture<DeleteHybridMonitorSLSGroupResponse> deleteHybridMonitorSLSGroup(DeleteHybridMonitorSLSGroupRequest request)
This topic provides an example on how to delete a Logstore group named Logstore_test. The response shows that the Logstore group is deleted.
request - the request parameters of DeleteHybridMonitorSLSGroup DeleteHybridMonitorSLSGroupRequestCompletableFuture<DeleteHybridMonitorTaskResponse> deleteHybridMonitorTask(DeleteHybridMonitorTaskRequest request)
This topic provides an example on how to delete a metric import task whose ID is 36****. The returned result indicates that the metric import task is deleted.
request - the request parameters of DeleteHybridMonitorTask DeleteHybridMonitorTaskRequestCompletableFuture<DeleteLogMonitorResponse> deleteLogMonitor(DeleteLogMonitorRequest request)
request - the request parameters of DeleteLogMonitor DeleteLogMonitorRequestCompletableFuture<DeleteMetricRuleBlackListResponse> deleteMetricRuleBlackList(DeleteMetricRuleBlackListRequest request)
request - the request parameters of DeleteMetricRuleBlackList DeleteMetricRuleBlackListRequestCompletableFuture<DeleteMetricRuleResourcesResponse> deleteMetricRuleResources(DeleteMetricRuleResourcesRequest request)
request - the request parameters of DeleteMetricRuleResources DeleteMetricRuleResourcesRequestCompletableFuture<DeleteMetricRuleTargetsResponse> deleteMetricRuleTargets(DeleteMetricRuleTargetsRequest request)
request - the request parameters of DeleteMetricRuleTargets DeleteMetricRuleTargetsRequestCompletableFuture<DeleteMetricRuleTemplateResponse> deleteMetricRuleTemplate(DeleteMetricRuleTemplateRequest request)
request - the request parameters of DeleteMetricRuleTemplate DeleteMetricRuleTemplateRequestCompletableFuture<DeleteMetricRulesResponse> deleteMetricRules(DeleteMetricRulesRequest request)
request - the request parameters of DeleteMetricRules DeleteMetricRulesRequestCompletableFuture<DeleteMonitorGroupResponse> deleteMonitorGroup(DeleteMonitorGroupRequest request)
request - the request parameters of DeleteMonitorGroup DeleteMonitorGroupRequestCompletableFuture<DeleteMonitorGroupDynamicRuleResponse> deleteMonitorGroupDynamicRule(DeleteMonitorGroupDynamicRuleRequest request)
request - the request parameters of DeleteMonitorGroupDynamicRule DeleteMonitorGroupDynamicRuleRequestCompletableFuture<DeleteMonitorGroupInstancesResponse> deleteMonitorGroupInstances(DeleteMonitorGroupInstancesRequest request)
request - the request parameters of DeleteMonitorGroupInstances DeleteMonitorGroupInstancesRequestCompletableFuture<DeleteMonitorGroupNotifyPolicyResponse> deleteMonitorGroupNotifyPolicy(DeleteMonitorGroupNotifyPolicyRequest request)
request - the request parameters of DeleteMonitorGroupNotifyPolicy DeleteMonitorGroupNotifyPolicyRequestCompletableFuture<DeleteMonitoringAgentProcessResponse> deleteMonitoringAgentProcess(DeleteMonitoringAgentProcessRequest request)
request - the request parameters of DeleteMonitoringAgentProcess DeleteMonitoringAgentProcessRequestCompletableFuture<DeleteSiteMonitorsResponse> deleteSiteMonitors(DeleteSiteMonitorsRequest request)
request - the request parameters of DeleteSiteMonitors DeleteSiteMonitorsRequestCompletableFuture<DescribeActiveMetricRuleListResponse> describeActiveMetricRuleList(DescribeActiveMetricRuleListRequest request)
request - the request parameters of DescribeActiveMetricRuleList DescribeActiveMetricRuleListRequest@Deprecated CompletableFuture<DescribeAlertHistoryListResponse> describeAlertHistoryList(DescribeAlertHistoryListRequest request)
request - the request parameters of DescribeAlertHistoryList DescribeAlertHistoryListRequestCompletableFuture<DescribeAlertLogCountResponse> describeAlertLogCount(DescribeAlertLogCountRequest request)
Queries the statistics of alert logs.
This topic provides an example on how to query the statistics of alert logs for Elastic Compute Service (ECS) based on the product dimension.
request - the request parameters of DescribeAlertLogCount DescribeAlertLogCountRequestCompletableFuture<DescribeAlertLogHistogramResponse> describeAlertLogHistogram(DescribeAlertLogHistogramRequest request)
This topic provides an example on how to query the number of alert logs for Elastic Compute Service (ECS) based on the product dimension.
request - the request parameters of DescribeAlertLogHistogram DescribeAlertLogHistogramRequestCompletableFuture<DescribeAlertLogListResponse> describeAlertLogList(DescribeAlertLogListRequest request)
You can call the operation to query only the alert logs within the last year.
This topic provides an example to show how to query the alert logs of Elastic Compute Service (ECS) based on the product dimension.
request - the request parameters of DescribeAlertLogList DescribeAlertLogListRequestCompletableFuture<DescribeAlertingMetricRuleResourcesResponse> describeAlertingMetricRuleResources(DescribeAlertingMetricRuleResourcesRequest request)
request - the request parameters of DescribeAlertingMetricRuleResources DescribeAlertingMetricRuleResourcesRequestCompletableFuture<DescribeContactGroupListResponse> describeContactGroupList(DescribeContactGroupListRequest request)
request - the request parameters of DescribeContactGroupList DescribeContactGroupListRequestCompletableFuture<DescribeContactListResponse> describeContactList(DescribeContactListRequest request)
request - the request parameters of DescribeContactList DescribeContactListRequestCompletableFuture<DescribeContactListByContactGroupResponse> describeContactListByContactGroup(DescribeContactListByContactGroupRequest request)
request - the request parameters of DescribeContactListByContactGroup DescribeContactListByContactGroupRequestCompletableFuture<DescribeCustomEventAttributeResponse> describeCustomEventAttribute(DescribeCustomEventAttributeRequest request)
request - the request parameters of DescribeCustomEventAttribute DescribeCustomEventAttributeRequestCompletableFuture<DescribeCustomEventCountResponse> describeCustomEventCount(DescribeCustomEventCountRequest request)
This operation queries the number of times that a custom event occurred for each service.
request - the request parameters of DescribeCustomEventCount DescribeCustomEventCountRequestCompletableFuture<DescribeCustomEventHistogramResponse> describeCustomEventHistogram(DescribeCustomEventHistogramRequest request)
request - the request parameters of DescribeCustomEventHistogram DescribeCustomEventHistogramRequestCompletableFuture<DescribeCustomMetricListResponse> describeCustomMetricList(DescribeCustomMetricListRequest request)
You can call the DescribeMetricList operation to query the metrics of cloud services. For more information, see DescribeMetricList.
request - the request parameters of DescribeCustomMetricList DescribeCustomMetricListRequestCompletableFuture<DescribeDynamicTagRuleListResponse> describeDynamicTagRuleList(DescribeDynamicTagRuleListRequest request)
This topic provides an example to show how to query tag rules that are related to tagkey1. The sample responses indicate that two tag rules are found. The rule IDs are 1536df65-a719-429d-8813-73cc40d7**** and 56e8cebb-b3d7-4a91-9880-78a8c84f****.
request - the request parameters of DescribeDynamicTagRuleList DescribeDynamicTagRuleListRequestCompletableFuture<DescribeEventRuleAttributeResponse> describeEventRuleAttribute(DescribeEventRuleAttributeRequest request)
This topic provides an example to show how to query the details of an event-triggered alert rule named testRule.
request - the request parameters of DescribeEventRuleAttribute DescribeEventRuleAttributeRequestCompletableFuture<DescribeEventRuleListResponse> describeEventRuleList(DescribeEventRuleListRequest request)
request - the request parameters of DescribeEventRuleList DescribeEventRuleListRequestCompletableFuture<DescribeEventRuleTargetListResponse> describeEventRuleTargetList(DescribeEventRuleTargetListRequest request)
This topic provides an example to show how to query the details of an event-triggered alert rule named testRule.
request - the request parameters of DescribeEventRuleTargetList DescribeEventRuleTargetListRequestCompletableFuture<DescribeExporterOutputListResponse> describeExporterOutputList(DescribeExporterOutputListRequest request)
request - the request parameters of DescribeExporterOutputList DescribeExporterOutputListRequestCompletableFuture<DescribeExporterRuleListResponse> describeExporterRuleList(DescribeExporterRuleListRequest request)
request - the request parameters of DescribeExporterRuleList DescribeExporterRuleListRequestCompletableFuture<DescribeGroupMonitoringAgentProcessResponse> describeGroupMonitoringAgentProcess(DescribeGroupMonitoringAgentProcessRequest request)
You can create a process monitoring task to monitor all or the specified Elastic Compute Service (ECS) instances in an application group and configure alert rules for the process monitoring task.
request - the request parameters of DescribeGroupMonitoringAgentProcess DescribeGroupMonitoringAgentProcessRequestCompletableFuture<DescribeHostAvailabilityListResponse> describeHostAvailabilityList(DescribeHostAvailabilityListRequest request)
This topic provides an example to show how to query all the availability monitoring tasks of your Alibaba Cloud account. The sample responses indicate that the account has one availability monitoring task named ecs_instance.
request - the request parameters of DescribeHostAvailabilityList DescribeHostAvailabilityListRequestCompletableFuture<DescribeHybridMonitorDataListResponse> describeHybridMonitorDataList(DescribeHybridMonitorDataListRequest request)
Hybrid Cloud Monitoring is activated. For more information, see Activate Hybrid Cloud Monitoring.
The size of monitoring data that is returned in each call cannot exceed 1.5 MB. If the returned data reaches the upper limit, the query fails. You must reset the query conditions.
This topic provides an example to show how to query the monitoring data of the AliyunEcs_cpu_total metric in the default-aliyun namespace from 1653804865 (14:14:25 on May 29, 2022) to 1653805225 (14:20:25 on May 29, 2022).
request - the request parameters of DescribeHybridMonitorDataList DescribeHybridMonitorDataListRequestCompletableFuture<DescribeHybridMonitorNamespaceListResponse> describeHybridMonitorNamespaceList(DescribeHybridMonitorNamespaceListRequest request)
In this example, all namespaces within the current account are queried. The response shows that the current account has only one namespace named aliyun-test.
request - the request parameters of DescribeHybridMonitorNamespaceList DescribeHybridMonitorNamespaceListRequestCompletableFuture<DescribeHybridMonitorSLSGroupResponse> describeHybridMonitorSLSGroup(DescribeHybridMonitorSLSGroupRequest request)
In this example, all Logstore groups within the current account are queried. The response shows that the current account has two Logstore groups: Logstore_test and Logstore_aliyun.
request - the request parameters of DescribeHybridMonitorSLSGroup DescribeHybridMonitorSLSGroupRequestCompletableFuture<DescribeHybridMonitorTaskListResponse> describeHybridMonitorTaskList(DescribeHybridMonitorTaskListRequest request)
This topic provides an example on how to query all metric import tasks that belong to the current Alibaba Cloud account. The returned result indicates that the current account has only one metric import task. The metric import task is named aliyun_task.
request - the request parameters of DescribeHybridMonitorTaskList DescribeHybridMonitorTaskListRequestCompletableFuture<DescribeLogMonitorAttributeResponse> describeLogMonitorAttribute(DescribeLogMonitorAttributeRequest request)
request - the request parameters of DescribeLogMonitorAttribute DescribeLogMonitorAttributeRequestCompletableFuture<DescribeLogMonitorListResponse> describeLogMonitorList(DescribeLogMonitorListRequest request)
request - the request parameters of DescribeLogMonitorList DescribeLogMonitorListRequestCompletableFuture<DescribeMetricDataResponse> describeMetricData(DescribeMetricDataRequest request)
Different from DescribeMetricList, the DescribeMetricData operation provides statistical features. You can set the Dimension parameter to
{"instanceId": "i-abcdefgh12****"}to aggregate all data of your Alibaba Cloud account. This topic provides an example on how to query the monitoring data of thecpu_idlemetric for Elastic Compute Service (ECS). The namespace of ECS isacs_ecs_dashboard.
request - the request parameters of DescribeMetricData DescribeMetricDataRequestCompletableFuture<DescribeMetricLastResponse> describeMetricLast(DescribeMetricLastRequest request)
If
Throttling.UserorRequest was denied due to user flow controlis returned when you call an API operation, the API operation is throttled. For more information about how to handle the issue, see How do I handle the throttling of a query API?
The storage duration of the monitoring data of each cloud service is related to the Period parameter (statistical period). A larger value of the Period parameter indicates that the monitoring data is distributed in a larger time range and the storage duration of the monitoring data is longer. The following list describes the specific relationships:
Period parameter is less than 60 seconds.Period parameter is 60 seconds.Period parameter is greater than or equal to 300 seconds.This topic provides an example on how to query the latest monitoring data of the CPUUtilization metric for Elastic Compute Service (ECS). The namespace of ECS is acs_ecs_dashboard. The returned result indicates that the monitoring data for the instance i-abcdefgh12**** of the account 123456789876**** is queried at an interval of 60 seconds. The maximum, minimum, and average values of the metric are 100, 93.1, and 99.52.
request - the request parameters of DescribeMetricLast DescribeMetricLastRequestCompletableFuture<DescribeMetricListResponse> describeMetricList(DescribeMetricListRequest request)
Each API operation can be called up to 50 times per second. An Alibaba Cloud account and the RAM users within the account share the quota.
This topic provides an example to show how to query the monitoring data of the
cpu_idlemetric for Elastic Compute Service (ECS). The namespace of ECS isacs_ecs_dashboard. The returned result indicates that the monitoring data for the instancei-abcdefgh12****of the account120886317861****is queried at an interval of 60 seconds. The maximum, minimum, and average values of the metric are 100, 93.1, and 99.52.
request - the request parameters of DescribeMetricList DescribeMetricListRequestCompletableFuture<DescribeMetricMetaListResponse> describeMetricMetaList(DescribeMetricMetaListRequest request)
This operation is used together with DescribeMetricList and DescribeMetricLast. For more information, see DescribeMetricList and DescribeMetricLast.
request - the request parameters of DescribeMetricMetaList DescribeMetricMetaListRequestCompletableFuture<DescribeMetricRuleBlackListResponse> describeMetricRuleBlackList(DescribeMetricRuleBlackListRequest request)
request - the request parameters of DescribeMetricRuleBlackList DescribeMetricRuleBlackListRequestCompletableFuture<DescribeMetricRuleCountResponse> describeMetricRuleCount(DescribeMetricRuleCountRequest request)
request - the request parameters of DescribeMetricRuleCount DescribeMetricRuleCountRequestCompletableFuture<DescribeMetricRuleListResponse> describeMetricRuleList(DescribeMetricRuleListRequest request)
This topic provides an example on how to query all alert rules within your Alibaba Cloud account. The returned result shows that only one alert rule is found. The name of the alert rule is Rule_01 and the ID is applyTemplate344cfd42-0f32-4fd6-805a-88d7908a****.
request - the request parameters of DescribeMetricRuleList DescribeMetricRuleListRequestCompletableFuture<DescribeMetricRuleTargetsResponse> describeMetricRuleTargets(DescribeMetricRuleTargetsRequest request)
This operation supports only Message Service (MNS) resources.
This topic provides an example on how to query the resources that are associated with an alert rule whose ID is
ae06917_75a8c43178ab66****.
request - the request parameters of DescribeMetricRuleTargets DescribeMetricRuleTargetsRequestCompletableFuture<DescribeMetricRuleTemplateAttributeResponse> describeMetricRuleTemplateAttribute(DescribeMetricRuleTemplateAttributeRequest request)
This topic provides an example on how to query the details of an alert template whose ID is 70****.
request - the request parameters of DescribeMetricRuleTemplateAttribute DescribeMetricRuleTemplateAttributeRequestCompletableFuture<DescribeMetricRuleTemplateListResponse> describeMetricRuleTemplateList(DescribeMetricRuleTemplateListRequest request)
This topic provides an example on how to query alert templates. In this example, the following alert templates are returned in the response: ECS_Template1 and ECS_Template2.
request - the request parameters of DescribeMetricRuleTemplateList DescribeMetricRuleTemplateListRequestCompletableFuture<DescribeMetricTopResponse> describeMetricTop(DescribeMetricTopRequest request)
The storage duration of the monitoring data of each cloud service is related to the Period parameter (statistical period). A larger value of the Period parameter indicates that the monitoring data is distributed in a larger time range and the storage duration of the monitoring data is longer. The following list describes the specific relationships:
Period parameter is less than 60 seconds.Period parameter is 60 seconds.Period is greater than or equal to 300 seconds.This topic provides an example on how to query the monitoring data of the cpu_idle metric in the last 60 seconds for Elastic Compute Service (ECS). The namespace of ECS is acs_ecs_dashboard. The monitoring data is sorted in descending order based on the Average field.
request - the request parameters of DescribeMetricTop DescribeMetricTopRequestCompletableFuture<DescribeMonitorGroupCategoriesResponse> describeMonitorGroupCategories(DescribeMonitorGroupCategoriesRequest request)
request - the request parameters of DescribeMonitorGroupCategories DescribeMonitorGroupCategoriesRequestCompletableFuture<DescribeMonitorGroupDynamicRulesResponse> describeMonitorGroupDynamicRules(DescribeMonitorGroupDynamicRulesRequest request)
request - the request parameters of DescribeMonitorGroupDynamicRules DescribeMonitorGroupDynamicRulesRequestCompletableFuture<DescribeMonitorGroupInstanceAttributeResponse> describeMonitorGroupInstanceAttribute(DescribeMonitorGroupInstanceAttributeRequest request)
request - the request parameters of DescribeMonitorGroupInstanceAttribute DescribeMonitorGroupInstanceAttributeRequestCompletableFuture<DescribeMonitorGroupInstancesResponse> describeMonitorGroupInstances(DescribeMonitorGroupInstancesRequest request)
request - the request parameters of DescribeMonitorGroupInstances DescribeMonitorGroupInstancesRequestCompletableFuture<DescribeMonitorGroupNotifyPolicyListResponse> describeMonitorGroupNotifyPolicyList(DescribeMonitorGroupNotifyPolicyListRequest request)
request - the request parameters of DescribeMonitorGroupNotifyPolicyList DescribeMonitorGroupNotifyPolicyListRequestCompletableFuture<DescribeMonitorGroupsResponse> describeMonitorGroups(DescribeMonitorGroupsRequest request)
This topic provides an example of how to query the application groups of the current account. The response shows that the current account has two application groups: testGroup124 and test123.
request - the request parameters of DescribeMonitorGroups DescribeMonitorGroupsRequestCompletableFuture<DescribeMonitorResourceQuotaAttributeResponse> describeMonitorResourceQuotaAttribute(DescribeMonitorResourceQuotaAttributeRequest request)
request - the request parameters of DescribeMonitorResourceQuotaAttribute DescribeMonitorResourceQuotaAttributeRequestCompletableFuture<DescribeMonitoringAgentAccessKeyResponse> describeMonitoringAgentAccessKey(DescribeMonitoringAgentAccessKeyRequest request)
request - the request parameters of DescribeMonitoringAgentAccessKey DescribeMonitoringAgentAccessKeyRequestCompletableFuture<DescribeMonitoringAgentConfigResponse> describeMonitoringAgentConfig(DescribeMonitoringAgentConfigRequest request)
request - the request parameters of DescribeMonitoringAgentConfig DescribeMonitoringAgentConfigRequestCompletableFuture<DescribeMonitoringAgentHostsResponse> describeMonitoringAgentHosts(DescribeMonitoringAgentHostsRequest request)
request - the request parameters of DescribeMonitoringAgentHosts DescribeMonitoringAgentHostsRequestCompletableFuture<DescribeMonitoringAgentProcessesResponse> describeMonitoringAgentProcesses(DescribeMonitoringAgentProcessesRequest request)
Before you call this operation, call the CreateMonitoringAgentProcess operation to create processes. For more information, see CreateMonitoringAgentProcess. This topic provides an example of how to query the processes of the
i-hp3hl3cx1pbahzy8****instance. The response indicates the details of theNGINXandHTTPprocesses.
request - the request parameters of DescribeMonitoringAgentProcesses DescribeMonitoringAgentProcessesRequestCompletableFuture<DescribeMonitoringAgentStatusesResponse> describeMonitoringAgentStatuses(DescribeMonitoringAgentStatusesRequest request)
This topic describes how to query the status of the CloudMonitor agent that is installed on the i-hp3dunahluwajv6f**** instance. The result indicates that the CloudMonitor agent is in the running state.
request - the request parameters of DescribeMonitoringAgentStatuses DescribeMonitoringAgentStatusesRequestCompletableFuture<DescribeMonitoringConfigResponse> describeMonitoringConfig(DescribeMonitoringConfigRequest request)
request - the request parameters of DescribeMonitoringConfig DescribeMonitoringConfigRequestCompletableFuture<DescribeProductResourceTagKeyListResponse> describeProductResourceTagKeyList(DescribeProductResourceTagKeyListRequest request)
If a tag is attached to multiple cloud resources in the region, the key of the tag is returned only once.
request - the request parameters of DescribeProductResourceTagKeyList DescribeProductResourceTagKeyListRequestCompletableFuture<DescribeProductsOfActiveMetricRuleResponse> describeProductsOfActiveMetricRule(DescribeProductsOfActiveMetricRuleRequest request)
request - the request parameters of DescribeProductsOfActiveMetricRule DescribeProductsOfActiveMetricRuleRequestCompletableFuture<DescribeProjectMetaResponse> describeProjectMeta(DescribeProjectMetaRequest request)
The information obtained by this operation includes the service description, namespace, and tags.
request - the request parameters of DescribeProjectMeta DescribeProjectMetaRequestCompletableFuture<DescribeSiteMonitorAttributeResponse> describeSiteMonitorAttribute(DescribeSiteMonitorAttributeRequest request)
This topic provides an example on how to query the details of a site monitoring task whose ID is cc641dff-c19d-45f3-ad0a-818a0c4f****. The returned result indicates that the task name is test123, the URL that is monitored by the task is https://aliyun.com, and the name of the carrier is Alibaba.
request - the request parameters of DescribeSiteMonitorAttribute DescribeSiteMonitorAttributeRequestCompletableFuture<DescribeSiteMonitorDataResponse> describeSiteMonitorData(DescribeSiteMonitorDataRequest request)
request - the request parameters of DescribeSiteMonitorData DescribeSiteMonitorDataRequestCompletableFuture<DescribeSiteMonitorISPCityListResponse> describeSiteMonitorISPCityList(DescribeSiteMonitorISPCityListRequest request)
This topic provides an example on how to query the detection points that are provided by China Unicom in Guiyang.
request - the request parameters of DescribeSiteMonitorISPCityList DescribeSiteMonitorISPCityListRequestCompletableFuture<DescribeSiteMonitorListResponse> describeSiteMonitorList(DescribeSiteMonitorListRequest request)
This topic provides an example on how to query all the site monitoring tasks of your Alibaba Cloud account. In this example, the returned result indicates that the Alibaba Cloud account has one site monitoring task named HanZhou_ECS2.
request - the request parameters of DescribeSiteMonitorList DescribeSiteMonitorListRequestCompletableFuture<DescribeSiteMonitorLogResponse> describeSiteMonitorLog(DescribeSiteMonitorLogRequest request)
You can create an instant test task only by using the Alibaba Cloud account that you used to enable Network Analysis and Monitoring.
This topic provides an example to show how to query the logs of an instant test task whose ID is afa5c3ce-f944-4363-9edb-ce919a29****.
request - the request parameters of DescribeSiteMonitorLog DescribeSiteMonitorLogRequestCompletableFuture<DescribeSiteMonitorQuotaResponse> describeSiteMonitorQuota(DescribeSiteMonitorQuotaRequest request)
request - the request parameters of DescribeSiteMonitorQuota DescribeSiteMonitorQuotaRequestCompletableFuture<DescribeSiteMonitorStatisticsResponse> describeSiteMonitorStatistics(DescribeSiteMonitorStatisticsRequest request)
This topic provides an example on how to query the statistics of the Availability metric for a site monitoring task whose ID is ef4cdc8b-9dc7-43e7-810e-f950e56c****. The result indicates that the availability rate of the site is 100%.
request - the request parameters of DescribeSiteMonitorStatistics DescribeSiteMonitorStatisticsRequestCompletableFuture<DescribeSyntheticProbeListResponse> describeSyntheticProbeList(DescribeSyntheticProbeListRequest request)
request - the request parameters of DescribeSyntheticProbeList DescribeSyntheticProbeListRequestCompletableFuture<DescribeSystemEventAttributeResponse> describeSystemEventAttribute(DescribeSystemEventAttributeRequest request)
request - the request parameters of DescribeSystemEventAttribute DescribeSystemEventAttributeRequestCompletableFuture<DescribeSystemEventCountResponse> describeSystemEventCount(DescribeSystemEventCountRequest request)
You can call the DescribeSystemEventMetaList operation to query the cloud services supported by CloudMonitor and their system events.
This topic provides an example on how to query the number of times that a system event of Elastic Compute Service (ECS) has occurred. The returned result shows that the specified system event has occurred three times.
request - the request parameters of DescribeSystemEventCount DescribeSystemEventCountRequestCompletableFuture<DescribeSystemEventHistogramResponse> describeSystemEventHistogram(DescribeSystemEventHistogramRequest request)
request - the request parameters of DescribeSystemEventHistogram DescribeSystemEventHistogramRequestCompletableFuture<DescribeSystemEventMetaListResponse> describeSystemEventMetaList(DescribeSystemEventMetaListRequest request)
request - the request parameters of DescribeSystemEventMetaList DescribeSystemEventMetaListRequestCompletableFuture<DescribeTagKeyListResponse> describeTagKeyList(DescribeTagKeyListRequest request)
request - the request parameters of DescribeTagKeyList DescribeTagKeyListRequestCompletableFuture<DescribeTagValueListResponse> describeTagValueList(DescribeTagValueListRequest request)
This topic provides an example of how to query the tag values corresponding to tagKey1. The return results are tagValue1 and tagValue2.
request - the request parameters of DescribeTagValueList DescribeTagValueListRequestCompletableFuture<DescribeUnhealthyHostAvailabilityResponse> describeUnhealthyHostAvailability(DescribeUnhealthyHostAvailabilityRequest request)
request - the request parameters of DescribeUnhealthyHostAvailability DescribeUnhealthyHostAvailabilityRequestCompletableFuture<DisableActiveMetricRuleResponse> disableActiveMetricRule(DisableActiveMetricRuleRequest request)
request - the request parameters of DisableActiveMetricRule DisableActiveMetricRuleRequestCompletableFuture<DisableEventRulesResponse> disableEventRules(DisableEventRulesRequest request)
request - the request parameters of DisableEventRules DisableEventRulesRequestCompletableFuture<DisableHostAvailabilityResponse> disableHostAvailability(DisableHostAvailabilityRequest request)
request - the request parameters of DisableHostAvailability DisableHostAvailabilityRequestCompletableFuture<DisableMetricRulesResponse> disableMetricRules(DisableMetricRulesRequest request)
request - the request parameters of DisableMetricRules DisableMetricRulesRequestCompletableFuture<DisableSiteMonitorsResponse> disableSiteMonitors(DisableSiteMonitorsRequest request)
request - the request parameters of DisableSiteMonitors DisableSiteMonitorsRequestCompletableFuture<EnableActiveMetricRuleResponse> enableActiveMetricRule(EnableActiveMetricRuleRequest request)
request - the request parameters of EnableActiveMetricRule EnableActiveMetricRuleRequestCompletableFuture<EnableEventRulesResponse> enableEventRules(EnableEventRulesRequest request)
request - the request parameters of EnableEventRules EnableEventRulesRequestCompletableFuture<EnableHostAvailabilityResponse> enableHostAvailability(EnableHostAvailabilityRequest request)
request - the request parameters of EnableHostAvailability EnableHostAvailabilityRequestCompletableFuture<EnableMetricRuleBlackListResponse> enableMetricRuleBlackList(EnableMetricRuleBlackListRequest request)
request - the request parameters of EnableMetricRuleBlackList EnableMetricRuleBlackListRequestCompletableFuture<EnableMetricRulesResponse> enableMetricRules(EnableMetricRulesRequest request)
request - the request parameters of EnableMetricRules EnableMetricRulesRequestCompletableFuture<EnableSiteMonitorsResponse> enableSiteMonitors(EnableSiteMonitorsRequest request)
request - the request parameters of EnableSiteMonitors EnableSiteMonitorsRequestCompletableFuture<InstallMonitoringAgentResponse> installMonitoringAgent(InstallMonitoringAgentRequest request)
The Cloud Assistant client is installed on an ECS instance. For more information about how to install the Cloud Assistant client, see Overview.
request - the request parameters of InstallMonitoringAgent InstallMonitoringAgentRequestCompletableFuture<ModifyGroupMonitoringAgentProcessResponse> modifyGroupMonitoringAgentProcess(ModifyGroupMonitoringAgentProcessRequest request)
request - the request parameters of ModifyGroupMonitoringAgentProcess ModifyGroupMonitoringAgentProcessRequestCompletableFuture<ModifyHostAvailabilityResponse> modifyHostAvailability(ModifyHostAvailabilityRequest request)
This topic provides an example on how to change the name of an availability monitoring task named 12345 in an application group named 123456 to task2.
request - the request parameters of ModifyHostAvailability ModifyHostAvailabilityRequestCompletableFuture<ModifyHostInfoResponse> modifyHostInfo(ModifyHostInfoRequest request)
request - the request parameters of ModifyHostInfo ModifyHostInfoRequestCompletableFuture<ModifyHybridMonitorNamespaceResponse> modifyHybridMonitorNamespace(ModifyHybridMonitorNamespaceRequest request)
This topic provides an example on how to change the data retention period of the aliyun namespace to cms.s1.2xlarge. The response shows that the namespace is modified.
request - the request parameters of ModifyHybridMonitorNamespace ModifyHybridMonitorNamespaceRequestCompletableFuture<ModifyHybridMonitorSLSGroupResponse> modifyHybridMonitorSLSGroup(ModifyHybridMonitorSLSGroupRequest request)
In this example, a Logstore group named Logstore_test is modified. The Logstore of the aliyun-project project in the cn-hangzhou region is changed to Logstore-aliyun-all. The response shows that the Logstore group is modified.
request - the request parameters of ModifyHybridMonitorSLSGroup ModifyHybridMonitorSLSGroupRequestCompletableFuture<ModifyHybridMonitorTaskResponse> modifyHybridMonitorTask(ModifyHybridMonitorTaskRequest request)
This topic provides an example on how to change the collection period of a metric import task whose ID is 36**** to 15 seconds. The task is used to monitor the logs that are imported from Log Service. The returned result indicates that the metric is modified.
request - the request parameters of ModifyHybridMonitorTask ModifyHybridMonitorTaskRequestCompletableFuture<ModifyMetricRuleBlackListResponse> modifyMetricRuleBlackList(ModifyMetricRuleBlackListRequest request)
request - the request parameters of ModifyMetricRuleBlackList ModifyMetricRuleBlackListRequestCompletableFuture<ModifyMetricRuleTemplateResponse> modifyMetricRuleTemplate(ModifyMetricRuleTemplateRequest request)
This topic provides an example on how to modify an alert template whose version is 1 and ID is 123456. The alert level is changed to Critical. The statistical method is changed to Average. The alert threshold comparator is changed to GreaterThanOrEqualToThreshold. The alert threshold is changed to 90. The number of alert retries is changed to 3. The response shows that the alert template is modified.
request - the request parameters of ModifyMetricRuleTemplate ModifyMetricRuleTemplateRequestCompletableFuture<ModifyMonitorGroupResponse> modifyMonitorGroup(ModifyMonitorGroupRequest request)
request - the request parameters of ModifyMonitorGroup ModifyMonitorGroupRequestCompletableFuture<ModifyMonitorGroupInstancesResponse> modifyMonitorGroupInstances(ModifyMonitorGroupInstancesRequest request)
request - the request parameters of ModifyMonitorGroupInstances ModifyMonitorGroupInstancesRequestCompletableFuture<ModifySiteMonitorResponse> modifySiteMonitor(ModifySiteMonitorRequest request)
The number of site monitoring tasks.
request - the request parameters of ModifySiteMonitor ModifySiteMonitorRequestCompletableFuture<PutContactResponse> putContact(PutContactRequest request)
request - the request parameters of PutContact PutContactRequestCompletableFuture<PutContactGroupResponse> putContactGroup(PutContactGroupRequest request)
This topic provides an example on how to create an alert contact group named ECS_Group.
request - the request parameters of PutContactGroup PutContactGroupRequestCompletableFuture<PutCustomEventResponse> putCustomEvent(PutCustomEventRequest request)
request - the request parameters of PutCustomEvent PutCustomEventRequestCompletableFuture<PutCustomEventRuleResponse> putCustomEventRule(PutCustomEventRuleRequest request)
Before you call this operation, call the PutCustomEvent operation to report the monitoring data of the custom event. For more information, see PutCustomEvent.
request - the request parameters of PutCustomEventRule PutCustomEventRuleRequestCompletableFuture<PutCustomMetricResponse> putCustomMetric(PutCustomMetricRequest request)
We recommend that you call the PutHybridMonitorMetricData operation of Hybrid Cloud Monitoring to report monitoring data.
request - the request parameters of PutCustomMetric PutCustomMetricRequestCompletableFuture<PutCustomMetricRuleResponse> putCustomMetricRule(PutCustomMetricRuleRequest request)
Before you call this operation, call the PutCustomMetric operation to report custom monitoring data. For more information, see PutCustomMetric.
request - the request parameters of PutCustomMetricRule PutCustomMetricRuleRequestCompletableFuture<PutEventRuleResponse> putEventRule(PutEventRuleRequest request)
If the specified rule name does not exist, an event-triggered alert rule is created. If the specified rule name exists, the specified event-triggered alert rule is modified.
In this example, the myRuleName alert rule is created for the ecs cloud service.
request - the request parameters of PutEventRule PutEventRuleRequestCompletableFuture<PutEventRuleTargetsResponse> putEventRuleTargets(PutEventRuleTargetsRequest request)
request - the request parameters of PutEventRuleTargets PutEventRuleTargetsRequestCompletableFuture<PutExporterOutputResponse> putExporterOutput(PutExporterOutputRequest request)
The monitoring data can be exported only to Log Service. More services will be supported in the future.
request - the request parameters of PutExporterOutput PutExporterOutputRequestCompletableFuture<PutExporterRuleResponse> putExporterRule(PutExporterRuleRequest request)
request - the request parameters of PutExporterRule PutExporterRuleRequestCompletableFuture<PutGroupMetricRuleResponse> putGroupMetricRule(PutGroupMetricRuleRequest request)
This topic provides an example on how to create an alert rule for the cpu_total metric of Elastic Compute Service (ECS) in the 17285**** application group. The ID of the alert rule is 123456. The name of the alert rule is Rule_test. The alert level is Critical. The statistical method is Average. The alert threshold comparator is GreaterThanOrEqualToThreshold. The alert threshold is 90. The number of alert retries is 3. The returned result shows that the alert rule is created and the alert rule ID is 123456.
request - the request parameters of PutGroupMetricRule PutGroupMetricRuleRequestCompletableFuture<PutHybridMonitorMetricDataResponse> putHybridMonitorMetricData(PutHybridMonitorMetricDataRequest request)
Hybrid Cloud Monitoring is activated. For more information, see Activate Hybrid Cloud Monitoring.
The size of the monitoring data that you import at a time must be less than or equal to 1 MB.
This topic provides an example on how to import the monitoring data of the CPU_Usage metric to the default-aliyun namespace of Hybrid Cloud Monitoring.
request - the request parameters of PutHybridMonitorMetricData PutHybridMonitorMetricDataRequestCompletableFuture<PutLogMonitorResponse> putLogMonitor(PutLogMonitorRequest request)
In the example of this topic, the cpu_total log monitoring metric is created. The response shows that the log monitoring metric is created and the metric ID is 16****.
request - the request parameters of PutLogMonitor PutLogMonitorRequestCompletableFuture<PutMetricRuleTargetsResponse> putMetricRuleTargets(PutMetricRuleTargetsRequest request)
This topic provides an example on how to associate an alert rule with a resource. In this example, the alert rule is ae06917_75a8c43178ab66****, the resource is acs:mns:cn-hangzhou:120886317861****:/queues/test/message, and the ID of the resource for which alerts are triggered is 1. The response indicates that the resource is associated with the specified alert rule.
request - the request parameters of PutMetricRuleTargets PutMetricRuleTargetsRequestCompletableFuture<PutMonitorGroupDynamicRuleResponse> putMonitorGroupDynamicRule(PutMonitorGroupDynamicRuleRequest request)
request - the request parameters of PutMonitorGroupDynamicRule PutMonitorGroupDynamicRuleRequestCompletableFuture<PutMonitoringConfigResponse> putMonitoringConfig(PutMonitoringConfigRequest request)
request - the request parameters of PutMonitoringConfig PutMonitoringConfigRequestCompletableFuture<PutResourceMetricRuleResponse> putResourceMetricRule(PutResourceMetricRuleRequest request)
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.
request - the request parameters of PutResourceMetricRule PutResourceMetricRuleRequestCompletableFuture<PutResourceMetricRulesResponse> putResourceMetricRules(PutResourceMetricRulesRequest request)
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.
request - the request parameters of PutResourceMetricRules PutResourceMetricRulesRequestCompletableFuture<RemoveTagsResponse> removeTags(RemoveTagsRequest request)
request - the request parameters of RemoveTags RemoveTagsRequestCompletableFuture<SendDryRunSystemEventResponse> sendDryRunSystemEvent(SendDryRunSystemEventRequest request)
This operation is used to test whether a system event can be triggered as expected. You can call this operation to simulate a system event and check whether an expected response is returned after the system event triggers an alert.
request - the request parameters of SendDryRunSystemEvent SendDryRunSystemEventRequestCompletableFuture<UninstallMonitoringAgentResponse> uninstallMonitoringAgent(UninstallMonitoringAgentRequest request)
This API operation is not applicable to Elastic Compute Service (ECS) instances. To uninstall the agent from an ECS instance, see Install and uninstall the CloudMonitor agent.
request - the request parameters of UninstallMonitoringAgent UninstallMonitoringAgentRequestCopyright © 2026. All rights reserved.