tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery(Beta)
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
L4 Proxy
Overview
Creating an L4 Proxy Instance
Modifying an L4 Proxy Instance
Disabling or Deleting an L4 Proxy Instance
Batch Configuring Forwarding Rules
Obtaining Real Client IPs
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
EdgeOne Skill User Guide
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

DescribeTopL7AnalysisData

PDF
Focus Mode
Font Size
Last updated: 2026-01-13 21:51:46

1. API Description

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

This API is used to query the top N data of the L7 domain name business by specified dimension.
Create and bind policy Query instance Reset instance access password.
This API is used to query data with a delay of about 10 minutes. It is recommended to pull data from at least 10 minutes before the current time.
This API is used to return post-protection traffic request data by default. Users can query defended data in Filters.mitigatedByWebSecurity.

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: DescribeTopL7AnalysisData.
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 End time. The query time range (EndTime - StartTime) must be less than or equal to 31 days.
MetricName Yes String Queried metric. Valid values:
  • l7Flow_outFlux_country: specifies the l7 EdgeOne response traffic metric counted by the country/region dimension.
  • l7Flow_outFlux_province: specifies the l7 EdgeOne response traffic metric counted by the dimension of provinces in chinese mainland.
  • l7Flow_outFlux_statusCode: specifies the l7 EdgeOne response traffic metric by status code dimension.
  • l7Flow_outFlux_domain: specifies the l7 EdgeOne response traffic metric counted by domain name dimension.
  • l7Flow_outFlux_url: specifies the l7 EdgeOne response traffic metric counted by url Path dimension.
  • l7Flow_outFlux_resourceType: specifies the l7 EdgeOne response traffic metric counted by resource type dimension.
  • l7Flow_outFlux_sip: specifies the l7 EdgeOne response traffic metric counted by the client IP dimension.
  • l7Flow_outFlux_referers: specifies the l7 EdgeOne response traffic statistics by Referer dimension.
  • l7Flow_outFlux_ua_device: specifies the l7 EdgeOne response traffic metric counted by device type dimension.
  • l7Flow_outFlux_ua_browser: specifies the l7 EdgeOne response traffic metric by browser type dimension.
  • l7Flow_outFlux_ua_os: specifies the l7 EdgeOne response traffic metric counted by the operating system type dimension.
  • l7Flow_outFlux_ua: specifies the l7 EdgeOne response traffic metric by User-Agent dimension statistics.
  • l7Flow_request_country: specifies the l7 access request count metric by country/region dimension.
  • l7Flow_request_province: specifies the l7 access request count metric by province in the chinese mainland.
  • l7Flow_request_statusCode: specifies the l7 access request count metric by status code dimension.
  • l7Flow_request_domain: specifies the l7 access request count metric counted by the domain name dimension.
  • l7Flow_request_url: specifies the l7 access request count metric counted by url Path dimension.
  • l7Flow_request_resourceType: specifies the l7 access request count metric counted by the resource type dimension.
  • l7Flow_request_sip: specifies the l7 access request count metric counted by the client IP dimension.
  • l7Flow_request_referers: specifies l7 access request count metrics by referer dimension.
  • l7Flow_request_ua_device: specifies the l7 access request count metric by device type dimension.
  • l7Flow_request_ua_browser: specifies the l7 access request count metric by browser type dimension.
  • l7Flow_request_ua_os: specifies the l7 access request count metric counted by the operating system type dimension.
  • l7Flow_request_ua: l7 access request count metric counted by the User-Agent dimension.
  • ZoneIds.N Yes Array of String Site ID set. this parameter will change from option to required after may 30, 2024. for details, see the notice: tencent cloud EdgeOne API change notification. a maximum of 100 site ids can be imported. use * to query all site data under the tencent cloud root account. querying account-level data requires all resource permissions for all sites in this interface.
    Limit No Integer Indicates the top N data to be queried. The maximum value is 1000. If this parameter is not input, the default value is 10, indicating querying the top 10 data.
    Filters.N No Array of QueryCondition Filter criteria used when filtering data. valid values refer to the available filter options for L7 access traffic, bandwidth, and request count in the metric analysis filtering condition description.
    If needed, limit the site or content identifier by importing the corresponding value in the ZoneIds.N parameter.
    Interval No String Query time granularity. this parameter is invalid. to be deprecated.
    Area No String Data ownership region. this parameter is deprecated. please filter data by client region in Filters.country.

    3. Output Parameters

    Parameter Name Type Description
    TotalCount Integer Total number of query results.
    Data Array of TopDataRecord The top N data list obtained from the statistics of L7 access data by a specified dimension MetricName.
    Note: This field may return null, which indicates a failure to obtain a valid value.
    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 Traffic Data of the Top URL Path Under a Specific HTTP Protocol Version

    This example shows you how to query the traffic data of the top URL path under a specific HTTP protocol version (HTTP/1.0 or HTTP/1.1).

    Input Example

    POST / HTTP/1.1
    Host: teo.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: DescribeTopL7AnalysisData
    <Common request parameters>
    
    {
        "Area": "mainland",
        "Interval": "day",
        "Limit": "1",
        "StartTime": "2022-07-31T00:00:00+08:00",
        "EndTime": "2022-08-29T19:17:59+08:00",
        "MetricName": "l7Flow_outFlux_url",
        "Filters": [
            {
                "Key": "protocol",
                "Operator": "equals",
                "Value": [
                    "HTTP/1.0",
                    "HTTP/1.1"
                ]
            }
        ],
        "ZoneIds": [
            "zone-2mzegj4vln5f"
        ]
    }

    Output Example

    {
        "Response": {
            "RequestId": "7c499897-8ad9-4a2d-884e-6154f283d723",
            "Data": [
                {
                    "DetailData": [
                        {
                            "Key": "path",
                            "Value": 1210001
                        }
                    ],
                    "TypeKey": "251227260"
                }
            ],
            "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.
    UnauthorizedOperation.NoPermission The sub-account is not authorized for the operation. Please get permissions first.

    Help and Support

    Was this page helpful?

    Help us improve! Rate your documentation experience in 5 mins.

    Feedback