- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Description of 14-day Trial Plan Experience Benefits
- Billing Overview
- Basic Service Fees
- Value-added Service Fees
- Related Tencent Cloud Services
- Extra Package Description (Prepaid)
- Subscriptions
- Renewals
- Overdue and Expiration Policies
- Refund Policy
- Usage Cap Policy
- EdgeOne Plan Upgrade Guide
- Comparison of EdgeOne Plans
- Billing Usage
- About "clean traffic" billing instructions
- Getting Started
- Domain Service
- Site Acceleration
- Origin Configuration
- Edge Functions
- Overview
- Getting Started
- Operation Guide
- Runtime APIs
- Sample Functions
- Example Overview
- 301 Redirect
- Obtaining Client URL Information
- Customization Based on Client Geo Location
- Obtaining Client Geo Location Information
- Batch Redirect
- Returning an HTML Page
- Returning a JSON Object
- Fetch Remote Resources
- Authenticating a Request Header
- Modifying a Response Header
- Performing an A/B Test
- Setting Cookies
- Performing Redirect Based on the Request Location
- Using the Cache API
- Caching POST Requests
- Responding in Streaming Mode
- Merging Resources and Responding in Streaming Mode
- Protecting Data from Tampering
- Rewriting a m3u8 File and Configuring Authentication
- Adaptive Image Resize
- Image Adaptive WebP
- Customize Referer restriction rules
- Remote Authentication
- HMAC Digital Signature
- Naming a Downloaded File
- Obtaining Client IP Address
- Practical Tutorial
- Security Protection
- Overview
- DDoS Protection
- DDoS Protection Overview
- Exclusive DDoS Protection Usage
- Configuration of Exclusive DDoS protection Rules
- Web Protection
- Rules Template
- IP Groups
- Origin Protection
- Custom Response Page
- Alarm Notification
- Rule Engine
- L4 Proxy
- Data Analysis&Log Service
- Tool Guide
- Practical Tutorial
- Configuring EdgeOne Security Event Alarms via TCOP
- EdgeOne Resource Abuse Prevention
- EdgeOne Implementation of Session Persistence Based on Client IP Addresses
- EdgeOne Implementation of Origin-Pull Based on Client's Geo Location
- EdgeOne Hotlink Protection Practical Tutorial
- EdgeOne initiates Automatic Warm-up
- EdgeOne Automatic Cache Purge
- Cross-regional Secure Acceleration (Oversea Sites)
- Scheduling Traffic to EdgeOne by Performing Canary Switching
- Quickly Enabling HTTPS Access with EdgeOne Free Certificate
- Through traffic orchestration to multiple service providers
- EdgeOne facilitate APKs.s dynamic packaging of Android
- 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
- CreateL4Proxy
- ModifyL4Proxy
- ModifyL4ProxyStatus
- DescribeL4Proxy
- DeleteL4Proxy
- CreateL4ProxyRules
- ModifyL4ProxyRules
- ModifyL4ProxyRulesStatus
- DescribeL4ProxyRules
- DeleteL4ProxyRules
- CreateApplicationProxy
- ModifyApplicationProxy
- ModifyApplicationProxyStatus
- DescribeApplicationProxies
- DeleteApplicationProxy
- CreateApplicationProxyRule
- ModifyApplicationProxyRule
- ModifyApplicationProxyRuleStatus
- DeleteApplicationProxyRule
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- Version Management APIs
- Data Types
- Error Codes
- FAQs
- Agreements
- TEO Policy
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Description of 14-day Trial Plan Experience Benefits
- Billing Overview
- Basic Service Fees
- Value-added Service Fees
- Related Tencent Cloud Services
- Extra Package Description (Prepaid)
- Subscriptions
- Renewals
- Overdue and Expiration Policies
- Refund Policy
- Usage Cap Policy
- EdgeOne Plan Upgrade Guide
- Comparison of EdgeOne Plans
- Billing Usage
- About "clean traffic" billing instructions
- Getting Started
- Domain Service
- Site Acceleration
- Origin Configuration
- Edge Functions
- Overview
- Getting Started
- Operation Guide
- Runtime APIs
- Sample Functions
- Example Overview
- 301 Redirect
- Obtaining Client URL Information
- Customization Based on Client Geo Location
- Obtaining Client Geo Location Information
- Batch Redirect
- Returning an HTML Page
- Returning a JSON Object
- Fetch Remote Resources
- Authenticating a Request Header
- Modifying a Response Header
- Performing an A/B Test
- Setting Cookies
- Performing Redirect Based on the Request Location
- Using the Cache API
- Caching POST Requests
- Responding in Streaming Mode
- Merging Resources and Responding in Streaming Mode
- Protecting Data from Tampering
- Rewriting a m3u8 File and Configuring Authentication
- Adaptive Image Resize
- Image Adaptive WebP
- Customize Referer restriction rules
- Remote Authentication
- HMAC Digital Signature
- Naming a Downloaded File
- Obtaining Client IP Address
- Practical Tutorial
- Security Protection
- Overview
- DDoS Protection
- DDoS Protection Overview
- Exclusive DDoS Protection Usage
- Configuration of Exclusive DDoS protection Rules
- Web Protection
- Rules Template
- IP Groups
- Origin Protection
- Custom Response Page
- Alarm Notification
- Rule Engine
- L4 Proxy
- Data Analysis&Log Service
- Tool Guide
- Practical Tutorial
- Configuring EdgeOne Security Event Alarms via TCOP
- EdgeOne Resource Abuse Prevention
- EdgeOne Implementation of Session Persistence Based on Client IP Addresses
- EdgeOne Implementation of Origin-Pull Based on Client's Geo Location
- EdgeOne Hotlink Protection Practical Tutorial
- EdgeOne initiates Automatic Warm-up
- EdgeOne Automatic Cache Purge
- Cross-regional Secure Acceleration (Oversea Sites)
- Scheduling Traffic to EdgeOne by Performing Canary Switching
- Quickly Enabling HTTPS Access with EdgeOne Free Certificate
- Through traffic orchestration to multiple service providers
- EdgeOne facilitate APKs.s dynamic packaging of Android
- 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
- CreateL4Proxy
- ModifyL4Proxy
- ModifyL4ProxyStatus
- DescribeL4Proxy
- DeleteL4Proxy
- CreateL4ProxyRules
- ModifyL4ProxyRules
- ModifyL4ProxyRulesStatus
- DescribeL4ProxyRules
- DeleteL4ProxyRules
- CreateApplicationProxy
- ModifyApplicationProxy
- ModifyApplicationProxyStatus
- DescribeApplicationProxies
- DeleteApplicationProxy
- CreateApplicationProxyRule
- ModifyApplicationProxyRule
- ModifyApplicationProxyRuleStatus
- DeleteApplicationProxyRule
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- Version Management APIs
- Data Types
- Error Codes
- FAQs
- Agreements
- TEO Policy
- Contact Us
- Glossary
Overview
The Billing Usage page of EdgeOne provides usage data for billing items, allowing you to estimate fees based on this data before actual billing. After billing, you can view the bill details in the Tencent Cloud Billing Center console. You can also view more detailed usage reports on this page and filter by resource tag, billing region, package, site, domain, and L4 proxy instance. This document explains the relationship between the component name fields in the Tencent Cloud Billing Center's detailed bill and the metric names on the EdgeOne Billing Usage page.
Note
1. The data displayed on the Billing Usage page may differ from that on other pages (Traffic Analysis, Service Overview, and Site Overview). If you are concerned with fees-related issues, it is recommended to refer to the Billing Usage page. The relationships among the various data provided by EdgeOne are as follows:
Tencent Cloud billing usage data = Data displayed on the Billing Usage page ≈ Data displayed on the Traffic Analysis, Service Overview, and Site Overview Pages > Data calculated using raw logs.The explanation for the differences between billing usage data and the data in logs can be found in Why are the traffic data in the console and the traffic data derived from logs inconsistent?
2. Due to latency and algorithm impacts, the data on this page may have some latency and generally stabilizes after 2 hours.
Relationship Between Metrics on the Billing Usage Page and Billing Items
For Personal/Basic/Standard Edition Users
Component Name Field in Tencent Cloud Billing Center Detailed Bill | Metric Name Displayed on EdgeOne Billing Usage Page | Billing Standard |
SCDN - Traffic - Hourly Settlement | Corresponds to the total usage generated by the following services: Content acceleration traffic: L7 (application layer) traffic generated by all domains when Smart Acceleration is not enabled; only downstream traffic is counted; Smart acceleration traffic: L7 (application layer) traffic generated by all domains when Smart Acceleration is enabled; both upstream and downstream traffic is counted. | |
HTTP/HTTPS Security Requests - Hourly Settlement | HTTP/HTTPS Requests: Application layer requests generated by all domains, regardless of protocol or whether they are static or dynamic requests. | |
Value-Added Service Usage Unit - Hourly Settlement | Corresponds to the total value-added service usage units generated by the following value-added services: Smart Acceleration Requests: HTTP/HTTPS requests generated by domains with Smart Acceleration enabled; QUIC Requests: Requests using the QUIC protocol generated by domains with HTTP/3 (QUIC) enabled; Bot Requests: HTTP/HTTPS requests generated by domains with Bot management enabled; |
For Enterprise Edition Users
Component Name Field in Tencent Cloud Billing Center Detailed Bill | Metric Name Displayed on EdgeOne Billing Usage Page | Billing Standard |
L7 content acceleration - Traffic | Content acceleration traffic: L7 (application layer) traffic generated by all domains when Smart Acceleration is not enabled; only downstream traffic is counted. | |
L7 smart acceleration - Traffic | Smart acceleration traffic: L7 (application layer) traffic generated by all domains when Smart Acceleration is enabled; both upstream and downstream traffic is counted. | |
L4 acceleration - Traffic | L4 acceleration traffic: The sum of L4 (transport layer) upstream and downstream traffic generated by all L4 proxy instances. | |
Exclusive DDoS Protection - Traffic | Exclusive protection traffic: Business traffic generated by domains/L4 proxy instances with Exclusive DDoS Protection enabled. | |
Chinese Mainland Network Optimization - Traffic | Cross-MLC-border acceleration traffic: Business traffic generated by sites/L4 proxy instances with the Cross-MLC-border Acceleration feature enabled. | |
HTTP/HTTPS Security Requests - Monthly Settlement | HTTP/HTTPS Requests: Application layer requests generated by all domains, regardless of protocol or whether they are static or dynamic requests. | |
Value-Added Service Usage Unit - Monthly Settlement | Corresponds to the total value-added service usage units generated by the following value-added services: Smart Acceleration Requests: HTTP/HTTPS requests generated by domains with Smart Acceleration enabled; QUIC Requests: Requests using the QUIC protocol generated by domains with HTTP/3 (QUIC) enabled; Bot Requests: HTTP/HTTPS requests generated by domains with Bot management enabled; | |
Exclusive DDoS Protection - Elastic Protection Bandwidth Package | Elastic DDoS Protection Bandwidth: The part of attack bandwidth exceeding the guaranteed protection bandwidth generated by exclusive DDoS protection instances within Chinese mainland. |
Supported Filter Criteria
Selecting the time period for data queries is supported. You can query data from February 9, 2022 onwards on this page, with a maximum single filter duration of 31 days.
Filtering based on the following criteria is supported, with an "and" relationship between multiple conditions:
Billing region: Filter by the billing region of the traffic, which is the region where the EdgeOne node serving user clients is located. For details, see Mapping Relationship Between Billing Regions and Countries.
Site tag: Filter by the resource tag key-value pairs bound to the site.
EdgeOne billing package: Filter by all sites included in the package.
Site: Filter by specified site, including sites deleted within the last 3 months.
Acceleration domain: Filter by specified acceleration domain, and cannot simultaneously add L4 proxy instance filter criterion.
L4 proxy instance: Filter by L4 proxy instance, and cannot simultaneously add acceleration domain filter criterion.
Example: Querying Billing Usage for Sites Bound with Specified Tags
Sample Scenario
Tencent Cloud Tag feature provides a flexible resource management method. By tagging cloud resources, users can more easily organize, search, and manage their resources on Tencent Cloud. If a company has deployed multiple projects on Tencent Cloud, to improve the efficiency and accuracy of resource management, the company classifies existing cloud resources. Based on dimensions such as projects, environments (such as development, testing, and production), and cost centers, the company plans a tag system. For example, for the project dimension, the company can set the tag key as
Project and the tag value as the specific project name; for the environment dimension, set the tag key as Environment and the tag value as Dev, Test, Prod, or other values. According to the planned tag system, the company tags the existing resources using the EdgeOne console or APIs. For example, a site belonging to project A and in the development environment would be tagged with Project: Project A and Environment: Dev. After the current billing cycle ends and the bill is issued, the company wants to review the billing usage by tag for the previous billing cycle.Directions
1. Log in to the EdgeOne console, and click Billing Management > Billing Usage in the left sidebar.
2. On the Billing Usage page, click Last month to quickly filter data from 00:00 on the 1st day of last month to 23:59 on the last day.
3. Click Select site tags, choose the Tag Key and Tag Value you want to view, such as
Project: Project A and Environment: Dev, and click OK.
4. The page will automatically display all sites bound with the selected tag key-value pairs. You can view or download the billing usage of these sites.
APIs
Yes
No
Was this page helpful?