FunctionGraph allows you to run your code without provisioning or managing servers, while ensuring high availability and scalability. All you need to do is upload your code and set execution conditions, and FunctionGraph will take care of the rest.
Figure 1 shows the process of using functions.
The following shows the details:
Edit code inline, upload a local ZIP or JAR file, or upload a ZIP file from OBS. For details, see Creating a Deployment Package.
Functions are triggered by API calls or cloud service events. For details, see Creating Triggers.
FunctionGraph implements auto scaling based on the number of requests. For details, see section "Notes and Constraints".
View run logs of function. FunctionGraph is interconnected with Log Tank Service (LTS). For details, see Logs.
View graphical monitoring information. FunctionGraph is interconnected with Cloud Eye. For details, see Metrics.
Table 1 describes the function metrics.
Metric |
Unit |
Description |
---|---|---|
Invocations |
Count |
Total number of invocation requests, including invocation errors and throttled invocations. In case of asynchronous invocation, the count starts only when a function is executed in response to a request. |
Duration |
ms |
Maximum duration: the maximum duration all functions are executed at a time within a period. Minimum duration: the minimum duration all functions are executed at a time within a period. Average duration: the average duration all functions are executed at a time within a period. |
Errors |
Count |
Number of times that your functions failed with error code 200 being returned. Errors caused by function syntax or execution are also included. |
Throttles |
Count |
Number of times that FunctionGraph throttles your functions due to the resource limit. |