tencent cloud

Serverless Cloud Function

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Related Concepts
How It Works
Strengths
Scenarios
Related Products
Purchase Guide
Billing Overview
Billing Mode
Billable Items and Billing Modes
Function Computing Power Support
Free Tier
SCF Pricing
Billing Example
Payment Overdue
Getting Started
Creating Event Function in Console
User Guide
Quota Management
Managing Functions
Web Function Management
Log Management
Concurrence Management
Trigger Management
Function URL
A Custom Domain Name
Version Management
Alias Management
Permission Management
Running Instance Management
Plugin Management
Managing Monitors and Alarms
Network Configuration
Layer Management
Execution Configuration
Extended Storage Management
DNS Caching Configuration
Resource Managed Mode Management
Near-Offline Resource Hosting Model
Workflow
Triggers
Trigger Overview
Trigger Event Message Structure Summary
API Gateway Trigger
COS Trigger
CLS Trigger
Timer Trigger
CKafka Trigger
Apache Kafka Trigger
MQTT Trigger
Trigger Configuration Description
MPS Trigger
CLB Trigger Description
TencentCloud API Trigger
Development Guide
Basic Concepts
Testing a Function
Environment Variables
Dependency Installation
Using Container Image
Error Types and Retry Policies
Dead Letter Queue
Connecting SCF to Database
Automated Deployment
Cloud Function Status Code
Common Errors and Solutions
Developer Tools
Serverless Web IDE
Calling SDK Across Functions
Third-Party Tools
Code Development
Python
Node.js
Golang
PHP
Java
Custom Runtime
Deploying Image as Function
Web Framework Development
Deploying Framework on Command Line
Quickly Deploying Egg Framework
Quickly Deploying Express Framework
Quickly Deploying Flask Framework
Quickly Deploying Koa Framework
Quickly Deploying Laravel Framework
Quickly Deploying Nest.js Framework
Quickly Deploying Next.js Framework
Quickly Deploying Nuxt.js Framework
Quickly Deploying Django Framework
Use Cases
Overview
Solutions with Tencent Cloud Services
Business Development
TRTC Practices
COS Practices
CKafka Practice
CLS
CLB Practice
MPS
CDN
CDWPG
VOD
SMS
ES
Scheduled Task
Video Processing
Success Stories
Tencent Online Education
Online Video Industry
Tencent Online Education
Best Practice of Tencent IEG Going Global
API Documentation
History
Introduction
API Category
Making API Requests
Other APIs
Namespace APIs
Layer Management APIs
Async Event Management APIs
Trigger APIs
Function APIs
Function and Layer Status Description
Data Types
Error Codes
SDK Documentation
FAQs
General
Web Function
Billing FAQs
Network FAQs
Log FAQs
SCF utility class
Event Handling FAQs
API Gateway Trigger FAQs
Related Agreement
Service Level Agreement
Contact Us
Glossary

Instance Level Monitoring

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2025-06-17 16:37:33

Feature Overview

The function platform now supports the "instance-level monitoring" feature. Through instance-level metrics, you can view core metric information such as vCPU usage, memory usage, and instance network conditions. This article introduces the use cases, definitions, metric information, and configuration methods of instance-level metrics.

Use Cases

Monitor CPU, memory, and network metrics of a single instance in real-time to accurately diagnose resource usage and identify matching issues between specification and workload.
Continuously track the instance lifecycle status, fully record key events such as startup, destruction, and abnormal exit, and ensure the observability of running health status;
Based on multidimensional data correlation analysis, quickly locate the root cause of failures, effectively distinguish between code defects and environment-related issues, and provide a basis for decision-making for failure recovery;

Instance-Level Monitoring Metric Descriptions

Instance-level metrics are performance metrics at the function instance dimension. They perform real-time monitoring and performance data collection on function instances, provide visual displays, and offer you an end-to-end monitoring and troubleshooting path for function instances.
Instance-level metrics support the following dimensionalities.
Instance dimension: Metrics of a specific certain function instance.
Function dimension or function version / Alias dimension: Refers to the aggregation performed by the function dimension. For example, if there are two instances of Function A executing at the same time, then the vCPU metric in the function dimension is the maximum value of vCPU usage among these two instances (awaiting release).
Metric Meaning
Meaning of Metric
Unit
Dimension

vcpu usage
Instance vCPU consumption. (vCPU quota, maximum vCPU, average vCPU)
vcpu
Instance Dimension
vcpu utilization
vCPU usage. Represent the actual number of vCPUs in use, which may exceed 100%. (Maximum utilization, Average utilization rate)

%
Instance Dimension

Memory Usage
Consumed memory of the instance. Unit: MB. (Memory quota, Maximum used memory, Average used memory)
MB
Instance Dimension
Memory Usage
Memory Utilization Rate. That is, actual consumed memory/total memory (Maximum Utilization Rate, Average Utilization Rate)
%
Instance Dimension

Network Traffic
Inbound Traffic
Traffic received by the cloud function instance since its start-up
Outbound Traffic
Traffic sent by the cloud function instance since its start-up
KBytes
Instance Dimension
Bandwidth
Inbound Bandwidth
Traffic bandwidth received by the cloud function instance since its start-up
Outbound Bandwidth
Traffic bandwidth sent by the cloud function instance since its start-up

Mbps
Instance Dimension

Configure Instance-Level Metrics

1. Log in to the SCF console and select Function Service in the left sidebar.
2. On the list page of "Function Service", enable log delivery when creating/updating a function.

3. Perform code testing, trigger a function call.
4. On the Function Management page, select Running Instances, click Monitoring.

5. In the pop-up, you can check corresponding monitoring metrics. Click in the upper right corner to configure alarms.



도움말 및 지원

문제 해결에 도움이 되었나요?

피드백