You can call this operation to query traffic data for accelerated domain names. Compared to the DescribeVodDomainRealTimeTrafficData operation, this operation supports queries for historical data over a longer time range. You can query data from the last 366 days. However, this operation has a larger time granularity, with a minimum of 5 minutes, and higher data latency.
Operation description
The endpoint for this operation is available only in the China (Shanghai) region.
This operation supports batch queries. You can query data for up to 500 domain names in a single request.
If you do not specify the
StartTimeandEndTimeparameters, data from the last 24 hours is returned by default. If you specifyStartTimeandEndTime, data within the specified time range is returned.
Data time granularity
If you do not set the Interval parameter, the default time granularity of the returned data is determined by the time range that you specify between StartTime and EndTime. The following table describes the time granularity, the supported time range for historical data queries, and the data latency.
Time granularity | Time span of a single query | Queryable time range for historical data | Data latency |
5 minutes | The time span of a single query is less than 3 days | 93 days | 15 minutes |
1 hour | The time span of a single query is greater than or equal to 3 days and less than 31 days | 186 days | Usually 3 to 4 hours |
1 day | The time span of a single query is greater than or equal to 31 days and less than or equal to 366 days | 366 days | Usually 4 hours, but no more than 24 hours |
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
vod:DescribeVodDomainTrafficData |
get |
*All Resource
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| DomainName |
string |
No |
The accelerated domain name that you want to query.
|
example.com |
| StartTime |
string |
No |
The beginning of the time range to query. The time follows the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time is displayed in UTC. |
2019-01-20T13:59:58Z |
| EndTime |
string |
No |
The end of the time range to query. The time follows the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time is displayed in UTC. Note
The end time must be later than the start time. |
2019-01-20T14:59:58Z |
| Interval |
string |
No |
The time granularity of the data to query. Unit: seconds. Valid values: 300, 3600, and 86400. If you do not set this parameter, or if you set it to an unsupported value, the default value is used. The supported time granularity varies based on the time range specified by
|
300 |
| IspNameEn |
string |
No |
The name of the carrier. If you do not set this parameter, data of all carriers is queried. |
unicom |
| LocationNameEn |
string |
No |
The name of the region. If you do not set this parameter, data in all regions is queried. Currently, only the Shanghai region is supported. |
shanghai |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response. |
||
| EndTime |
string |
The end of the time range. |
2019-01-20T14:59:58Z |
| StartTime |
string |
The beginning of the time range. |
2019-01-20T13:59:58Z |
| RequestId |
string |
The request ID. |
D94E471F-1A27-442E-552D-D4D2000C**** |
| DomainName |
string |
The accelerated domain name. |
example.com |
| TotalTraffic |
string |
The total traffic. |
5906662826 |
| DataInterval |
string |
The time interval between two consecutive data entries. This is the time granularity of the data. Unit: seconds. |
300 |
| TrafficDataPerInterval |
object |
||
| DataModule |
array<object> |
The list of traffic data at each time interval. |
|
|
object |
|||
| HttpsDomesticValue |
string |
The HTTPS traffic on L1 nodes in the Chinese mainland. Unit: bytes. |
0 |
| Value |
string |
The total traffic. Unit: bytes. |
0 |
| OverseasValue |
string |
The traffic outside the Chinese mainland. Unit: bytes. |
0 |
| HttpsValue |
string |
The total HTTPS traffic on L1 nodes. Unit: bytes. |
0 |
| HttpsOverseasValue |
string |
The HTTPS traffic on L1 nodes outside the Chinese mainland. Unit: bytes. |
0 |
| TimeStamp |
string |
The data timestamp. The time follows the ISO 8601 standard and is displayed in UTC. |
2019-01-20T13:59:58Z |
| DomesticValue |
string |
The traffic in the Chinese mainland. Unit: bytes. |
0 |
Examples
Success response
JSON format
{
"EndTime": "2019-01-20T14:59:58Z",
"StartTime": "2019-01-20T13:59:58Z",
"RequestId": "D94E471F-1A27-442E-552D-D4D2000C****",
"DomainName": "example.com",
"TotalTraffic": "5906662826",
"DataInterval": "300\n",
"TrafficDataPerInterval": {
"DataModule": [
{
"HttpsDomesticValue": "0",
"Value": "0",
"OverseasValue": "0",
"HttpsValue": "0",
"HttpsOverseasValue": "0",
"TimeStamp": "2019-01-20T13:59:58Z",
"DomesticValue": "0"
}
]
}
}
Error codes
|
HTTP status code |
Error code |
Error message |
Description |
|---|---|---|---|
| 400 | MissingTimeParameter | The StartTime and EndTime must be both specified. | Both start time and end must be specified |
| 400 | InvalidStartTime.Malformed | The specified StartTime is invalid. | |
| 400 | InvalidEndTime.Malformed | The specified EndTime is invalid. | |
| 400 | InvalidEndTime.Mismatch | The specified EndTime is earlier than the StartTime. | End time is earlier than start time |
| 400 | InvalidStartTime.ValueNotSupported | The specified StartTime is invalid. |
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.