This document describes the products supported by health status in Cloud Service Diagnostics.
The following table lists the products that support health status monitoring. Support for more products is coming soon.
Category | Product name | Abbreviation | Resource type | Definition of unavailability | Unavailability criteria | Interval |
Compute | ECS | ECS | instance | An ECS instance is unavailable during a specific period if its performance is affected or degraded due to limitations of the underlying host, storage, or network. This includes issues such as Out of Memory (OOM) errors, blue screens, or hangs. When this happens, the system marks its status as abnormal. You can restart the instance to restore service, or submit a ticket to report the failure. | ECS monitors the instance status and reports events to CloudMonitor. Product: Event name: | Recorded on each status change |
Function Compute | FC | service | An FC service is unavailable if its request error rate (requests with an HTTP 500 status code / total requests) exceeds 10% during a period. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket to report the failure. | FC monitors service requests and reports time-series metrics to CloudMonitor. Namespace: Failed requests: Error rate: Unavailability is indicated if | Recorded every 10 minutes (fixed interval) | |
Storage | Object Storage Service | OSS | bucket | An OSS bucket is unavailable if the HTTP request error rate (failed requests with a 5xx status code / total requests) exceeds 10% during a period. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket to report the failure. | OSS monitors and calculates HTTP requests and reports time-series metrics to CloudMonitor. Namespace: Availability metric: Unavailability is indicated if | Recorded every 10 minutes (fixed interval) |
Elastic Block Storage | EBS | disk | An EBS disk is unavailable if it cannot be read from or written to, or if its read/write performance is severely degraded during a period. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket to report the failure. | EBS monitors the disk status and reports system events to CloudMonitor. Product: Local disk corruption alert starts: Disk performance severely affected: Unavailability is indicated if either of these two events occurs. | Recorded on each status change | |
Log Service | SLS | log project | A request that fails due to an SLS issue is a failed request. The service is unavailable if the error rate (failed requests / valid requests) exceeds 10% for 10 consecutive minutes. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket. | SLS monitors service requests and reports time-series metrics to CloudMonitor. Namespace: Failed requests: The number of 5xx errors filtered from the Valid requests: The total count of Unavailability is indicated if the error rate (total failed requests / total valid requests) in a 10-minute period > 10%. If the total number of valid requests is < 100, the error rate is not calculated, and the service is considered normal by default. | Recorded every 10 minutes (fixed interval) | |
Networking & CDN | Content Delivery Network | CDN | domain name | A CDN service is unavailable if its request error rate (failed requests with a 5xx status code returned by the domain name due to CDN system issues / total requests) exceeds 10% during a period. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket to report the failure. | CDN monitors service requests and reports time-series metrics to CloudMonitor. Namespace: Error rate metric: Total requests: | Recorded every 10 minutes (fixed interval) |
Dynamic Content Delivery Network | DCDN | domain name | A DCDN service is unavailable if its request error rate (failed requests with a 5xx status code returned by the domain name due to DCDN system issues / total requests) exceeds 10% during a period. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket to report the failure. | DCDN monitors service requests and reports time-series metrics to CloudMonitor. Namespace: Error rate metric: Total requests: | Recorded every 10 minutes (fixed interval) | |
NAT Gateway | NAT Gateway | instance | A NAT Gateway instance is unavailable if all its outbound data packets are dropped by the Alibaba Cloud egress gateway device during a period. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket. | NAT Gateway monitors the instance status and reports system events to CloudMonitor. Product: NAT data path unavailable event: An event is sent if the unavailability lasts for more than 10 minutes. The event is re-sent every 10 minutes if the issue persists. The service is considered recovered when these events stop. | Recorded every 10 minutes (arbitrary interval) | |
Middleware | API Gateway | API Gateway | instance | An API Gateway instance is unavailable if its request error rate (failed API calls due to gateway issues / total requests) exceeds 10% during a period. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket to report the failure. | API Gateway monitors and calculates service requests and reports time-series metrics to CloudMonitor. Namespace: Total requests: Failed requests: Instance node loss ratio: 1. The instance is unavailable if 2. The instance is unavailable if ( | Recorded every 10 minutes (fixed interval) |
ApsaraMQ for RocketMQ | ApsaraMQ | instance | An ApsaraMQ for RocketMQ instance is unavailable if all attempts to connect to it fail, or if all API requests to produce, consume, or confirm messages fail during a period. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket. (Note: Only RocketMQ 5.x instances are supported.) | ApsaraMQ for RocketMQ monitors instance status and reports availability changes through CloudMonitor system events. Product: Event names: | Recorded on each status change | |
ApsaraMQ for Kafka | Kafka | instance | An ApsaraMQ for Kafka instance is unavailable if all continuous attempts to call the Topic API of the specified instance fail, or if message delivery latency exceeds 5 minutes. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket. | ApsaraMQ for Kafka monitors instance status and reports availability changes through CloudMonitor system events. Product: Event names: | Recorded on each status change | |
Database | ApsaraDB for RDS | RDS | instance | An RDS instance is unavailable if all continuous attempts to connect to it fail during a period. When this happens, the system marks its status as abnormal. You can try to restart the instance to restore service or submit a ticket to report the failure. | RDS monitors the instance status and reports system events to CloudMonitor. Product: Event names: | Recorded on each status change |
ApsaraDB for MongoDB | MongoDB | instance | An ApsaraDB for MongoDB instance is unavailable if all continuous attempts to connect to it fail during a period. When this happens, the system marks its status as abnormal. You can try to restart the instance, component, or node to restore service or submit a ticket to report the failure. | ApsaraDB for MongoDB monitors the instance status and reports system events to CloudMonitor. Product: Event names: | Recorded on each status change | |
PolarDB | PolarDB | cluster | A PolarDB cluster is unavailable if all continuous attempts to connect to it fail during a period. When this happens, the system marks its status as abnormal. You can try to use node management to restore service or submit a ticket to report the failure. | PolarDB monitors the instance status and reports system events to CloudMonitor. Product: Event names: | Recorded on each status change | |
ApsaraDB for Redis | Redis | instance | An ApsaraDB for Redis instance is unavailable if all continuous attempts to connect to it fail during a period. When this happens, the system marks its status as abnormal. You can try to restart the instance to restore service or submit a ticket to report the failure. | ApsaraDB for Redis monitors the instance status and reports system events to CloudMonitor. Product: Event names: | Recorded on each status change | |
PolarDB-X | PolarDB-X | instance | A PolarDB-X instance is unavailable if all continuous attempts to connect to it fail during a period. When this happens, the system marks its status as abnormal. You can try to restart the instance to restore service or submit a ticket. | PolarDB-X monitors the instance status and reports system events to CloudMonitor. Product: Event names: | Recorded on each status change | |
AnalyticDB for PostgreSQL | AnalyticDB for PostgreSQL | instance | An AnalyticDB for PostgreSQL instance is unavailable if all continuous attempts to connect to it fail during a period. When this happens, the system marks its status as abnormal. You can try to restart the instance to restore service or submit a ticket. | AnalyticDB for PostgreSQL monitors instance status and reports availability changes through CloudMonitor system events. Product: Event names: | Recorded on each status change | |
Data Transmission Service | DTS | instance | A DTS instance is unavailable if data written to it cannot be synchronized to the destination and this status persists for more than 5 minutes. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket. | DTS monitors instance status and reports time-series metrics to CloudMonitor. Namespace: Synchronization task instance unavailable: Unavailability is indicated if Subscription task instance unavailable: Unavailability is indicated if Migration task instance unavailable: Unavailability is indicated if | Recorded every 5 minutes (fixed interval) | |
Lindorm | Lindorm | instance | A Lindorm instance is unavailable for a given minute if all attempts to connect to it fail within that minute. When this happens, the system marks its status as abnormal. | Lindorm monitors instance status and reports system events to CloudMonitor. Product: Event names: | Recorded on each status change | |
AI & Machine Learning | OpenSearch | OpenSearch | application | An OpenSearch application is unavailable if all continuous attempts to initiate search requests to it fail during a period. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket. | OpenSearch monitors and calculates service requests and reports time-series metrics to CloudMonitor. Namespace: Request status: Unavailability is indicated if all requests within a 10-minute period return a 5xx status code and the total number of requests is > 30. | Recorded every 10 minutes (fixed interval) |
Others | ApsaraVideo Live | LIVE | domain name | A request is considered failed due to an ApsaraVideo Live fault if: (1) for FLV-HTTP/RTMP, no data is returned for 20 seconds while the connection is maintained; or (2) for HLS, a 5xx error occurs. The service is unavailable if the error rate (failed requests / total requests) exceeds 20%. When this happens, the system marks its status as abnormal. If the service does not recover promptly, you can submit a ticket to report the failure. | ApsaraVideo Live monitors service requests and reports time-series metrics to CloudMonitor. Namespace: Error rate metric: Total requests: Unavailability is indicated if | Recorded every 10 minutes (fixed interval) |
Recorded on each status change: The system logs a record when the status changes from available to unavailable, and again when it changes back. For example, if a service becomes unavailable at 12:00:02 and recovers at 12:00:06, the period from 12:00:02 to 12:00:06 is marked as abnormal.
Recorded every 10 minutes (fixed interval): The result is calculated and recorded for fixed 10-minute intervals, such as 00:00:00–00:09:59 and 00:10:00–00:19:59. For example, if the period from 12:00:00 to 12:09:59 is calculated as unavailable, it is marked as abnormal. If the period from 12:10:00 to 12:19:59 is calculated as available, it is marked as normal. The system does not calculate results for non-fixed intervals, such as 12:01:00–12:10:59.
Recorded every 10 minutes (arbitrary interval): If a service is unavailable for any continuous 10-minute period, the system records that period as unavailable. For example, if a service becomes unavailable at 12:00:02 and the unavailability lasts until 12:12:05, the period from 12:00:02 to 12:10:01 is marked as abnormal. The subsequent period from 12:10:02 to 12:12:05 is less than 10 minutes and is therefore marked as normal.