tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
Documentation

DescribeTimingL7AnalysisData

Last updated: 2024-11-14 16:58:11

    1. API Description

    Domain name for API request: teo.tencentcloudapi.com.

    This API is used to query the time series data of the L7 domain name. Note that there is a delay of about 10 minutes for this API. It is recommended to pull data from 10 minutes before the current time.

    A maximum of 100 requests can be initiated per second for this API.

    We recommend you to use API Explorer
    Try it
    API Explorer provides a range of capabilities, including online call, signature authentication, SDK code generation, and API quick search. It enables you to view the request, response, and auto-generated examples.

    2. Input Parameters

    The following request parameter list only provides API request parameters and some common parameters. For the complete common parameter list, see Common Request Parameters.

    Parameter Name Required Type Description
    Action Yes String Common Params. The value used for this API: DescribeTimingL7AnalysisData.
    Version Yes String Common Params. The value used for this API: 2022-09-01.
    Region No String Common Params. This parameter is not required.
    StartTime Yes Timestamp ISO8601 The start time.
    EndTime Yes Timestamp ISO8601 The end time.
    MetricNames.N Yes Array of String Metric list. Valid values:
  • l7Flow_outFlux: L7 EdgeOne response traffic;
  • l7Flow_inFlux: L7 client request traffic;
  • l7Flow_flux: L7 total access traffic (including the EdgeOne response traffic and client request traffic);
  • l7Flow_outBandwidth: L7 EdgeOne response bandwidth;
  • l7Flow_inBandwidth: L7 client request bandwidth;
  • l7Flow_bandwidth: L7 total access bandwidth (including the EdgeOne response bandwidth and client request bandwidth);
  • l7Flow_request: L7 access request count.
    		•
    ZoneIds.N No Array of String Zone ID set. This parameter is required.
    Interval No String Query period granularity. Valid values:
  • min: 1 minute;
  • 5min: 5 minutes;
  • hour: 1 hour;
  • day: 1 day.
    • If this parameter is not filled in, the granularity will be automatically calculated based on the interval between the start time and end time. Specifically, data will be queried with a granularity of min, 5min, hour, and day respectively when the period is no more than 2 hours, no more than 2 days, no more than 7 days, and over 7 days.
    Filters.N No Array of QueryCondition Filter criteria. The detailed key values are as follows:
  • country: Filter by country/region. The country/region follows the ISO 3166-1 alpha-2 standard. Example value: CN.
  • province: Filter by province. This parameter is supported only when the service area is the Chinese mainland. For province codes, refer to the Mapping Table of Provinces Within the Chinese Mainland. Example value: 22.
  • isp: Filter by ISP. This parameter is supported only when the service area is the Chinese mainland. Valid values are as follows:
    2: China Telecom;
    26: China Unicom;
    1046: China Mobile;
    3947: China Tietong;
    38: CERNET;
    43: Great Wall Broadband;
    0: other ISPs.
  • domain: Filter by subdomain name. Example value: www.example.com.
  • url: Filter by URL path. Example value: /content or /content/test.jpg. If the url parameter is input, up to 30 days of data can be queried.
  • referer: Filter by Referer request header. Example value: http://www.example.com/. If the referer parameter is input, up to 30 days of data can be queried.
  • resourceType: Filter by resource type, which is generally the file suffix. Example value: .jpg. If the resourceType parameter is input, up to 30 days of data can be queried;
  • protocol: Filter by HTTP protocol version. Valid values are as follows:
    HTTP/1.0;
    HTTP/1.1;
    HTTP/2.0;
    HTTP/3;
    WebSocket.
  • socket: Filter by HTTP protocol type. Valid values are as follows:
    HTTP: HTTP protocol;
    HTTPS: HTTPS protocol;
    QUIC: QUIC protocol.
  • statusCode: Filter by edge status code. If the statusCode parameter is input, up to 30 days of data can be queried. Valid values are as follows:
    1XX: 1xx status code;
    2XX: 2xx status code;
    3XX: 3xx status code;
    4XX: 4xx status code;
    5XX: 5xx status code;
    An integer within the range [0,600).
  • browserType: Filter by browser type. If the browserType parameter is input, up to 30 days of data can be queried. Valid values are as follows:
    Firefox: Firefox browser;
    Chrome: Chrome browser;
    Safari: Safari browser;
    Other: other browser types;
    Empty: The browser type is empty;
    Bot: search engine crawler;
    MicrosoftEdge: Microsoft Edge browser;
    IE: IE browser;
    Opera: Opera browser;
    QQBrowser: QQ browser;
    LBBrowser: LB browser;
    MaxthonBrowser: Maxthon browser;
    SouGouBrowser: Sogou browser;
    BIDUBrowser: Baidu browser;
    TaoBrowser: Tao browser;
    UBrowser: UC browser.
  • deviceType: Filter by device type. If the deviceType parameter is input, up to 30 days of data can be queried. Valid values are as follows:
    TV: TV device;
    Tablet: tablet device;
    Mobile: mobile device;
    Desktop: desktop device;
    Other: other device types;
    Empty: The device type is empty.
  • operatingSystemType: Filter by operating system type. If the operatingSystemType parameter is input, up to 30 days of data can be queried. Valid values are as follows:
    Linux: Linux operating system;
    MacOS: MacOS operating system;
    Android: Android operating system;
    IOS: iOS operating system;
    Windows: Windows operating system;
    NetBSD: NetBSD;
    ChromiumOS: ChromiumOS;
    Bot: search engine crawler;
    Other: other types of operating systems;
    Empty: The operating system is empty.
  • tlsVersion: Filter by TLS version. If the tlsVersion parameter is input, up to 30 days of data can be queried. Valid values are as follows:
    TLS1.0;
    TLS1.1;
    TLS1.2;
    TLS1.3.
  • ipVersion: Filter by IP version. Valid values are as follows:
    4: IPv4;
    6: IPv6.
  • cacheType: Filter by cache status. Valid values are as follows:
    hit: The request hits the EdgeOne node cache and the resources are provided by the node cache. A partial cache hit for resources is also recorded as hit.
    miss: The request does not hit the EdgeOne node cache and the resources are provided by the origin server.
    dynamic: The requested resources cannot be cached or are not configured with node cache and are provided by the origin server.
    other: unrecognizable cache status. Requests responded to by edge functions are recorded as other.
  • clientIp: Filter by client IP.
    		•
    Area No String Data region. Valid values:
  • overseas: global (excluding the Chinese mainland) data;
  • mainland: Chinese mainland data;
  • global: global data.

    • If this parameter is not filled in, the default value is global.

    3. Output Parameters

    Parameter Name Type Description
    TotalCount Integer Total number of query results.
    Data Array of TimingDataRecord The list of L7 traffic data recorded over time.
    Note: This field may return null, indicating that no valid values can be obtained.
    RequestId String The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem.

    4. Example

    Example1 Querying the Time Series Data of the Request Count by HTTP Protocol Version

    This example shows you how to query the request count metric data by HTTP protocol version.

    Input Example

    POST / HTTP/1.1
Host: teo.tencentcloudapi.com
Content-Type: application/json
X-TC-Action: DescribeTimingL7AnalysisData
<Common request parameters>

{
    "EndTime": "2022-08-29T19:17:59+08:00",
    "Interval": "day",
    "Area": "mainland",
    "StartTime": "2022-07-31T00:00:00+08:00",
    "MetricNames": [
        "l7Flow_request"
    ],
    "Filters": [
        {
            "Key": "protocol",
            "Operator": "equals",
            "Value": [
                "HTTP/1.0",
                "HTTP/1.1"
            ]
        }
    ],
    "ZoneIds": [
        "zone-2o7b38ba1hvr"
    ]
}

    Output Example

    {
    "Response": {
        "RequestId": "141a7ccd-9713-43a2-91d5-1b47692d0609",
        "Data": [
            {
                "TypeKey": "251227260",
                "TypeValue": [
                    {
                        "Avg": 803,
                        "Detail": [
                            {
                                "Timestamp": 1659139200,
                                "Value": 0
                            },
                            {
                                "Timestamp": 1661731200,
                                "Value": 0
                            }
                        ],
                        "Max": 7921,
                        "MetricName": "l7Flow_request",
                        "Sum": 24918
                    }
                ]
            }
        ],
        "TotalCount": 1
    }
}

    5. Developer Resources

    SDK

    TencentCloud API 3.0 integrates SDKs that support various programming languages to make it easier for you to call APIs.

    Command Line Interface

    6. Error Code

    The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.

    Error Code Description
    FailedOperation Operation failed.
    InternalError.ProxyServer An unknown error occurred in the backend server.
    InvalidParameter Parameter error.
    InvalidParameterValue Invalid parameter value.
    LimitExceeded The quota limit has been reached.
    LimitExceeded.QueryTimeLimitExceeded Query time limit exceeded.
    OperationDenied Operation denied.
    ResourceNotFound The resource doesn’t exist.
    ResourceUnavailable The resource is unavailable.
    UnauthorizedOperation.CamUnauthorized CAM is not authorized.
    Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
    Privacy PolicyLegalCookie Policy