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
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

Console

PDF
Focus Mode
Font Size
Last updated: 2025-08-01 14:31:48
Designed based on the Web APIs standard Console API. The edge function runtime can use the console object to output debugging information and logs. The output content can be viewed and analyzed through web debugging operations, or the real-time log push feature can be used to achieve long-term log retention and query analysis.

Description

console.log(val1)
console.log(val1, /* …, */ valN)
console object's other methods (info(), notice(), warn(), error(), debug()) have the same syntax format.

Parameter

Parameter Name
Type
Required
Description
val1
string | number | null | undefined | boolean | object | Symbol | Array<[string, string]> | Function
No
The first value to output.
valN
string | number | null | undefined | boolean | object | Symbol | Array<[string, string]> | Function
No
Other values to output.
Note:
In edge functions, the content output by console can be retained and analyzed through the real-time log push feature for long-term log retention and query analysis.
1. In Function logs, console supports four levels: info, notice, warn, and error. console.log() corresponds to the info level.
2. In edge functions, custom log output content other than log, info, notice, warn, and error will not be recorded in Function logs.
3. The size limit for a single real-time log is 40KB, and the console output content size limit is 4KB. Exceeding the limit will result in truncation.
Note:
1. In a single edge function, it is recommended to limit each console content length to 8k characters.
2. In a single edge function, the Web debugging page displays a maximum of 20 console outputs per request. Any console output exceeding 20 will not be shown on the debugging page.

Example Code

function handleEvent(event) {
const { request } = event;
const url = new URL(request.url);

// Output basic information
console.log('Process request:', url.pathname);

// Output prompt message
console.info('Request processing started');

// Output attention information
console.notice('Request processing method:', request.method);

// Output warning information
console.warn('Request parameters may be incomplete');

// Output error information
console.error('Error occurred while processing the request');

return event.respondWith(new Response('Hello World'));
}

addEventListener('fetch', event => {
handleEvent(event);
});

Sample Preview



Related Reference




Help and Support

Was this page helpful?

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

Feedback