By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permissions policies to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on FunctionGraph based on the permissions.
LTS
|
lts:groups:create
diff --git a/docs/fg/umn/functiongraph_01_0180.html b/docs/fg/umn/functiongraph_01_0180.html
index 4e9cdccca..8581f29e9 100644
--- a/docs/fg/umn/functiongraph_01_0180.html
+++ b/docs/fg/umn/functiongraph_01_0180.html
@@ -1,6 +1,6 @@
-Managing Versions
+Configuring Versions
OverviewFunctionGraph allows you to publish one or more versions throughout the development, test, and production processes to manage your function code. The code and environment variables of each version are saved as a snapshot. After the function code is published, you can modify settings as required.
After a function is created, the default version is latest. Each function has the latest version. After the function code is published, you can modify the version configuration as required.
 A version is a snapshot of a function and corresponds to a tag in code. Each version contains the configuration and code of the function. By default, no trigger is bound to a new version. After a version is published, the configuration (such as environment variables) and code of the version cannot be updated, to ensure stability and traceability.
diff --git a/docs/fg/umn/functiongraph_01_0200.html b/docs/fg/umn/functiongraph_01_0200.html
index ebc25947a..1a6019dde 100644
--- a/docs/fg/umn/functiongraph_01_0200.html
+++ b/docs/fg/umn/functiongraph_01_0200.html
@@ -1,6 +1,6 @@
- Creating Triggers
+ Configuring Triggers
@@ -14,8 +14,6 @@
- Using a Kafka Trigger
-- Using a DIS Trigger
-
- Using an SMN Trigger
- Using an LTS Trigger
diff --git a/docs/fg/umn/functiongraph_01_0200_0.html b/docs/fg/umn/functiongraph_01_0200_0.html
index 853ba327c..ee7e4542e 100644
--- a/docs/fg/umn/functiongraph_01_0200_0.html
+++ b/docs/fg/umn/functiongraph_01_0200_0.html
@@ -2,7 +2,7 @@
Product Features
Function ManagementFunctionGraph provides console-based function management.
- - The Node.js, Java, Python, Go, PHP, and custom runtimes are supported. Table 1 provides the details.
You are advised to use the latest runtime version.
+ - The Node.js, Java, Python, Go, C#, PHP, and custom runtimes are supported. Table 1 provides the details.
You are advised to use the latest runtime version.
Table 1 RuntimesRuntime
@@ -13,37 +13,37 @@
|
|---|
Node.js
|
-6.10, 8.10, 10.16, 12.13, 14.18, 16.17, 18.15, 20.15
+ | 6.10, 8.10, 10.16, 12.13, 14.18, 16.17, 18.15, 20.15
|
Python
|
-2.7, 3.6, 3.9, 3.10, 3.12
+ | 2.7, 3.6, 3.9, 3.10, 3.12
|
Java
|
-8.0, 11, 17, 21
+ | 8, 11, 17, 21
|
Go
|
-1.x
+ | 1.x
|
C#
|
-.NET Core 2.1, .NET Core 3.1, .NET Core 6.0
+ | .NET Core 2.1, .NET Core 3.1, .NET Core 6.0
|
PHP
|
-7.3, 8.3
+ | 7.3, 8.3
|
Custom
|
--
+ | -
|
@@ -129,7 +129,7 @@
Supported
|
-Custom
+ | Custom
|
Supported
|
@@ -145,74 +145,59 @@
-TriggerTable 3 lists the invocation modes for different trigger types.
+ Function TriggersTable 3 lists the invocation modes for different trigger types.
- Table 3 Function invocation modesTrigger
+Table 3 Function trigger invocationTrigger
|
-Function Invocation Mode
+ | Invocation Mode
|
|---|
-SMN trigger
+ | API Gateway (Dedicated)
|
-Asynchronous invocation
+ | Synchronous invocation is used by default. You can change it to asynchronous invocation. For details, see Asynchronous Invocation.
|
-APIG trigger
+ | Timer
|
-Synchronous invocation
+ | Synchronous (default)
|
-OBS trigger
+ | Cloud Trace Service (CTS)
|
-Asynchronous invocation
+ | Asynchronous (default and cannot be changed)
|
-Data Ingestion Service (DIS) trigger
+ | Document Database Service (DDS)
|
-Asynchronous invocation
+ | Asynchronous (default and cannot be changed)
|
-Timer trigger
+ | DMS (for Kafka)
|
-Asynchronous invocation
+ | Asynchronous (default and cannot be changed)
|
-Log Tank Service (LTS) trigger
+ | Kafka (Open-Source)
|
-Asynchronous invocation
+ | Asynchronous (default and cannot be changed)
|
-Cloud Trace Service (CTS) trigger
+ | Log Tank Service (LTS)
|
-Asynchronous invocation
+ | Asynchronous (default and cannot be changed)
|
-Document Database Service (DDS) trigger
+ | Simple Message Notification (SMN)
|
-Asynchronous invocation
- |
-
-Kafka trigger
- |
-Asynchronous invocation
- |
-
-Distributed Message Service (DMS) for Kafka
- |
-Synchronous invocation
- |
-
-Distributed Message Service (DMS) for RocketMQ
- |
-Synchronous invocation
+ | Asynchronous (default and cannot be changed)
|
Logs and MetricsFunctionGraph graphically displays function monitoring metrics and collects function running logs, enabling you to view function statuses, and locate problems by querying logs.
+ Logs and MetricsFunctionGraph graphically displays function monitoring metrics and collects function running logs, enabling you to view function statuses, and locate problems by querying logs.
For details about how to query logs, see Managing Function Logs.
For details about a single monitoring metric, see section "Function Monitoring" in the FunctionGraph User Guide.
For details about tenant-level monitoring information, see Introduction to Dashboard.
@@ -220,7 +205,7 @@
Function InitializationThe initializer interface is introduced to:
- Isolate function initialization and request processing to enable clearer program logic and better structured and higher-performance code.
- Ensure smooth function upgrade to prevent performance loss during the application layer's cold start initialization. Enable new function instances to automatically execute initialization logic before processing requests.
- Identify the overhead of application layer initialization, and accurately determine the time for resource scaling and the quantity of required resources. This feature makes request latency more stable when the application load increases and more function instances are required.
- HTTP FunctionsYou can set Function Type to HTTP Function on the function creation page. HTTP functions are designed to optimize web services. You can send HTTP requests to URLs to trigger function execution. HTTP functions support APIG and API Connect (APIC) triggers only.
+ HTTP FunctionsYou can set Function Type to HTTP Function on the function creation page. HTTP functions are designed to optimize web services. You can send HTTP requests to URLs to trigger function execution. HTTP functions support APIG triggers only.
Custom ImagesYou can directly package and upload container images. The images are loaded and started by the platform and can be called in a similar way as HTTP functions. Unlike the previous code upload mode, you can use a custom code package, which is flexible and reduces migration costs.
diff --git a/docs/fg/umn/functiongraph_01_0201.html b/docs/fg/umn/functiongraph_01_0201.html
index fcd91e601..9eb83582a 100644
--- a/docs/fg/umn/functiongraph_01_0201.html
+++ b/docs/fg/umn/functiongraph_01_0201.html
@@ -36,7 +36,7 @@
|
|---|
- - Set the initializer in the same way as the handler. For example, for a Node.js or Python function, set an initializer name in the format of [file name].[initialization function name].
- For details about the function code configuration, see Creating a Deployment Package.
+ - Set the initializer in the same way as the handler. For example, for a Node.js or Python function, set an initializer name in the format of [file name].[initialization function name].
- For details about the function code configuration, see Configuring Code.
diff --git a/docs/fg/umn/functiongraph_01_0202.html b/docs/fg/umn/functiongraph_01_0202.html
index 73aaf2775..e07d1bc45 100644
--- a/docs/fg/umn/functiongraph_01_0202.html
+++ b/docs/fg/umn/functiongraph_01_0202.html
@@ -3,7 +3,7 @@
Using an SMN Trigger
This section describes how to create an SMN trigger and publish a message to trigger a function.
For details about the SMN event source, see section "Supported Event Sources".
- Prerequisites
+
Creating an SMN Trigger- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Triggers and click Create Trigger.
Figure 1 Creating a trigger
- Set the following parameters:
- Trigger Type: Select Simple Message Notification (SMN).
- Topic Name: Select a topic, for example, smn-test.
@@ -11,7 +11,7 @@
- Publishing a Message to Trigger the FunctionOn the SMN console, publish a message to the smn-test topic. For details, see Publishing a Text Message.
+ Publishing a Message to Trigger the FunctionOn the SMN console, publish a message to the smn-test topic. For details, see Publishing a Text Message.
Table 1 describes the parameters required for publishing a message.
Table 1 Parameters required for publishing a messageParameter
@@ -46,7 +46,7 @@
diff --git a/docs/fg/umn/functiongraph_01_0204.html b/docs/fg/umn/functiongraph_01_0204.html
index 84ec5e374..f43130cb1 100644
--- a/docs/fg/umn/functiongraph_01_0204.html
+++ b/docs/fg/umn/functiongraph_01_0204.html
@@ -76,6 +76,7 @@ def handler (event, context):
|
|---|
- Click OK.
Figure 2 Creating a trigger
+
- URL indicates the calling address of the APIG trigger.
- After the APIG trigger is created, an API named API_apig is generated on the APIG console. You can click the API name in the trigger list to go to the APIG console.
@@ -90,7 +91,7 @@ def handler (event, context):
diff --git a/docs/fg/umn/functiongraph_01_0205.html b/docs/fg/umn/functiongraph_01_0205.html
index c9452f5ef..1e3e46871 100644
--- a/docs/fg/umn/functiongraph_01_0205.html
+++ b/docs/fg/umn/functiongraph_01_0205.html
@@ -11,7 +11,7 @@
- Set the following parameters:
- Trigger Type: Select Object Storage Service (OBS).
- Bucket Name: Specify the OBS bucket to be used as an event source, for example, obs-cff.
- Events: Select events that will trigger the function. In this example, select Put, Post, and Delete. When files in the obs_cff bucket are updated, uploaded, or deleted, the function is triggered.
- Event Notification Name: Specify the name of the event notification to be sent by SMN when an event occurs.
- Prefix: Enter a keyword for limiting notifications to those about objects whose names start with the matching characters. This limit can be used to filter the names of OBS objects.
- Suffix: Enter a keyword for limiting notifications to those about objects whose names end with the matching characters. This limit can be used to filter the names of OBS objects.
- Click OK.
- Triggering a FunctionOn the OBS console, upload an image ZIP package to the obs-cff bucket. For details, see Uploading a File.
+ Triggering a FunctionOn the OBS console, upload an image ZIP package to the obs-cff bucket. For details, see Uploading a File.
After the ZIP package is uploaded to the obs-cff bucket, the HelloWorld function is triggered.
@@ -20,7 +20,7 @@
diff --git a/docs/fg/umn/functiongraph_01_0206.html b/docs/fg/umn/functiongraph_01_0206.html
deleted file mode 100644
index 360819305..000000000
--- a/docs/fg/umn/functiongraph_01_0206.html
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
- Using a DIS Trigger
- For details about the DIS event source, see section "Supported Event Sources".
- PrerequisitesBefore creating a trigger, ensure that you have prepared the following:
-
-
- Setting an AgencyBefore creating a DIS trigger, set an agency to delegate FunctionGraph to access DIS. For details on how to create an agency, see Configuring Agency Permissions.
- Since you did not specify an agency while creating the HelloWorld function, specify one first.
- - Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Permissions, and change the agency to serverless-trust created in Configuring Agency Permissions.
- Click Save.
-
- Creating a DIS Trigger- Return to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Triggers and click Create Trigger.
- Set the following parameters:
- Trigger Type: Select Data Ingestion Service (DIS).
- Stream Name: Select a DIS stream, for example, dis-function.
- Max. Fetch Bytes: Maximum volume of data that can be fetched in each request. Only the records smaller than this value will be fetched. The value ranges from 0 KB to 4 MB.
- Starting Position: Specify a position in the specified stream from which to start reading data.
- TRIM_HORIZON: Data is read from the earliest valid records that are stored in the partition.
- LATEST: Data is read just after the most recent record in the partition. This setting ensures that you always read the latest data.
- - Pull Period: Set a period for pulling data from the stream.
- Serial Data Processing: If this option is selected, FunctionGraph pulls data from the stream only after previous data is processed. If this option is not selected, FunctionGraph pulls data from the stream as long as the pull period ends.
- - Click OK.
-
- Configuring a DIS Event to Trigger the Function- Return to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- On the function details page, select a version.
- On the Code tab page, click Test. The Configure Test Event dialog box is displayed.
- Set the parameters described in Table 1 and click Save.
- Table 1 Test event informationParameter
- |
-Description
- |
-
|---|
-
-Configure Test Event
- |
-You can choose to create a test event or edit an existing one.
-Use the default option Create new test event.
- |
-
-Event Template
- |
-Select Data Ingestion Service (DIS) to use the built-in DIS event template.
- |
-
-Event Name
- |
-The event name can contain 1 to 25 characters and must start with a letter and end with a letter or digit. Only letters, digits, underscores (_), and hyphens (-) are allowed. For example, dis-123test.
- |
-
-Event data
- |
-The system automatically loads the built-in DIS event template, which is used in this example without modifications.
- |
-
-
-
- - Click Test. The function test result is displayed.
-
-
-
-
diff --git a/docs/fg/umn/functiongraph_01_0207.html b/docs/fg/umn/functiongraph_01_0207.html
index b45ecb6b4..9aa52aec9 100644
--- a/docs/fg/umn/functiongraph_01_0207.html
+++ b/docs/fg/umn/functiongraph_01_0207.html
@@ -5,7 +5,7 @@
Creating a Timer Trigger- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Triggers and click Create Trigger.
Figure 1 Creating a trigger
- Set the following parameters:
- Trigger Type: Select Timer.
- Timer Name: Enter a timer name, for example, Timer.
- Rule: Set a fixed rate or a cron expression.
- Fixed rate: The function is triggered at a fixed rate of minutes, hours, or days. You can set a fixed rate from 1 to 60 minutes, 1 to 24 hours, or 1 to 30 days.
- Cron expression: The function is triggered based on a complex rule. For example, you can set a function to be executed at 08:30:00 from Monday to Friday. For more information, see Cron Expressions for a Function Timer Trigger.
- - Enable Trigger: Choose whether to enable the timer trigger.
- Additional Information: The additional information you configure will be put into the user_event field of the timer event source.
+ - Enable Trigger: Choose whether to enable the timer trigger.
- Additional Information: The additional information you configure will be put into the user_event field of the timer event source.
- Click OK.
@@ -15,7 +15,7 @@
diff --git a/docs/fg/umn/functiongraph_01_0208.html b/docs/fg/umn/functiongraph_01_0208.html
index 8b8ab0f9f..cbd1d5d68 100644
--- a/docs/fg/umn/functiongraph_01_0208.html
+++ b/docs/fg/umn/functiongraph_01_0208.html
@@ -46,7 +46,7 @@
This section describes how to create a DDS trigger for a function, and invoke the function when a database table changes.
A function using a DDS trigger will be triggered every time a database table is updated. For details about the DDS event source, see section "Supported Event Sources".
PrerequisitesBefore creating a trigger, ensure that you have prepared the following:
-
+
Creating a DDS Trigger- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Triggers and click Create Trigger.
Figure 1 Creating a trigger
- Set the following parameters:
- Trigger Type: Select Document Database Service (DDS).
- DB Instance: Select a DDS DB instance.
- Password: Enter the password of DDS DB instance administrator rwuser.
- Database: Enter the name of a database. Note that admin, local, and config are reserved database names and cannot be used here.
- Collection: Enter the name of a database collection.
- Batch Size: Set the number of records to be read from the database at a time.
- - Click OK.
After VPC access is enabled, you need to configure corresponding subnet permissions for the DDS security group. For details about how to configure VPC access, see Configuring the Network.
+ - Click OK.
After VPC access is enabled, you need to configure corresponding subnet permissions for the DDS security group. For details about how to configure VPC access, see Configuring Networks.
@@ -48,7 +48,7 @@
diff --git a/docs/fg/umn/functiongraph_01_0211.html b/docs/fg/umn/functiongraph_01_0211.html
index c572576d3..c1b894d3f 100644
--- a/docs/fg/umn/functiongraph_01_0211.html
+++ b/docs/fg/umn/functiongraph_01_0211.html
@@ -4,16 +4,16 @@
diff --git a/docs/fg/umn/functiongraph_01_0212.html b/docs/fg/umn/functiongraph_01_0212.html
index 164878259..41bd3673c 100644
--- a/docs/fg/umn/functiongraph_01_0212.html
+++ b/docs/fg/umn/functiongraph_01_0212.html
@@ -1,7 +1,7 @@
-Function Monitoring
-FunctionGraph is interconnected with Cloud Eye, allowing you to view function metrics without the need for any configurations.
+ Viewing FunctionGraph Metrics
+ FunctionGraph is interconnected with AOM, allowing you to view function metrics without the need for any configurations.
Viewing Function MetricsFunctionGraph collects function metrics and displays aggregated results. Switch to your target function version before viewing metrics.
- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Monitoring > Metrics, select an interval (last hour, last 3 hours, last 12 hours, last day, last 3 days, or custom), and check the running status of the function.
diff --git a/docs/fg/umn/functiongraph_01_0214.html b/docs/fg/umn/functiongraph_01_0214.html
index b2773be30..a3cc8505f 100644
--- a/docs/fg/umn/functiongraph_01_0214.html
+++ b/docs/fg/umn/functiongraph_01_0214.html
@@ -6,11 +6,11 @@
- For details about the differences between DMS for Kafka and open-source Kafka, see Comparing DMS for Kafka and Open-Source Kafka.
- In cases of Kafka data processing failure, the Kafka trigger will discard records that are larger than 6 MB.
PrerequisitesBefore creating a trigger, ensure that you have prepared the following:
- - You have created a function. For details, see Creating a Function from Scratch.
- You have enabled VPC access for the function. For details, see Configuring the Network.
- You have created a Kafka instance. For details, see "Creating an Instance" in the Distributed Message Service for Kafka User Guide.
- You have created a topic under a Kafka instance. For details, see section "Creating a Topic" in the Distributed Message Service for Kafka User Guide.
+ - You have created a function. For details, see Creating a Function from Scratch.
- You have enabled VPC access for the function. For details, see Configuring Networks.
- You have created a Kafka instance. For details, see "Creating an Instance" in the Distributed Message Service for Kafka User Guide.
- You have created a topic under a Kafka instance. For details, see section "Creating a Topic" in the Distributed Message Service for Kafka User Guide.
Creating a Kafka Trigger- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Triggers and click Create Trigger.
Figure 1 Creating a trigger
- Set the following parameters:
- Trigger Type: Select DMS (for Kafka).
- Instance: Select a Kafka premium instance.
- Topic: Select a topic of the Kafka premium instance.
- Batch Size: Set the number of messages to be retrieved from a topic each time.
- Username: Enter the username of the instance if SSL has been enabled for it.
- Password: Enter the password of the instance if SSL has been enabled for it.
- - Click OK.
- After VPC access is enabled, you need to configure corresponding subnet permissions for the Kafka security group. For details about how to configure VPC access, see Configuring the Network.
- You can create a Kafka trigger with multiple topics. You do not need to create one such trigger for each topic in the same instance.
Figure 2 Selecting multiple topics
+ - Click OK.
- After VPC access is enabled, you need to configure corresponding subnet permissions for the Kafka security group. For details about how to configure VPC access, see Configuring Networks.
- You can create a Kafka trigger with multiple topics. You do not need to create one such trigger for each topic in the same instance.
Figure 2 Selecting multiple topics
@@ -52,7 +52,7 @@
diff --git a/docs/fg/umn/functiongraph_01_0222.html b/docs/fg/umn/functiongraph_01_0222.html
index 491fea435..23dbc3eb4 100644
--- a/docs/fg/umn/functiongraph_01_0222.html
+++ b/docs/fg/umn/functiongraph_01_0222.html
@@ -1,6 +1,6 @@
- Configuring the Network
+ Configuring Networks
Public AccessBy default, functions can access services on public networks. If the target public network service requires whitelist verification using a fixed IP address, enable VPC access, configure a NAT gateway for the VPC, and bind an Elastic IP (EIP) to the gateway. For details, see Configuring a Fixed Public IP Address
Configuring VPC AccessFunctions can access resources in a VPC bound to it. If a function needs both VPC and public access, configure a NAT gateway for the VPC and bind an EIP to the gateway. For details, see Configuring a Fixed Public IP Address.
@@ -51,7 +51,7 @@
- (Optional) Configure the domain name.
Enter one or more private domain names of the VPC so that the function can use them to access resources in this VPC. See Figure 1.
- (Optional) Configure the VPC CIDR block.
Figure 2 VPC CIDR block
+ - (Optional) Configure the VPC CIDR block.
Figure 2 VPC CIDR block
- You can enter the VPC CIDR block used in the code to check whether it conflicts with FunctionGraph's VPC CIDR block.
- Click Save.
@@ -62,7 +62,7 @@
Prerequisites
- You have created a VPC and a subnet according to Creating a VPC.
- You have obtained an EIP according to Assigning an EIP.
Procedure
- - In the left navigation pane of the management console, choose Network > NAT Gateway to go to the NAT Gateway console. Then click Create NAT Gateway.
- On the displayed page, enter gateway information, select a VPC (for example, vpc-01) and subnet, and confirm and submit the settings. For details, see Creating a Public NAT Gateway.
- Click the NAT gateway name. On the details page that is displayed, click Add SNAT Rule, set the rule, and click OK.
+ - In the left navigation pane of the management console, choose Network > NAT Gateway to go to the NAT Gateway console. Then click Create NAT Gateway.
- On the displayed page, enter gateway information, select a VPC (for example, vpc-01) and subnet, and confirm and submit the settings. For details, see Creating a Public NAT Gateway.
- Click the NAT gateway name. On the details page that is displayed, click Add SNAT Rule, set the rule, and click OK.
diff --git a/docs/fg/umn/functiongraph_01_0301.html b/docs/fg/umn/functiongraph_01_0301.html
index e9399fddf..f08603458 100644
--- a/docs/fg/umn/functiongraph_01_0301.html
+++ b/docs/fg/umn/functiongraph_01_0301.html
@@ -10,7 +10,7 @@
diff --git a/docs/fg/umn/functiongraph_01_0302.html b/docs/fg/umn/functiongraph_01_0302.html
index 99bf46274..e9f1da3cc 100644
--- a/docs/fg/umn/functiongraph_01_0302.html
+++ b/docs/fg/umn/functiongraph_01_0302.html
@@ -57,11 +57,6 @@
Simulates a DDS event to trigger your function.
|
-Data Ingestion Service (DIS)
- |
-Simulates a DIS event to trigger your function.
- |
-
Log Tank Service (LTS)
|
Simulates an LTS event to trigger your function.
@@ -102,26 +97,6 @@
| The event is {"key": "value"}, which can be changed based on requirements.
|
-Login Security Analysis
- |
-Serves as an input for the loginSecurity-realtime-analysis-python function template.
- |
-
-Image Classification
- |
-Serves as an input for the image-tag function template.
- |
-
-Pornographic Image Analysis
- |
-Serves as an input for the porn-image-analysis function template.
- |
-
-Speech Recognition
- |
-Serves as an input for the voice-analysis function template.
- |
-
Configuring Single-Instance Multi-Concurrency
-OverviewBy default, each function instance processes only one request at a specific time. For example, to process three concurrent requests, FunctionGraph triggers three function instances. To address this issue, FunctionGraph has launched the single-instance multi-concurrency feature, allowing multiple requests to be processed concurrently on one instance.
+ Configuring Concurrency
+ OverviewFunctionGraph allows you to configure the maximum number of instances that can be run for a function at a time. The number of instances is limited to prevent resource exhaustion, ensure that each instance has sufficient resources to run, and improve processing efficiency.
- ScenarioThis feature is suitable for functions which spend a long time to initialize or wait for a response from downstream services. The feature has the following advantages:
- - Fewer cold starts and lower latency: Usually, FunctionGraph starts three instances to process three requests, involving three cold starts. If you configure the concurrency of three requests per instance, only one instance is required, involving only one cold start.
- Shorter processing duration and lower cost: Normally, the total duration of multiple requests is the sum of each request's processing time.
-
- ComparisonIf a function takes 5s to execute each time and you set the number of requests that can be concurrently processed by an instance to 1, three requests need to be processed in three instances, respectively. Therefore, the total execution duration is 15s.
- When you set Max. Requests per Instance to 5, if three requests are sent, they will be concurrently processed by one instance. The total execution time is 5s.
- If the maximum number of requests per instance is greater than 1, new instances will be automatically added when this number is reached. The maximum number of instances will not exceed Max. Instances per Function you set.
-
-
- Table 1 ComparisonComparison Item
- |
-Single-Instance Single-Concurrency
- |
-Single-Instance Multi-Concurrency
- |
-
|---|
-
-Log printing
- |
--
- |
-To print logs, Node.js Runtime uses the console.info() function, Python Runtime uses the print() function, and Java Runtime uses the System.out.println() function. In this mode, current request IDs are included in the log content. However, when multiple requests are concurrently processed by an instance, the request IDs are incorrect if you continue to use the preceding functions to print logs. In this case, use context.getLogger() to obtain a log output object, for example, Python Runtime.
-log = context.getLogger()
-log.info("test")
- |
-
-Shared variables
- |
-Not involved.
- |
-Modifying shared variables will cause errors. Mutual exclusion protection is required when you modify non-thread-safe variables during function writing.
- |
-
-Monitoring metrics
- |
-Perform monitoring based on the actual situation.
- |
-Under the same load, the number of function instances decreases significantly.
- |
-
-Flow control error
- |
-Not involved.
- |
-When there are too many requests, the error code in the body is FSS.0429, the status in the response header is 429, and the error message is Your request has been controlled by overload sdk, please retry later.
- |
-
-
-
-
-
- Configuring Single-Instance Multi-Concurrency- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Concurrency.
Set parameters by referring to Table 2 and click Save.
+Configuring Function Concurrency- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Concurrency.
Set parameters by referring to Table 1 and click Save.
Figure 1 Concurrency configuration
- Table 2 DescriptionParameter
+Table 1 DescriptionParameter
|
-Description
+ | Description
|
|---|
-Max. Instances per Function
+ | Max. Instances per Function
|
-Explanation:
+ | Explanation:
Maximum number of on-demand instances that can be enabled for a function.
Restrictions:
-- Requests that exceed the processing capability of instances will be discarded.
- Errors caused by excessive requests will not be displayed in function logs. You can obtain error details by referring to Configuring Asynchronous Execution Notification.
+- Requests that exceed the processing capability of instances will be discarded.
- Errors caused by excessive requests will not be displayed in function logs. You can obtain error details by referring to Configuring Asynchronous Notification Policy.
Value range:
-1 or an integer ranging from 1 to 1000. The value –1 indicates that the number of instances is not limited.
Default value:
diff --git a/docs/fg/umn/functiongraph_01_0304.html b/docs/fg/umn/functiongraph_01_0304.html
index 6560e2ebd..db7d89d5a 100644
--- a/docs/fg/umn/functiongraph_01_0304.html
+++ b/docs/fg/umn/functiongraph_01_0304.html
@@ -1,6 +1,6 @@
-Creating an Alarm Rule
+Configuring an Alarm Rule
After creating a function and trigger, you can monitor the invocation and running statuses of the function in real time.
Viewing Function MetricsFunctionGraph differentiates the metrics of a function by version, allowing you to query the metrics of a specific function version.
diff --git a/docs/fg/umn/functiongraph_01_0320.html b/docs/fg/umn/functiongraph_01_0320.html
index e05343c7f..cdec50f47 100644
--- a/docs/fg/umn/functiongraph_01_0320.html
+++ b/docs/fg/umn/functiongraph_01_0320.html
@@ -1,6 +1,6 @@
- Function Management
+ Managing Functions
OverviewFunction is a combination of code, runtime, resources, and settings required to achieve a specific purpose. It is the minimum unit that can run independently. A function can be triggered by triggers and automatically schedule required resources and environments to achieve expected results.
Exporting a FunctionYou can export the functions that you created.
diff --git a/docs/fg/umn/functiongraph_01_0390_01.html b/docs/fg/umn/functiongraph_01_0390_01.html
index b4889a668..9266ef967 100644
--- a/docs/fg/umn/functiongraph_01_0390_01.html
+++ b/docs/fg/umn/functiongraph_01_0390_01.html
@@ -1,6 +1,6 @@
- Monitoring
+ Viewing Metrics and Configuring Alarms
diff --git a/docs/fg/umn/functiongraph_01_0390_03.html b/docs/fg/umn/functiongraph_01_0390_03.html
index 7d79a93c7..aabf4fc5a 100644
--- a/docs/fg/umn/functiongraph_01_0390_03.html
+++ b/docs/fg/umn/functiongraph_01_0390_03.html
@@ -1,9 +1,9 @@
-Configuring Asynchronous Execution Notification
+Configuring Asynchronous Notification Policy
OverviewFunctions can be invoked synchronously or asynchronously. In asynchronous mode, FunctionGraph sends a response immediately after persisting a request. The request result cannot be known in real time. To retry when an asynchronous request fails or obtain asynchronous processing results, configure asynchronous settings.
- Scenario- Retry: By default, FunctionGraph does not retry if a function fails due to a code error. If your function needs retry, for example, if third-party services often fail to be invoked, configure retry to improve the success rate.
- Result notifications: FunctionGraph automatically notifies downstream services of the asynchronous execution result of a function for further processing. For example, storing execution failure information in OBS for cause analysis, or pushing execution success information to DIS or triggering the function again.
+ Scenario- Retry: By default, FunctionGraph does not retry if a function fails due to a code error. If your function needs retry, for example, if third-party services often fail to be invoked, configure retry to improve the success rate.
- Result notifications: FunctionGraph automatically notifies downstream services of the asynchronous execution result of a function for further processing. For example, storing execution failure information in OBS for cause analysis, or pushing execution success information or triggering the function again.
Procedure- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Configure Async Notification. On the displayed page, click Edit next to Asynchronous Notification Policy.
Figure 1 Configuring an asynchronous notification policy
- Set parameters by referring to Table 1. For example, specify FunctionGraph for Target Service.
Figure 2 Setting parameters
@@ -22,13 +22,13 @@
Success Notification
|
Target Service: to which a notification will be sent if a function is executed successfully.
-- FunctionGraph
- OBS
- DIS
- SMN
+- FunctionGraph
- OBS
- SMN
|
Failure Notification
|
Target Service: to which a notification will be sent if a function fails to be executed.
-- FunctionGraph
- OBS
- DIS
- SMN
+- FunctionGraph
- OBS
- SMN
|
|
diff --git a/docs/fg/umn/functiongraph_01_0391.html b/docs/fg/umn/functiongraph_01_0391.html
index 6f9b5b760..c0938dde5 100644
--- a/docs/fg/umn/functiongraph_01_0391.html
+++ b/docs/fg/umn/functiongraph_01_0391.html
@@ -1,6 +1,6 @@
-Dependency Management
+Configuring Dependencies
diff --git a/docs/fg/umn/functiongraph_01_0394.html b/docs/fg/umn/functiongraph_01_0394.html
index e03c7c6e0..b2e26cf83 100644
--- a/docs/fg/umn/functiongraph_01_0394.html
+++ b/docs/fg/umn/functiongraph_01_0394.html
@@ -15,7 +15,7 @@
Creating a RocketMQ Trigger- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Triggers and click Create Trigger.
Figure 1 Creating a trigger
- Set the following parameters:
- Trigger Type: Select Distributed Message Service (DMS) for RocketMQ.
- Instance: Select a RocketMQ instance.
- Topic: Select a topic you created from the drop-down list.
- Batch Size: Maximum number of data records that can be obtained a time. Range: 1–1,000.
- Click OK.
- - After VPC access is enabled, you need to configure corresponding subnet permissions for the RocketMQ security group. For details about how to configure VPC access, see Configuring the Network.
- A newly created RocketMQ trigger is disabled by default. To use it, click Enable.
+ - After VPC access is enabled, you need to configure corresponding subnet permissions for the RocketMQ security group. For details about how to configure VPC access, see Configuring Networks.
- A newly created RocketMQ trigger is disabled by default. To use it, click Enable.
Configuring a RocketMQ Event to Trigger the Function- Return to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- On the function details page, select a version.
- On the Code tab page, click Test. The Configure Test Event dialog box is displayed.
- Set the parameters described in Table 1 and click Save.
@@ -54,7 +54,7 @@
diff --git a/docs/fg/umn/functiongraph_01_0401.html b/docs/fg/umn/functiongraph_01_0401.html
index 197210a9a..550e6197a 100644
--- a/docs/fg/umn/functiongraph_01_0401.html
+++ b/docs/fg/umn/functiongraph_01_0401.html
@@ -15,7 +15,7 @@
diff --git a/docs/fg/umn/functiongraph_01_0402.html b/docs/fg/umn/functiongraph_01_0402.html
index cb3ad9d87..4d875373e 100644
--- a/docs/fg/umn/functiongraph_01_0402.html
+++ b/docs/fg/umn/functiongraph_01_0402.html
@@ -19,7 +19,7 @@
Before mounting an SFS Turbo file system to a function, specify an agency that has been granted SFS Administrator and VPC Administrator permissions for the function. If no agencies are available, create one in IAM.
Configuring VPC Access
An SFS Turbo file system is accessible only in the VPC where it has been created. Before mounting such a file system to a function, enable VPC access for the function.
- - On the SFS console, obtain the information about the VPC and subnet where a file system is to be mounted to your function. For details, see File System Management.
- Enable VPC access by referring to Configuring the Network and enter the VPC and subnet obtained in 1.
+ - On the SFS console, obtain the information about the VPC and subnet where a file system is to be mounted to your function. For details, see File System Management.
- Enable VPC access by referring to Configuring Networks and enter the VPC and subnet obtained in 1.
Mounting an SFS Turbo File System
SFS Turbo file systems can be mounted in the same way as SFS file systems. Select a file system and set the access path.
Enter a shared directory and function access path.
Figure 1 Setting the path
-Follow-up OperationsA function can read and write data in an access path in the same way as in the mounted file system.
- Function logs can be persisted by configuring the log path as a subdirectory in the access path.
- The following uses SFS Turbo and template Web-Server-Access-Log-Statistics as an example to describe how to analyze logs of servers running on the cloud.
- - Log in to the FunctionGraph console. In the navigation pane, choose Templates.
- In the upper right corner of the Templates page, enter Web-Server-Access-Log-Statistics in the search box and press Enter.
- In the search result, click Configure. The configuration page is displayed, as shown in Figure 2. Set the parameters as follows:
Figure 2 Function template
-- Region: Select the same region as the created VPC and file system. For details about how to create a VPC and file system, see Configuring the Network and Creating a File System.
- Project: Use default.
- Function Name: Enter a custom name.
- Agency: Select an agency with the file system, VPC, and APIG permissions. For details about how to create an agency, see Configuring Agency Permissions.
- Enterprise Project: Select an enterprise project as required.
- Environment Variables: access_log_path indicates the log file address. Set this parameter to /home/test/access_log.log.
To specify file paths in the file system, use absolute paths starting with a slash (/). However, if no file system is mounted, you can skip adding the slash (/) and simply set the parameter to code/access_log.log.
-
- - Trigger Type: The default value is API Gateway (APIG). For details about how to configure APIG, see Using an APIG (Dedicated) Trigger.
- API Name: Enter a custom name.
- API Group: Select a group based on the actual service.
- Environment: Select RELEASE.
- Security Authentication: Select None.
- Protocol and Timeout (ms): Retain the default values.
- - After parameter configuration is complete, click Create Function.
- On the function details page, click the Code tab, add the following code to the index.py file, and click Deploy.
import shutil
-shutil.copyfile('/opt/function/code/access_log.log', '/home/test/access_log.log')
-Figure 3 Adding code
-In addition, add the public dependency Jinja2-2.10. For details, see How Do I Add a Dependency to a Function?.
- If no file system is mounted, you do not need to add the preceding code.
-
- - On the function details page, choose Configuration > Network and enable VPC Access. Set VPC and Subnet to the created VPC and subnet, and click Save.
Figure 4 VPC access
- - Choose Disk Mounting, click Mount File System, and select SFS Turbo.
- File System: Select an existing SFS Turbo file system.
- Access Path: Set this parameter to /home/test.
- - Click the Code tab, select Configure Test Event, create a Blank Template, and click Create.
Figure 5 Configuring a test event
- - Select the created test event and click Test.
Figure 6 Test result
- - Choose Configuration > Triggers, copy the URL of the APIG trigger, and open the URL using a browser.
Figure 7 Copying the URL
-Figure 8 Results display
-
- Creating an NFS Shared Directory on ECS- Linux
- CentOS, SUSE, EulerOS, Fedora, or openSUSE
- Configure a YUM repository.
1. Create a file named euleros.repo in the /etc/yum.repos.d directory. Ensure that the file name must end with .repo.
2. Run the following command to enter euleros.repo and edit the configuration:
vi /etc/yum.repos.d/euleros.repo
@@ -114,21 +93,7 @@ sudo apt install nfs-kernel-server
exportfs -rv
-
- Windows
- - Install the NFS server.
Paid software: haneWIN NFS Server. Download the software at the haneWIN official website.
-Free software: FreeNFS and WinNFSd. Download the software at the SourceForge website.
- - Enable the NFS function.
- In the case of WinNFSd, see WinNFSd configuration.
- Download and decompress WinNFSd, and create the nfs folder in the decompressed directory.
- Set the sharing and read/write permissions on the nfs file.
- Right-click the nfs file and choose Properties.
- Click the Sharing tab, and then click Share....
- Add Everyone and click Share.
Figure 9 Adding Everyone
- - Click the Security tab, select Everyone in the Group or user names list, and click Edit.
- In the displayed Security dialog box, select Everyone from the Group or user name list, select Read and Write from the Allow check boxes in the Permissions for Everyone list, and click OK.
- - Disable all firewalls, including the Domain network, Private network, and Public network. Enable them after the entire configuration is complete.
- Log in to the virtual server of the router and enable ports 111, 2049, and 1058 of the external network. (Note: An external IP address is required.)
- Run the following command. For details, see https://github.com/winnfsd/winnfsd.
WinNFSd.exe -addr {Your own local IP address 192.168.xxx.xxx} F:\nfs /nfs
-
- - In the case of haneWIN NFS Server, perform the following steps:
- Run the downloaded .exe file as the Windows system administrator.
- After the installation is complete, open the NFS Server file and choose Edit > Preferences.
- Retain the default settings on the NFS, Server, and PortMapper tab pages. Click the Exports tab, click Edit exports file to configure the shared directory, and click Save.
The shared directory format can be referenced as D:\share -public -name:nfs, which means to set the permission on the share folder to public and define an alias nfs.
-
- - Click OK.
- Disable all firewalls, including the Domain network, Private network, and Public network. Enable them after the entire configuration is complete.
Run the following command in Linux to mount the directory and check whether the file sharing is successful:
- mount -t nfs -o nolock 192.168.xxx.xxx:/nfs /mnt
- - 192.168.xxx.xxx is the IP address of the Windows operating system.
- nfs is the alias created when the shared directory is configured.
- /mnt is the local directory where the remote directory is mounted.
-
-
-
+
- Windows
For details about how to install NFS and share files, see the official document on Windows.
Configuring Class Isolation and Pre-stop for Java Functions
+Class isolation is used to load your code and dependencies using an independent class loader if they conflict with the runtime dependencies.
+ Pre-stop is used to call a callback function before FunctionGraph stops the current function instance.
+ ConstraintsOnly Java functions can be configured with class isolation and pre-stop.
+
+ Configuring Class Isolation for a Java Function- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the name of a function.
- Choose Configuration > Advanced Settings.
- Enable Class Isolation and click Save.
+
+ Configuring Pre-stop for a Java Function- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the name of a function.
- On the Configuration tab, click Lifecycle.
- Enable Pre-stop and set the related parameters.
+
Table 1 Pre-stop configurationParameter
+ |
+Description
+ |
+
|---|
+
+Pre-stop Timeout (s)
+ |
+Timeout for executing the callback function before the current function instance is stopped. The value is an integer ranging from 1 to 90.
+ |
+
+Pre-stop Handler
+ |
+Handler of the callback function, which can contain a maximum of 128 characters in the format of "[package name].[class name].[execution function name]".
+ |
+
+
+
+ - Click Save.
+
+ Unavailable
|
SWR Admin: administrator who has all permissions for the Software Repository for Container (SWR) service.
-For details about how to create a custom image, see Deploying a Function Using a Container Image.
+For details about how to create a custom image, see Creating a Function with an Image.
|
Mounting an SFS Turbo file system
@@ -61,16 +61,6 @@
aom:metric:list: permissions for querying metric list in AOM.
|
-Using a DIS trigger
- |
-DIS Administrator
- |
-Unavailable
- |
-Administrator who has all permissions for the DIS service.
-For details about how to create a DIS trigger, see Using a DIS Trigger.
- |
-
Using a DMS trigger
|
DMS ReadOnlyAccess
@@ -94,13 +84,10 @@
|
Users with the VPC Administrator permissions can perform any operations on all cloud resources of the VPC. To configure cross-VPC access, specify an agency with VPC management permissions.
Fine-grained minimum permission for VPC: permissions for unbinding a virtual IP address from a VM, querying a port, creating a port, querying a VPC, querying a subnet, and querying security groups or details about a security group.
-For details about how to configure cross-domain VPC access, see Configuring the Network.
+For details about how to configure cross-domain VPC access, see Configuring Networks.
|
-Configuring asynchronous notification
-
-
-
+ | Configuring asynchronous notification
|
If the target service is OBS:
OBS Administrator
@@ -111,7 +98,7 @@
|
OBS Administrator: administrator who has all permissions for OBS.
Fine-grained minimum permission for OBS: permissions for obtaining bucket metadata, creating a bucket, uploading objects using POST method, copying objects, appending an object, initializing a multipart task, uploading parts, and merging parts.
-For details about how to configure asynchronous notification, see Configuring Asynchronous Execution Notification.
+For details about how to configure asynchronous notification, see Configuring Asynchronous Notification Policy.
|
If the target service is SMN:
@@ -122,16 +109,7 @@
|
SMN Administrator: administrator who has all permissions for SMN.
Fine-grained minimum permission for using SMN: permissions for publishing a message and querying the topic list.
-For details about how to configure asynchronous notification, see Configuring Asynchronous Execution Notification.
- |
-
-If the target service is DIS:
-DIS Administrator
- |
-Unavailable
- |
-DIS Administrator: administrator who has all permissions for DIS.
-For details about how to configure asynchronous notification, see Configuring Asynchronous Execution Notification.
+For details about how to configure asynchronous notification, see Configuring Asynchronous Notification Policy.
|
@@ -170,7 +148,7 @@
-Configuration Agency
+ | Agency
|
Select a function that you have created.
|
@@ -185,7 +163,7 @@
- To ensure optimal performance, select Specify an exclusive agency for function execution and set different agencies for function configuration and execution. You can also use no agency or specify the same agency for both purposes. Figure 5 shows the agency options.
Figure 5 Setting agencies
- Configuration Agency: For example, to create Data Ingestion Service (DIS) triggers, first specify an agency with DIS permissions. If such an agency is not specified or the specified agency does not exist, no DIS triggers can be created.
- Execution Agency: This type of agency enables you to obtain a token and AK/SK from the context in the function handler for accessing other cloud services.
+ - Execution Agency: This type of agency enables you to obtain a token and AK/SK from the context in the function handler for accessing other cloud services.
- Click Save.
diff --git a/docs/fg/umn/functiongraph_01_1000.html b/docs/fg/umn/functiongraph_01_1000.html
index 432f35e9b..bbe8d9644 100644
--- a/docs/fg/umn/functiongraph_01_1000.html
+++ b/docs/fg/umn/functiongraph_01_1000.html
@@ -12,8 +12,6 @@
- Application Scenarios
-- Function Types
-
- Notes and Constraints
- Permissions Management
diff --git a/docs/fg/umn/functiongraph_01_1047.html b/docs/fg/umn/functiongraph_01_1047.html
index f4bae8f6a..c28e9cc58 100644
--- a/docs/fg/umn/functiongraph_01_1047.html
+++ b/docs/fg/umn/functiongraph_01_1047.html
@@ -1,6 +1,6 @@
-Deploying a Function Using a Container Image
+Creating a Function with an Image
IntroductionPackage your container images complying with the Open Container Initiative (OCI) standard, and upload them to FunctionGraph. The images will be loaded and run by FunctionGraph. Unlike the code upload mode, you can use a custom code package, which is flexible and reduces migration costs. You can create event and HTTP functions by using a custom image.
For details about how to develop and deploy an HTTP function using a container image, see Developing an HTTP Function.
For details about how to develop and deploy an event function using a container image, see Creating an Event Function Using a Container Image and Executing the Function.
@@ -29,7 +29,7 @@
Select a function type.
-HTTP function: triggered once HTTP requests are sent to specific URLs. NOTE: - The custom container image must contain an HTTP server with listening port 8000.
- HTTP functions support APIG and APIC triggers only.
- When calling a function using APIG, isBase64Encoded is valued true by default, indicating that the request body transferred to FunctionGraph is encoded using Base64 and must be decoded for processing.
- The function must return characters strings by using the following structure.
{
+HTTP function: triggered once HTTP requests are sent to specific URLs. NOTE: - The custom container image must contain an HTTP server with listening port 8000.
- HTTP functions support APIG triggers only.
- When calling a function using APIG, isBase64Encoded is valued true by default, indicating that the request body transferred to FunctionGraph is encoded using Base64 and must be decoded for processing.
- The function must return characters strings by using the following structure.
{
"isBase64Encoded": true|false,
"statusCode": httpStatusCode,
"headers": {"headerName":"headerValue",...},
@@ -122,7 +122,7 @@ app.listen(PORT, () => {
diff --git a/docs/fg/umn/functiongraph_01_1062.html b/docs/fg/umn/functiongraph_01_1062.html
index aaa26e04a..cacf64644 100644
--- a/docs/fg/umn/functiongraph_01_1062.html
+++ b/docs/fg/umn/functiongraph_01_1062.html
@@ -19,11 +19,6 @@
Asynchronous
|
|
-DIS
- |
-Asynchronous
- |
-
Timer
|
Asynchronous
@@ -52,14 +47,17 @@
|
- APIG and APIG (dedicated) triggers can be configured for asynchronous invocation on their console. You can also use the asynchronous execution API instead. In this scenario, the maximum execution duration of a function is 12 hours (configured in the whitelist).
If the E2E function execution latency exceeds 90s, asynchronous invocation is recommended. If synchronous invocation is used, no responses can be received after 90s due to gateway restrictions.
+ - APIG (dedicated) triggers can be configured for asynchronous invocation on their console. You can also use the asynchronous execution API instead. In this scenario, the maximum execution duration of a function is 12 hours (configured in the whitelist).
If the E2E function execution latency exceeds 90s, asynchronous invocation is recommended. If synchronous invocation is used, no responses can be received after 90s due to gateway restrictions.
Example
- The following procedure uses the APIG trigger of a function as an example.
+ The following procedure uses the APIG trigger of a function as an example. For details about how to create an APIG trigger, see Using an APIG (Dedicated) Trigger.
- Go to the function details page, and choose Configuration > Triggers.
- Click the APIG trigger name to go to the APIG console.
Figure 1 Clicking a trigger name
- - Click Edit in the upper right.
Figure 2 Clicking Edit
- - Click Next until the Define Backend Request page is displayed. Then change Invocation Mode to Asynchronous.
Figure 3 Changing the invocation mode
+
+ - Click Modify in the upper right.
Figure 2 Clicking Modify
+
+ - Click Next until the Backend Configuration page is displayed. Then change Invocation Mode to Asynchronous.
Figure 3 Changing the invocation mode
+
- Click Finish to save the settings.
diff --git a/docs/fg/umn/functiongraph_01_1441.html b/docs/fg/umn/functiongraph_01_1441.html
index 47f0a70a2..d82a4e379 100644
--- a/docs/fg/umn/functiongraph_01_1441.html
+++ b/docs/fg/umn/functiongraph_01_1441.html
@@ -8,7 +8,7 @@
Each FunctionGraph function runs in its own environment and has its own resources and file system.
-Prerequisites- You must be familiar with the programming languages supported by FunctionGraph. For details, see Supported Programming Languages.
- You have created a deployment package. For details, see Creating a Deployment Package.
- (Optional) You have created an agency. For details, see Configuring Agency Permissions.
+
Procedure- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- On the Function List page, click Create Function in the upper right corner.
- Click Create from scratch and configure the function information by referring to Table 1. The parameters marked with an asterisk (*) are mandatory.
Figure 1 Creating a function from scratch
@@ -20,7 +20,7 @@
|
|---|
* Function Type
|
-- Event functions: triggered by triggers.
- HTTP functions: triggered once HTTP requests are sent to specific URLs.
NOTE: - HTTP functions do not distinguish between programming languages. The handler must be set in the bootstrap file. You can directly write the startup command, and allow access over port 8000.
- HTTP functions support APIG and APIC triggers only.
- For details about how to use HTTP functions, see Creating an HTTP Function.
+ - Event functions: triggered by triggers.
- HTTP functions: triggered once HTTP requests are sent to specific URLs.
NOTE: - HTTP functions do not distinguish between programming languages. The handler must be set in the bootstrap file. You can directly write the startup command, and allow access over port 8000.
- HTTP functions support APIG triggers only.
- For details about how to use HTTP functions, see Creating an HTTP Function.
|
@@ -81,7 +81,7 @@
- Click Create Function. On the displayed Code tab page, continue to configure the code.
-Configuring Code- You can deploy the code based on the runtime you select. For details, see Creating a Deployment Package. After the deployment is complete, click Deploy.
As shown in the following example, to deploy code in Node.js 10.16, you can edit code inline, upload a local ZIP file, or upload a ZIP file from OBS.
+Configuring Code- You can deploy the code based on the runtime you select. For details, see Configuring Code. After the deployment is complete, click Deploy.
As shown in the following example, to deploy code in Node.js 10.16, you can edit code inline, upload a local ZIP file, or upload a ZIP file from OBS.
Figure 2 Deploying code
If you deploy code by uploading a local ZIP file, ensure that the region selected for creating the function is the same as that selected for creating an OBS bucket.
diff --git a/docs/fg/umn/functiongraph_01_1442.html b/docs/fg/umn/functiongraph_01_1442.html
index fa52c2e18..a989648a3 100644
--- a/docs/fg/umn/functiongraph_01_1442.html
+++ b/docs/fg/umn/functiongraph_01_1442.html
@@ -1,11 +1,67 @@
Creating an HTTP Function
-OverviewHTTP functions are designed to optimize web services. You can send HTTP requests to URLs to trigger function execution. HTTP functions support APIG triggers only.
- - HTTP functions do not distinguish between programming languages. The handler must be set in the bootstrap file. You can directly write the startup command, and allow access over port 8000. The bound IP address is 127.0.0.1.
- The bootstrap file is the startup file of the HTTP function. The HTTP function can only read bootstrap as the startup file name. If the file name is not bootstrap, the service cannot be started. For more information, see the bootstrap file example.
- HTTP functions support multiple programming languages.
- Functions must return a valid HTTP response.
- This section uses Node.js as an example. To use another runtime, simply change the runtime path. The code package path does not need to be changed. For the paths of other runtimes, see Table 1.
- When a function initiates an HTTP request, the request IP address is dynamic for private network access and fixed for public network access. For more information, contact technical support.
-
+ OverviewHTTP functions are designed to optimize web services and support multiple programming languages. You can send HTTP requests to URLs to trigger function execution.
- Prerequisites- Prepare a Node.js script. A code example is as follows:
const http = require('http'); // Import Node.js core module
+Common Function Request HeadersThe following table lists the default request header fields of an HTTP function.
+
+ Table 1 Default request header fieldsField
+ |
+Description
+ |
+
|---|
+
+X-CFF-Request-Id
+ |
+ID of the current request
+ |
+
+X-CFF-Memory
+ |
+Allocated memory
+ |
+
+X-CFF-Timeout
+ |
+Function timeout duration
+ |
+
+X-CFF-Func-Version
+ |
+Function version
+ |
+
+X-CFF-Func-Name
+ |
+Function name
+ |
+
+X-CFF-Project-Id
+ |
+Project ID
+ |
+
+X-CFF-Package
+ |
+App to which the function belongs
+ |
+
+X-CFF-Region
+ |
+Current region
+ |
+
+
+
+
+ Constraints- HTTP functions do not distinguish between programming languages. The handler must be set in the bootstrap file. You can directly write the startup command, and allow access over port 8000. The bound IP address is 127.0.0.1.
- The HTTP response body cannot exceed 6 MB.
A valid HTTP function response must contain body(String), statusCode(int), headers(Map), and isBase64Encoded(boolean). By default, the response is encoded using Base64. The default value of isBase64Encoded is true. The same applies to other frameworks.
+ - The bootstrap file is the startup file of the HTTP function. The HTTP function can only read bootstrap as the startup file name. If the file name is not bootstrap, the service cannot be started. For more information, see the bootstrap file example.
If you run the JAR package, you are advised to add the JVM parameter -Dfile.encoding=utf-8 to bootstrap. Otherwise, garbled Chinese characters may be displayed.
+ - Only APIG triggers can be created for HTTP functions.
- HTTP functions cannot be executed for a long time, invoked asynchronously, or retried.
- When a function initiates an HTTP request, the request IP address is dynamic for private network access and fixed for public network access. For more information, contact technical support.
+ Creating and Configuring an HTTP FunctionThe following uses an example to describe how to create and configure an HTTP function.
+ Step 1: Creating a Code Package- Prepare a Node.js script. A code example is as follows:
const http = require('http'); // Import Node.js core module
var server = http.createServer(function (req, res) { //create web server
res.writeHead(200, { 'Content-Type': 'text/html' });
@@ -16,215 +72,154 @@ var server = http.createServer(function (req, res) { //create web server
server.listen(8000, '127.0.0.1'); //6 - listen for any incoming requests
console.log('Node.js web server at port 8000 is running..')
- - You have prepared a bootstrap file as the startup file of the HTTP function.
Example
-The content of the bootstrap file is as follows:
+ - You have prepared a bootstrap file as the startup file of the HTTP function.
The content of the bootstrap file is as follows:
/opt/function/runtime/nodejs12.13/rtsp/nodejs/bin/node $RUNTIME_CODE_ROOT/index.js
- - Compress the preceding two files into a ZIP package.
Figure 1 Compressing files into a ZIP package
- For HTTP functions in Python, add the -u parameter in the bootstrap file to ensure that logs can be flushed to the disk. Example:
- /opt/function/runtime/python3.6/rtsp/python/bin/python3 -u $RUNTIME_CODE_ROOT/index.py
-
-To use another runtime, change the runtime path by referring to Table 1. The code package path does not need to be changed.
+ - Compress the preceding two files into a ZIP package.
Figure 1 Compressing files into a ZIP package
+For HTTP functions in Python, add the -u parameter in the bootstrap file to ensure that logs can be flushed to the disk. For example:
+/opt/function/runtime/python3.6/rtsp/python/bin/python3 -u $RUNTIME_CODE_ROOT/index.py
+To use another runtime, change the runtime path by referring to Table 2. The code package path does not need to be changed.
-Table 1 Paths for different runtimesRuntime
+Table 2 Paths for different runtimesRuntime
|
-Path
+ | Path
|
|---|
-Java 8
+ | Java 8
|
-/opt/function/runtime/java8/rtsp/jre/bin/java
+ | /opt/function/runtime/java8/rtsp/jre/bin/java
|
-Java 11
+ | Java 11
|
-/opt/function/runtime/java11/rtsp/jre/bin/java
+ | /opt/function/runtime/java11/rtsp/jre/bin/java
|
-Java17
+ | Java 17
|
-/opt/function/runtime/java17/rtsp/jre/bin/java
+ | /opt/function/runtime/java17/rtsp/jre/bin/java
|
-Java21
+ | Java 21
|
-/opt/function/runtime/java21/rtsp/jre/bin/java
+ | /opt/function/runtime/java21/rtsp/jre/bin/java
|
-Node.js 6
+ | Node.js 6
|
-/opt/function/runtime/nodejs6.10/rtsp/nodejs/bin/node
+ | /opt/function/runtime/nodejs6.10/rtsp/nodejs/bin/node
|
-Node.js 8
+ | Node.js 8
|
-/opt/function/runtime/nodejs8.10/rtsp/nodejs/bin/node
+ | /opt/function/runtime/nodejs8.10/rtsp/nodejs/bin/node
|
-Node.js 10
+ | Node.js 10
|
-/opt/function/runtime/nodejs10.16/rtsp/nodejs/bin/node
+ | /opt/function/runtime/nodejs10.16/rtsp/nodejs/bin/node
|
-Node.js 12
+ | Node.js 12
|
-/opt/function/runtime/nodejs12.13/rtsp/nodejs/bin/node
+ | /opt/function/runtime/nodejs12.13/rtsp/nodejs/bin/node
|
-Node.js 14
+ | Node.js 14
|
-/opt/function/runtime/nodejs14.18/rtsp/nodejs/bin/node
+ | /opt/function/runtime/nodejs14.18/rtsp/nodejs/bin/node
|
-Node.js 16
+ | Node.js 16
|
-/opt/function/runtime/nodejs16.17/rtsp/nodejs/bin/node
+ | /opt/function/runtime/nodejs16.17/rtsp/nodejs/bin/node
|
-Node.js 18
+ | Node.js 18
|
-/opt/function/runtime/nodejs18.15/rtsp/nodejs/bin/node
+ | /opt/function/runtime/nodejs18.15/rtsp/nodejs/bin/node
|
-Node.js20
+ | Node.js 20
|
-/opt/function/runtime/nodejs20.15/rtsp/nodejs/bin/node
+ | /opt/function/runtime/nodejs20.15/rtsp/nodejs/bin/node
|
-Python 2.7
+ | Python 2.7
|
-/opt/function/runtime/python2.7/rtsp/python/bin/python
+ | /opt/function/runtime/python2.7/rtsp/python/bin/python
|
-Python 3.6
+ | Python 3.6
|
-/opt/function/runtime/python3.6/rtsp/python/bin/python3
+ | /opt/function/runtime/python3.6/rtsp/python/bin/python3
|
-Python 3.9
+ | Python 3.9
|
-/opt/function/runtime/python3.9/rtsp/python/bin/python3
+ | /opt/function/runtime/python3.9/rtsp/python/bin/python3
|
-Python3.10
+ | Python 3.10
|
-/opt/function/runtime/python3.10/rtsp/python/bin/python3
+ | /opt/function/runtime/python3.10/rtsp/python/bin/python3
|
-Python3.12
+ | Python 3.12
|
-/opt/function/runtime/python3.12/rtsp/python/bin/python3
+ | /opt/function/runtime/python3.12/rtsp/python/bin/python3
|
-PHP 7.3
+ | PHP 7.3
|
-/opt/function/runtime/php7.3/rtsp/php/bin/php
+ | /opt/function/runtime/php7.3/rtsp/php/bin/php
|
-PHP8.3
+ | PHP 8.3
|
-/opt/function/runtime/php8.3/rtsp/php/bin/php
+ | /opt/function/runtime/php8.3/rtsp/php/bin/php
|
-C# (.NET Core 2.1)
+ | C# (.NET Core 2.1)
|
-/opt/function/runtime/dotnet2.1/rtsp/dotnet/dotnet
+ | /opt/function/runtime/dotnet2.1/rtsp/dotnet/dotnet
|
-C# (.NET Core 3.1)
+ | C# (.NET Core 3.1)
|
-/opt/function/runtime/dotnet3.1/rtsp/dotnet/dotnet
+ | /opt/function/runtime/dotnet3.1/rtsp/dotnet/dotnet
|
-C# (.NET Core 6.0)
+ | C# (.NET Core 6.0)
|
-/opt/function/runtime/dotnet6.0/rtsp/dotnet/dotnet
- |
-
-C# (.NET Core 8.0)
- |
-/opt/function/runtime/dotnet8.0/rtsp/dotnet/dotnet
+ | /opt/function/runtime/dotnet6.0/rtsp/dotnet/dotnet
|
Procedure- Create a function.
- Create an HTTP function. For details, see Creating an Event Function. Pay special attention to the following parameters:
- Function Type: HTTP function
- Region: Select a region where you will deploy your code.
- - Choose Upload > Local ZIP, upload the ZIP package, and click Deploy.
Figure 2 Uploading a ZIP file
- If you deploy code by uploading a local ZIP file, ensure that the region selected for creating the function is the same as that selected for creating an OBS bucket.
+
Step 2: Deploying the Code Package- On the Code page of the HTTP function, click Upload > Local ZIP, and upload the prepared ZIP file.
- Create a trigger.
- Choose Configuration > Triggers and click Create Trigger.
- Configure the trigger information..
Figure 2 Creating a trigger
+
+In this example, Security Authentication is set to None. You need to select an authentication mode based on site requirements.
+ - App: AppKey and AppSecret authentication. This mode is of high security and is recommended.
- IAM: IAM authentication. This mode grants access permissions to IAM users only and is of medium security.
- None: No authentication. This mode grants access permissions to all users.
+ - Click OK.
+ - Publish the API.
- On the Triggers tab page, click an API name to go to the API overview page.
Figure 3 API trigger
+
+ - Click Edit in the upper right corner. The API basic information page is displayed.
Figure 4 Modifying an API
+
+ - Change the value of Path to /user/get and click Finish.
Figure 5 Defining an API request
+
+ - On the API details page, click Publish in the upper right corner. On the displayed page, click OK.
- - Create a trigger.
HTTP functions support APIG triggers only.
-
-- On the function details page, choose Configuration > Triggers and click Create Trigger.
- Set the trigger information. This step uses an API Gateway (Dedicated) trigger as an example. For more information, see Using an APIG (Dedicated) Trigger.
-
Figure 3 Creating a trigger
- In this example, Security Authentication is set to None. You need to select an authentication mode based on site requirements.
- - App: AppKey and AppSecret authentication. This mode is of high security and is recommended.
- IAM: IAM authentication. This mode grants access permissions to IAM users only and is of medium security.
- None: No authentication. This mode grants access permissions to all users.
-
- - When the configuration is complete, click OK. After the trigger is created, API_test_http will be generated on the APIG console.
- - Publish the API.
- On the Triggers tab page, click an API name to go to the API overview page.
Figure 4 APIG trigger
- - Click Edit in the upper right corner. The Basic Information page is displayed.
Figure 5 Editing an API
- - Click Next. On the Define API Request page that is displayed, change Path to /user/get and click Finish.
Figure 6 Defining an API request
- - Click Publish API. On the displayed page, click Publish.
- - Trigger a function.
- Go to the FunctionGraph console, choose Functions > Function List in the navigation pane, and click the created HTTP function to go to its details page.
- Choose Configuration > Triggers, copy the URL, and access it using a browser.
Figure 7 Copying the URL
- - View the request result.
Figure 8 Viewing the request result
+
Step 3: Triggering Function Execution- Go to the FunctionGraph console, choose Functions > Function List in the navigation pane, and click the created HTTP function to go to its details page.
- Choose Configuration > Triggers, copy the URL as shown in , and access it using a browser.
Figure 6 Copying the URL
+
+ - View the request result.
Figure 7 Viewing the request result
-
-
- Common Function Request HeadersThe following table lists the default request header fields of an HTTP function.
-
- Table 2 Default request header fieldsField
- |
-Description
- |
-
|---|
-
-X-CFF-Request-Id
- |
-ID of the current request
- |
-
-X-CFF-Memory
- |
-Allocated memory
- |
-
-X-CFF-Timeout
- |
-Function timeout duration
- |
-
-X-CFF-Func-Version
- |
-Function version
- |
-
-X-CFF-Func-Name
- |
-Function name
- |
-
-X-CFF-Project-Id
- |
-Project ID
- |
-
-X-CFF-Package
- |
-App to which the function belongs
- |
-
-X-CFF-Region
- |
-Current region
- |
-
-
-
-
-
+
diff --git a/docs/fg/umn/functiongraph_01_1814.html b/docs/fg/umn/functiongraph_01_1814.html
index 5c13ba93d..7ce626e9e 100644
--- a/docs/fg/umn/functiongraph_01_1814.html
+++ b/docs/fg/umn/functiongraph_01_1814.html
@@ -3,7 +3,7 @@
Retry Mechanism
If synchronous or asynchronous invocation fails, do as follows:
- Synchronous invocation
Try again.
- - Asynchronous invocation
You can set the maximum number of retries and the maximum message validity period (up to 24 hours) by referring to Configuring Asynchronous Execution Notification. FunctionGraph will retry a function based on these two parameters.
+ - Asynchronous invocation
You can set the maximum number of retries and the maximum message validity period (up to 24 hours) by referring to Configuring Asynchronous Notification Policy. FunctionGraph will retry a function based on these two parameters.
IdempotencyIn programming, idempotency means that an application or component can identify duplicate events and prevent duplication, inconsistency, and data loss. If you want to keep a function idempotent, you need to design the function logic to correctly handle repeated events.
Idempotent function logic helps reduce the following problems:
diff --git a/docs/fg/umn/functiongraph_01_1829.html b/docs/fg/umn/functiongraph_01_1829.html
index f276f53d7..f6273fa96 100644
--- a/docs/fg/umn/functiongraph_01_1829.html
+++ b/docs/fg/umn/functiongraph_01_1829.html
@@ -1,11 +1,11 @@
- Managing Aliases
+ Configuring Function Aliases
OverviewAn alias points to a specific function version. Create an alias and expose it to clients, for example, bind a trigger to the alias instead of the corresponding version. Then your modification to the version for update or rollback will be imperceptible to the clients. An alias can point to up to two versions with different weights for dark launch.
ConstraintsYou can create up to 10 aliases for a function.
- Creating an Alias- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- On the Aliases tab page, click Create Alias.
Figure 1 Creating an alias
+Creating an Alias- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- On the Aliases tab page, click Create Alias.
Figure 1 Creating an alias
- Alias: Enter an alias.
- Version: Select a version to be associated with the alias.
- Traffic Shifting: Choose whether to enable traffic shifting. If this function is enabled, you can distribute a specific percentage of traffic to the additional version.
- Additional Version: Select an additional version to be associated. The latest version cannot be used as an additional version.
- Shift By: You can shift requests to the additional version by Percentage or Rule.
Table 1 Shifting modeShift By
|
@@ -21,7 +21,7 @@
|---|
Rule
|
Available only for HTTP functions or functions with APIG triggers. The following parameters need to be configured:
-- Rule Type: Select All rules met or Any rule met to forward requests with specified headers to the additional version.
- Rules: Set the header rule conditions. For details, see Table 2.
+- Rule Type: Select All rules met or Any rule met to forward requests with specified headers to the additional version.
- Rules: Set the header rule conditions. For details, see Table 2.
|
@@ -56,10 +56,10 @@
- Click OK.
-Modifying an Alias- Return to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- On the Aliases tab page of the latest version, select the alias to modify.
Figure 2 Modifying an alias
+Modifying an Alias- Return to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- On the Aliases tab page of the latest version, select the alias to modify.
Figure 2 Modifying an alias
- Modify the alias information, and click OK.
Deleting an Alias- Return to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- On the Aliases tab page of the latest version, select the alias to delete.
Figure 3 Deleting an alias
+Deleting an Alias- Return to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- On the Aliases tab page of the latest version, select the alias to delete.
Figure 3 Deleting an alias
- Click OK to delete the version.
Reserved Instance Management
+Configuring Reserved Instances
IntroductionFunctionGraph provides on-demand and reserved instances.
- On-demand instances are created and released by FunctionGraph based on actual function usage. When receiving requests to call functions, FunctionGraph automatically allocates execution resources to the requests.
- Reserved instances can be created and released by you as required. After you create reserved instances for a function, FunctionGraph preferentially forwards requests to the reserved instances. If the number of requests exceeds the processing capability of the reserved instances, FunctionGraph will forward the excessive requests to on-demand instances and automatically allocates execution resources to these requests.
After reserved instances are created for a function, the code, dependencies, and initializer of the function are automatically loaded. Reserved instances are always alive in the execution environment, eliminating the influence of cold starts on your services. (Do not execute one-time services using the initializer of reserved instances.)
You can configure a fixed number of reserved instances or scheduled scaling policies.
diff --git a/docs/fg/umn/functiongraph_01_1838.html b/docs/fg/umn/functiongraph_01_1838.html
index bc7ce8ef5..db3f05380 100644
--- a/docs/fg/umn/functiongraph_01_1838.html
+++ b/docs/fg/umn/functiongraph_01_1838.html
@@ -6,7 +6,7 @@
- For details about the differences between DMS for Kafka and open-source Kafka, see Comparing DMS for Kafka and Open-Source Kafka.
- In cases of Kafka data processing failure, the Kafka trigger will discard records that are larger than 6 MB.
PrerequisitesBefore creating a trigger, ensure that you have prepared the following:
- - You have created a function.
- You have enabled VPC access for the function. For details, see Configuring the Network.
+ - You have created a function.
- You have enabled VPC access for the function. For details, see Configuring Networks.
Creating an Open-Source Kafka Trigger- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Triggers and click Create Trigger.
Figure 1 Creating a trigger
- Set the following parameters:
- Trigger Type: Select Kafka (OPENSOURCEKAFKA).
- Connection Address: Addresses of brokers running Kafka. Separate the addresses with commas (,).
- Topic: Enter one or more topics.
- Batch Size: Maximum number of data records that can be processed by the function at a time.
@@ -54,7 +54,7 @@
Configuring a Log Group and Log Stream
- This feature is supported only by FunctionGraph V2.
-
- IntroductionYou can bind a log group and log stream to a function to store its invocation logs. By default, the logs are stored in the log stream automatically created for the function. For details, see Using LTS to Manage Function Logs.
+ IntroductionYou can bind a log group and log stream to a function to store its invocation logs. By default, the logs are stored in the log stream automatically created for the function. For details, see Using LTS to Manage Function Logs.
PrerequisitesYou have created a log group and log stream on the LTS console.
Procedure- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click the function to be configured to go to the function details page.
- Choose Configuration > Log, and configure log collection according to Table 1.
-
Table 1 Log configuration parametersParameter
+Table 1 Log configuration parametersParameter
|
-Description
+ | Description
|
|---|
-Collect Logs
+ | Collect Logs
|
-Enabled by default in FunctionGraph V2. This feature is unavailable for FunctionGraph V1.
+ | Enabled by default in FunctionGraph V2. This feature is unavailable for FunctionGraph V1.
|
-Log Group
+ | Log Group
|
-Select a log group for the function. The default log group functiongraph.log.group.xxx cannot be selected.
+ | Select a log group for the function. The default log group functiongraph.log.group.xxx cannot be selected.
By default, the log group (starting with functiongraph) automatically generated by FunctionGraph is selected.
|
-Log Stream
+ | Log Stream
|
-Select a log stream in the specified log group.
+ | Select a log stream in the specified log group.
By default, the log stream (starting with the function name) automatically generated for the function is selected.
|
diff --git a/docs/fg/umn/functiongraph_01_2102.html b/docs/fg/umn/functiongraph_01_2102.html
index c09b361f4..ef62c0ff4 100644
--- a/docs/fg/umn/functiongraph_01_2102.html
+++ b/docs/fg/umn/functiongraph_01_2102.html
@@ -149,7 +149,7 @@
diff --git a/docs/fg/umn/functiongraph_01_2119.html b/docs/fg/umn/functiongraph_01_2119.html
index 1f5617939..6b649b03c 100644
--- a/docs/fg/umn/functiongraph_01_2119.html
+++ b/docs/fg/umn/functiongraph_01_2119.html
@@ -87,7 +87,7 @@
diff --git a/docs/fg/umn/functiongraph_02_1005.html b/docs/fg/umn/functiongraph_02_1005.html
index e33044a7b..12b5a387d 100644
--- a/docs/fg/umn/functiongraph_02_1005.html
+++ b/docs/fg/umn/functiongraph_02_1005.html
@@ -6,13 +6,13 @@
Event SourceAn event source is a public cloud service or custom application that publishes events.
RuntimeThe runtime provides an execution environment for the corresponding programming language to pass function invocation events, context information, and responses.
- For supported runtimes, see .
+ FunctionGraph currently supports Node.js, Python, Java, Go, C#, PHP, and custom runtimes.
Synchronous InvocationClients wait for explicit responses to their requests from a function. Responses are returned only after the function is invoked.
Asynchronous InvocationClients do not care about the function invocation results of their requests. After receiving a request, FunctionGraph puts it in a queue, returns a response, and processes other requests when there are idle resources.
TriggerA trigger is an event that triggers function execution.
+ TriggerA trigger is an event that triggers function execution. Triggers can also be used to trigger functions when specified cloud service events occur.
Single-Instance Multi-ConcurrencyThe number of requests that can be concurrently processed by an instance.
diff --git a/docs/fg/umn/functiongraph_03_0100.html b/docs/fg/umn/functiongraph_03_0100.html
index 60d637ba1..e09b6093a 100644
--- a/docs/fg/umn/functiongraph_03_0100.html
+++ b/docs/fg/umn/functiongraph_03_0100.html
@@ -6,8 +6,6 @@
- What If Error Code 500 Is Reported When Functions that Use APIG Triggers Return Strings?
-- What Do LATEST and TRIM_HORIZON Mean in DIS Trigger Configuration?
-
- Why Can't I Enable or Disable OBS Triggers by Calling APIs?
- How Do I Use an APIG Trigger to Invoke a Function?
diff --git a/docs/fg/umn/functiongraph_03_0110_00.html b/docs/fg/umn/functiongraph_03_0110_00.html
index e21f6fb0b..a81a14205 100644
--- a/docs/fg/umn/functiongraph_03_0110_00.html
+++ b/docs/fg/umn/functiongraph_03_0110_00.html
@@ -10,6 +10,8 @@
- Do I Need to Deploy My Code After Programming?
+- What Runtimes Does FunctionGraph Support?
+
- How Much Disk Space Is Allocated to Each FunctionGraph Function?
- Does FunctionGraph Support Function Versioning?
diff --git a/docs/fg/umn/functiongraph_03_0240.html b/docs/fg/umn/functiongraph_03_0240.html
index e5dcffdec..3dcff8f8f 100644
--- a/docs/fg/umn/functiongraph_03_0240.html
+++ b/docs/fg/umn/functiongraph_03_0240.html
@@ -1,7 +1,7 @@
Does FunctionGraph Support Function Versioning?
-Yes. For details, see Managing Versions.
+ Yes. For details, see Configuring Versions.
diff --git a/docs/fg/umn/functiongraph_03_0260.html b/docs/fg/umn/functiongraph_03_0260.html
new file mode 100644
index 000000000..c4e47dda4
--- /dev/null
+++ b/docs/fg/umn/functiongraph_03_0260.html
@@ -0,0 +1,57 @@
+
+
+ What Runtimes Does FunctionGraph Support?
+ Table 1 lists the runtimes supported by FunctionGraph.
+ For details, see the runtime versions displayed on the console.
+
+ Table 1 Supported runtimesRuntime
+ |
+Version
+ |
+
|---|
+
+Node.js
+ |
+6.10, 8.10, 10.16, 12.13, 14.18, 16.17, 18.15, 20.15
+ |
+
+Python
+ |
+2.7, 3.6, 3.9, 3.10, 3.12
+ |
+
+Java
+ |
+8, 11, 17, 21
+ |
+
+Go
+ |
+1.x
+ |
+
+C#
+ |
+.NET Core 2.1, .NET Core 3.1, .NET Core 6.0
+ |
+
+PHP
+ |
+7.3, 8.3
+ |
+
+Custom
+ |
+-
+ |
+
+
+
+
+
+
+
diff --git a/docs/fg/umn/functiongraph_03_0280.html b/docs/fg/umn/functiongraph_03_0280.html
index ba0db89bc..34bf10bdd 100644
--- a/docs/fg/umn/functiongraph_03_0280.html
+++ b/docs/fg/umn/functiongraph_03_0280.html
@@ -3,7 +3,7 @@
What Are the Rules for Packaging a Function Project?
In addition to inline code editing, you can create a function by uploading a ZIP or JAR file, or uploading a ZIP file from OBS. For details, see Packaging Rules and Example ZIP Project Packages.
- Packaging RulesIn addition to inline code editing, you can create a function by uploading a local ZIP file or JAR file, or uploading a ZIP file from Object Storage Service (OBS). Table 1 describes the rules for packaging a function project.
+ Packaging RulesIn addition to inline code editing, you can create a function by uploading a local ZIP file or JAR file, or uploading a ZIP file from Object Storage Service (OBS). For details, see . Table 1 describes the rules for packaging a function project.
Table 1 Function project packaging rulesRuntime
|
@@ -19,7 +19,7 @@
Not supported.
|
-- If the function project files are saved under the ~/Code/ directory, select and package all files under this directory to ensure that the function handler is under the root directory after the ZIP file is decompressed.
- If the function project uses third-party dependencies, package the dependencies into a ZIP file, and import the ZIP file on the function code page. Alternatively, package the third-party dependencies and the function project files together.
+ | - If the function project files are saved under the ~/Code/ directory, select and package all files under this directory to ensure that the function handler is under the root directory after the ZIP file is decompressed.
- If the function project uses third-party dependencies, package the dependencies into a ZIP file, and import the ZIP file on the function code page. Alternatively, package the third-party dependencies and the function project files together.
|
Compress project files into a ZIP file and upload it to an OBS bucket.
|
@@ -28,30 +28,21 @@
Not supported.
|
-- If the function project files are saved under the ~/Code/ directory, select and package all files under this directory to ensure that the function handler is under the root directory after the ZIP file is decompressed.
- If the function project uses third-party dependencies, package the dependencies into a ZIP file, and import the ZIP file on the function code page. Alternatively, package the third-party dependencies and the function project files together.
+ | - If the function project files are saved under the ~/Code/ directory, select and package all files under this directory to ensure that the function handler is under the root directory after the ZIP file is decompressed.
- If the function project uses third-party dependencies, package the dependencies into a ZIP file, and import the ZIP file on the function code page. Alternatively, package the third-party dependencies and the function project files together.
|
Compress project files into a ZIP file and upload it to an OBS bucket.
|
|---|
-Python 2.7
+ | Python
|
Not supported.
|
-- If the function project files are saved under the ~/Code/ directory, select and package all files under this directory to ensure that the function handler is under the root directory after the ZIP file is decompressed.
- If the function project uses third-party dependencies, package the dependencies into a ZIP file, and import the ZIP file on the function code page. Alternatively, package the third-party dependencies and the function project files together.
+ | - If the function project files are saved under the ~/Code/ directory, select and package all files under this directory to ensure that the function handler is under the root directory after the ZIP file is decompressed.
- If the function project uses third-party dependencies, package the dependencies into a ZIP file, and import the ZIP file on the function code page. Alternatively, package the third-party dependencies and the function project files together.
|
Compress project files into a ZIP file and upload it to an OBS bucket.
|
-Python 3.6
- |
-Not supported.
- |
-- If the function project files are saved under the ~/Code/ directory, select and package all files under this directory to ensure that the function handler is under the root directory after the ZIP file is decompressed.
- If the function project uses third-party dependencies, package the dependencies into a ZIP file, and import the ZIP file on the function code page. Alternatively, package the third-party dependencies and the function project files together.
- |
-Compress project files into a ZIP file and upload it to an OBS bucket.
- |
-
-Java 8
+ | Java
|
If the function does not reference third-party components, compile only the function project files into a JAR file.
|
@@ -64,7 +55,7 @@
Not supported.
|
-Zip the compiled file and ensure that the name of the binary file is consistent with that of the handler. For example, if the name of the binary file is Handler, set the name of the handler to Handler.
+ | Zip the compiled file and ensure that the name of the binary file is consistent with that of the handler. For example, if the name of the binary file is Handler, set the name of the handler to Handler.
|
Compress project files into a ZIP file and upload it to an OBS bucket.
|
@@ -73,7 +64,7 @@
Not supported.
|
-Compress project files into a ZIP file. The ZIP file must contain the following files: Project_name.deps.json, Project_name.dll, Project_name.runtimeconfig.json, Project_name.pdb, and HC.Serverless.Function.Common.dll.
+ | Compress project files into a ZIP file. The ZIP file must contain the following files: Project_name.deps.json, Project_name.dll, Project_name.runtimeconfig.json, Project_name.pdb, and HC.Serverless.Function.Common.dll.
|
Compress project files into a ZIP file and upload it to an OBS bucket.
|
diff --git a/docs/fg/umn/functiongraph_03_0320.html b/docs/fg/umn/functiongraph_03_0320.html
deleted file mode 100644
index dadd1f267..000000000
--- a/docs/fg/umn/functiongraph_03_0320.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-What Do LATEST and TRIM_HORIZON Mean in DIS Trigger Configuration?
-Cursors LATEST and TRIM_HORIZON specify the start points for reading data in Data Ingestion Service (DIS) streams.
- - TRIM_HORIZON: Data is read from the earliest valid record stored in the partition.
For example, a tenant used a DIS stream to upload three pieces of data A1, A2, and A3. Assuming that A1 expires but A2 and A3 are still valid after a period of time, if the tenant specifies TRIM_HORIZON for downloading data, only A2 and A3 can be downloaded.
- - LATEST: Data is read from the latest record in the partition. This option ensures that the most recent data in the partition is read.
- Does FunctionGraph Support Function Extension?
FunctionGraph has integrated non-standard libraries such as redis, http, and obs_client. You can directly use these libraries when developing functions.
- Alternatively, use your own dependencies. For more information, see Dependency Management.
+ Alternatively, use your own dependencies. For more information, see Configuring Dependencies.
diff --git a/docs/fg/umn/functiongraph_03_0346.html b/docs/fg/umn/functiongraph_03_0346.html
index 9ada68fc4..b7e1cecc6 100644
--- a/docs/fg/umn/functiongraph_03_0346.html
+++ b/docs/fg/umn/functiongraph_03_0346.html
@@ -8,8 +8,6 @@
- Which Steps Are Included in Function Execution?
- - How Does FunctionGraph Process Concurrent Requests?
-
- What If Function Instances Have Not Been Executed for a Long Time?
- How Can I Speed Up Initial Access to a Function?
@@ -22,8 +20,6 @@
- How Do I Read the Request Header of a Function?
- - Why Does a Function Use More Memory Than Estimated and Even Trigger the Out of Memory Alarm?
-
- How Do I Check the Memory Usage When Seeing "runtime memory limit exceeded"?
- How Do I Troubleshoot "CrashLoopBackOff"?
diff --git a/docs/fg/umn/functiongraph_03_0348.html b/docs/fg/umn/functiongraph_03_0348.html
deleted file mode 100644
index 1fe520177..000000000
--- a/docs/fg/umn/functiongraph_03_0348.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-How Does FunctionGraph Process Concurrent Requests?
-FunctionGraph automatically scales in or out function instances based on the number of requests. If the number of concurrent requests increases, FunctionGraph allocates more function instances to process the requests. If that number decreases, FunctionGraph allocates fewer function instances accordingly.
- Number of function instances = Function concurrency/Concurrency per instance
- - Function concurrency: the number of requests concurrently executed by a function at a certain time point.
- Concurrency per instance: the maximum number of concurrent requests allowed by a single instance. This is equivalent to the Max. Requests per Instance parameter on the Concurrency page.
- Why Does a Function Use More Memory Than Estimated and Even Trigger the Out of Memory Alarm?
-- Event parsing and cache consume extra memory during function invocation.
- After the invocation is complete, reclaimed memory is often put in the internal pool instead of back to the OS, resulting in high memory usage. This is more obvious in the case of high concurrency.
- Creating a Function from Scratch and Executing the Function
This section describes how to quickly create and test a HelloWorld function on the FunctionGraph console.
- Prerequisites- Grant the FunctionGraph operation permissions to the user.
To perform the operations described in this section, ensure that you have the FunctionGraph FullAccess permissions, that is, all permissions for FunctionGraph. For more information, see Permissions Management.
+Prerequisites- Grant the FunctionGraph operation permissions to the user.
To perform the operations described in this section, ensure that you have the FunctionGraph FullAccess permissions, that is, all permissions for FunctionGraph. For more information, see section "Permissions Management".
Step 1: Create a Function- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click Create Function in the upper right corner and choose Create from scratch.
- On the displayed page, enter HelloWorld for Function Name and retain the default values for other parameters by referring to Figure 1, and click Create Function. The following describes the parameters.
- Function Type: Select Event Function.
- Region: The default value is used. You can select other regions.
Regions are geographic areas isolated from each other. Resources are region-specific and cannot be used across regions through internal network connections. For low network latency and quick resource access, select the nearest region.
- - Function Name: enter HelloWorld.
- Enterprise Project: The default value is default. You can select the created enterprise project.
Enterprise projects let you manage cloud resources and users by project.
- - Agency: By default, no agency is used. You can select an existing agency.
Specify an agency if you want to delegate FunctionGraph to access other cloud services, such as LTS and VPC.
- - Runtime: Select a runtime to compile the function. Default: Node.js 16.17. You can select another runtime.
- Advanced Settings: Collect Logs is disabled by default. If it is enabled, function execution logs will be reported to Log Tank Service (LTS). You will be billed for log management on a pay-per-use basis.
-
Table 1 Parameters for configuring Collect LogsParameter
+Step 1: Create a Function- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click Create Function in the upper right corner and choose Create from scratch.
- Configure basic function information by referring to Figure 1. Then, click Create Function.
+
Table 1 Parameters required for creating a functionParameter
|
-Description
+ | Description
+ |
+Example Value
|
|---|
-Log Configuration
+ | Function Type
|
-You can select Auto or Custom.
+ | Select Event Function.
+An event function is triggered by a specific event, which is usually a request event in JSON format.
+ |
+Event Function
+ |
+
+Region
+ |
+Select the region where the function is located.
+Regions are geographic areas isolated from each other. Resources are region-specific and cannot be used across regions through internal network connections. Select a region near you to ensure the lowest latency possible.
+ |
+eu-de
+ |
+
+Function Name
+ |
+Enter a function name. The naming rules are as follows:
+- Consists of 1 to 60 characters, and can contain letters, digits, hyphens (-), and underscores (_).
- Start with a letter and end with a letter or digit.
+ |
+HelloWorld
+ |
+
+Enterprise Project
+ |
+Select the enterprise project to which the function belongs. Enterprise projects let you manage cloud resources and users by project.
+The default value is default. You can select the created enterprise project.
+ |
+default
+ |
+
+Agency
+ |
+Select an agency for the function. An agency is used to authorize FunctionGraph to access other cloud services. If FunctionGraph does not access any cloud service, you do not need to select an agency.
+By default, Use no agency is used. You can select an existing agency.
+ |
+Use no agency
+ |
+
+Permission Policies
+ |
+This parameter is displayed only when an agency is selected.
+For details about how to adjust the permission policies on the IAM console, see section "Configuring Agency Permissions".
+ |
+-
+ |
+
+Runtime
+ |
+Select a runtime to compile the function.
+- CloudIDE supports only online editing of Node.js, Python, PHP, and custom runtimes.
- After a function is created, the runtime language cannot be changed.
+ |
+Node.js 16.17
+ |
+
+
+
+ - Advanced Settings: Collect Logs is disabled by default. If it is enabled, function execution logs will be reported to Log Tank Service (LTS). You will be billed for log management on a pay-per-use basis.
+
Table 2 Parameters for configuring Collect LogsParameter
+ |
+Description
+ |
+
|---|
+
+Log Configuration
+ |
+You can select Auto or Custom.
- Auto: Use the default log group and log stream. Log groups prefixed with "functiongraph.log.group" are filtered out.
- Custom: Select a custom log group and log stream. Log streams that are in the same enterprise project as your function.
|
-Log Tag
+ | Log Tag
|
-You can use these tags to filter function logs in LTS. You can add 10 more tags.
+ | You can use these tags to filter function logs in LTS. You can add 10 more tags.
Tag key/value: Enter a maximum of 64 characters. Only digits, letters, underscores (_), and hyphens (-) are allowed.
|
@@ -32,7 +97,8 @@
Figure 1 Configuring basic information
-- Configure the code source, copy the following code to the code window, and click Deploy.
The sample code enables you to obtain test events and print test event information. exports.handler = function (event, context, callback) {
+
+- Configure the code source, copy the following code to the code window, and click Deploy.
The sample code enables you to obtain test events and print test event information. exports.handler = function (event, context, callback) {
const error = null;
const output = `Hello message: ${JSON.stringify(event)}`;
callback(error, output);
diff --git a/docs/fg/umn/functiongraph_04_0102.html b/docs/fg/umn/functiongraph_04_0102.html
index 8646add05..25d47d87e 100644
--- a/docs/fg/umn/functiongraph_04_0102.html
+++ b/docs/fg/umn/functiongraph_04_0102.html
@@ -2,40 +2,17 @@
Creating a Function Using a Template and Executing the Function
FunctionGraph provides multiple templates to automatically complete code and running environment configurations when you create a function, helping you quickly build applications. This section uses context-class-introduction as an example.
- Prerequisites- Grant the FunctionGraph operation permissions to the user.
To perform the operations described in this section, ensure that you have the FunctionGraph FullAccess permissions, that is, all permissions for FunctionGraph. For more information, see Permissions Management.
+Prerequisites- Grant the FunctionGraph operation permissions to the user.
To perform the operations described in this section, ensure that you have the FunctionGraph FullAccess permissions, that is, all permissions for FunctionGraph. For more information, see section "Permissions Management".
Step 1: Create a Function- Log in to the FunctionGraph console. In the navigation pane, choose Functions > Function List.
- Click Create Function in the upper right corner and choose Select template.
- Select the template shown in Figure 1 and click Configure.
Figure 1 Selecting a template
-
- Set Function Name to context, select any agency from the Agency drop-down list, retain default values for other parameters, and click Create Function.
|
|---|
|
|---|
|
|---|
|
|
