Resource Monitoring collects data for metrics based on the region or carrier of client IP addresses. By monitoring your CDN resources, you can obtain a comprehensive view of key metrics, such as bandwidth usage and cache hit ratio. This information helps you optimize your configurations.
Overview
Compared with real-time monitoring, Resource Monitoring supports a wider time range for single queries and older historical data:
Supported time granularities
The maximum time range for a single query and the retention period of historical data vary. This variation depends on whether you query data in the console or by calling an API operation. The following tables describe the relationship between granularity, maximum query span, historical data retention, and data latency.
In the console:
Granularity
Maximum time range per query
Historical data available
Data latency
5 minutes
3 days
90 days
15 minutes
1 hour
31 days
90 days
4 hours
1 day
90 days
90 days
4:00 AM the next day
By calling APIs:
Granularity
Maximum time range per query
Historical data available
Data latency
5 minutes
3 days
93 days
15 minutes
1 hour
31 days
186 days
4 hours
1 day
366 days
366 days
4:00 AM the next day
Metrics
Resource Monitoring provides the six metrics that are listed in the following table. You can select the domain names, regions, and carriers that you want to monitor. View the details for each metric online or download the query results for analysis.
Resource Monitoring collects statistics based on the region or carrier of client IP addresses. In contrast, billing is based on statistics about traffic, bandwidth, and requests that are generated on CDN points of presence (POPs) in each billing region. The results may differ because the statistical methods are different. The charts in Resource Monitoring are intended to show bandwidth trends. To query the metering data that corresponds to your bills, see Usage overview.
The data is calculated and statistics are generated using APIs. For more information, see the API documentation that corresponds to each metric in the following table.
Metric | Monitored data | Related APIs |
Data Transfer/Bandwidth of Requests | Displays the bandwidth and traffic of accelerated domain names. Data can be queried by region, carrier, and protocol (HTTP, HTTPS, QUIC, IPv4, and IPv6). | |
Back-to-origin Data Transfer/Bandwidth | Displays the origin bandwidth and origin traffic of accelerated domain names. Note
| |
Number of Requests | Displays the number of requests and queries per second (QPS) for accelerated domain names. Data can be queried by region, carrier, and protocol (HTTP, HTTPS, QUIC, IPv4, and IPv6). Note
| |
Hit Rate | Displays the byte hit ratio and request hit ratio of accelerated domain names. Note
| |
HTTPCODE | Displays the HTTP status code information for accelerated domain names. You can query data by the 2xx, 3xx, 4xx, and 5xx status codes. For detailed descriptions and solutions for status codes, see HTTP status codes.
| |
HTTP Status Codes to Back-to-origin Requests | Displays the back-to-origin HTTP status code information for accelerated domain names. You can query data by the 2xx, 3xx, 4xx, and 5xx status codes. For detailed descriptions and solutions for status codes, see HTTP status codes.
|
Notes
The traffic data for an accelerated domain name that is queried using the monitoring or usage query features in the console (or using OpenAPI) differs from the traffic data that is calculated from logs. Typically, the traffic data from monitoring and usage queries is 1.1 times the traffic data that is calculated from logs. For more information, see Why is there a discrepancy between traffic data from monitoring queries, usage queries, and log analysis?.
Usage vs. Resource Monitoring vs. Real-time Monitoring
Usage: Usage collects usage data based on POPs. Each POP belongs to a specific billing region. Therefore, you can query usage data only by billing region, such as the Chinese mainland, Asia Pacific 1, and North America. For more information, see Query resource usage.
Resource Monitoring and Real-time Monitoring: These features collect monitoring data based on client IP addresses. Each client IP address belongs to a specific region or carrier. Therefore, you can query monitoring data only by region or carrier (or a combination of both). For more information, see Resource Monitoring and Real-time Monitoring.
Resource Monitoring vs. Real-time Monitoring
Minimum data latency: Real-time Monitoring provides data with lower latency. In Real-time Monitoring, if the data granularity is 1 minute, the data latency is approximately 5 minutes. In Resource Monitoring, the minimum data granularity is 5 minutes, and the data latency is approximately 15 minutes.
Minimum data granularity: Real-time Monitoring provides data with a finer granularity. The minimum data granularity is 1 minute for Real-time Monitoring and 5 minutes for Resource Monitoring.
Queryable protocol layers: Resource Monitoring lets you query data by more protocol layers. Resource Monitoring supports querying data by protocol layer, such as HTTP, HTTPS, QUIC, IPv4, and IPv6. Real-time Monitoring does not support this feature.
Procedure
Log on to the CDN console.
In the navigation pane on the left, choose .
On the Resource Monitoring page, select the metric and conditions and then click Search.
The dashboard displays the query results based on your selected metric and conditions:
