After web applications are deployed, you can view the information about the web applications, including basic information, event information, logs, monitoring information, and settings. You can also associate the web applications with resources and deploy versions of the web applications.

Prerequisites

Web applications are migrated to Function Compute. For more information, see Migrate Web applications to Function Compute.

View the information about an application

  1. Log on to the Function Compute console.
  2. In the top navigation bar, select a region.
  3. In the left-side navigation pane, click Application center .
  4. In the Application center Page, click My Applications .
  5. In the My Applications Page, click the application name.
    yingyongzhongxin1
  6. On the details page of the application, view the information about the application.
    Information Operation
    Basic information

    Click the Overview tab.

    On the Overview tab, you can view the name, type, domain name, description, and template of the application, and the time when the application was created.

    Event information

    Click the Event tab.

    On the Event tab, you can view the operation records of application creation, update, rollback, and deletion events.

    Resource information

    Click the Resource tab.

    On the Resource tab, you can view the information about the services in Function Compute and resources that the application uses. You can also configure the information about the resources.

    Monitoring information

    Click the Monitoring tab.

    On the Monitoring tab, you can view the number of function invocations and the memory and time consumed for function executions within the specified time range. You can also view the numbers of times that various types of error codes are returned, and the numbers of function, system, throttling, and client errors.

    Logs

    Click the Log tab.

    On the Log tab, you can view the logs.

    Deployment information

    Click the Deployment tab.

    On the Deployment tab, you can view the major version, canary release version, and update percentage for the canary update of the application.

    Settings

    Click the Settings tab.

    On the Settings tab, you can view the parameters that you set when you create the application. In addition, you can modify the values of the parameters in the Start Command Settings section.

    Note The code package must be redeployed once for the updated start command and port number to take effect.

Associate an application with resources

To enable an application to use Log Service, ApsaraDB RDS, ApsaraDB for Redis, or Apsara File Storage NAS, you must associate the application with corresponding Alibaba Cloud services.

  1. Log on to the Function Compute console.
  2. In the top navigation bar, select a region.
  3. In the left-side navigation pane, click Application center .
  4. In the Application center Page, click My Applications .
  5. In the My Applications Page, click the application name.
    yingyongzhongxin1
  6. On the application page, click Item Tab page.
  7. Click the ianmegc icon to associate the application with related resources. Click OK.
    • Associate the application with a domain name

      After the application is created, Alibaba Cloud automatically creates a temporary domain name. You can also associate the application with a domain name.

      GUI element Description
      Section The type of the resource. Select Domain Name.
      Domain name type The type of the domain name. Valid values:
      • Use Temporary Domain Name: the temporary domain name that Alibaba Cloud automatically creates. The temporary domain name has a validity period, and the maximum number of calls allowed per day is 1,000.
      • Customize Domain Name: the custom domain name that has obtained an ICP filing from Alibaba Cloud.
      Custom Domain Name

      This parameter is required if you select Customize Domain Name.

      Enter the domain name in the format of {userId}.{regionId}.fc.aliyuncs.com.

      Example: 123456.cn-shanghai.fc.aliyuncs.com.

      Protocol

      This parameter is required if you select Customize Domain Name.

      The protocol that is used to access resources. Valid values:

      • HTTP: Only HTTP is supported.
      • HTTP,HTTPS: Both HTTP and HTTPS are supported.

      After the application is associated with the domain name, you can view the associated domain name in the Domain Name section on the Resource tab.

      link_domain_name
      Note If a temporary domain name is associated, click Extend Validity Period in the Actions column to extend the validity period of the temporary domain name for 10 days.
    • Associate the application with Log Service

      To obtain logs, you must associate the application with Log Service.

      Note Before you associate the application with Log Service, you must create a project and a Logstore in the Log Service console. For more information, see the "Step 1: Create a project and a Logstore" section of the Quick Start topic.
      GUI element Description
      Section The type of the resource. Select Log Service (SLS).
      Log Project Select the created Log Service project from the drop-down list.
      Logstore Select the created Log Service Logstore from the drop-down list.

      After the application is associated with Log Service, you can view the information about the associated project and Logstore in the Log Service (SLS) section on the Resource tab. In addition, the system synchronizes the related configuration to the corresponding service in Function Compute.

      link_sls
    • Associate the application with ApsaraDB RDS

      If you need to use a database to store data for the application, you must associate the application with ApsaraDB RDS.

      GUI element Description
      Section The type of the resource. Select ApsaraDB for RDS.
      Purchase Method The method in which the RDS instance is purchased. Valid values:
      • Surrogate: Function Compute purchases and maintains the RDS instance on behalf of you.
      • Imported: You purchase and import the RDS instance.
      • If you set the Purchase Method parameter to Surrogate, set the following parameters.
        Parameter Description
        Billing Method The billing method of the RDS instance. Valid values:
        • Pay-as-you-go: A pay-as-you-go instance is billed by hour. The hourly fee is calculated based on the instance type that you specified in the purchase order and is deducted from the balance of your Alibaba Cloud account.
        • Subscription: You must pay the subscription fee when you create a subscription instance.

        For more information about how to select a billing method, see Pricing, billable items, and billing methods.

        Zone and VSwitch Select the zone and vSwitch from the drop-down list.
        Database Engine Click MySQL. Only ApsaraDB RDS for MySQL instances are supported.
        Engine Version The version of the database engine that your business requires. Valid values:
        • 8.0
        • 5.7
        • 5.6
        • 5.5
        Edition The instance edition that your business requires. Valid values:
        • Basic Edition: provides a single node and separates computing from storage. This edition is cost-efficient.
        • High-availability Edition: adopts a highly available architecture that consists of a primary node and a secondary node. This edition is applicable to more than 80% of scenarios.

        For more information about how to select the instance edition, see Overview of ApsaraDB RDS editions.

        Storage Type The type of storage that your business requires.
        • Basic Edition supports only standard solid-state drives (SSDs).
        • High-availability Edition supports only standard SSDs and on-premises SSDs.

        For more information about how to select a storage type, see Storage types.

        Instance Family The specifications of the RDS instance. For more information about how to select specifications, see Primary instance types.
        Storage Space The size of the storage space that your business requires.
        Database Name The name of the database.
        Account Name The name of the account.
        Password The password that corresponds to the account name.
        Confirm Password Enter the password again to confirm the password.
      • If you set the Purchase Method parameter to Imported, set the following parameters.
        Parameter Description
        Instances The RDS instance to be imported.
        Note You must select an RDS instance that is deployed in the same virtual private cloud (VPC) as the application.
        Database Name The name of the database.
        Database Account The name of the account.
        Password The password that corresponds to the account name.
      After the application is associated with ApsaraDB RDS, you can view the information about the associated database in the ApsaraDB for RDS section on the Resource tab. link_RDS
      In addition, the system synchronizes the related configuration to the environment variables of the application. You can view the related information in the Environment Variable Settings section on the Settings tab. rds_environment_value
    • Associate the application with ApsaraDB for Redis

      If you need to use a database to store cached data for the application, you must associate the application with ApsaraDB for Redis.

      GUI element Description
      Section The type of the resource. Select ApsaraDB for Redis.
      Purchase Method The method in which the ApsaraDB for Redis instance is purchased. Valid values:
      • Surrogate: Function Compute purchases and maintains the ApsaraDB for Redis instance on behalf of you.
      • Imported: You purchase and import the ApsaraDB for Redis instance.
      • If you set the Purchase Method parameter to Surrogate, set the following parameters.
        Parameter Description
        Billing Method The billing method of the ApsaraDB for Redis instance. Valid values:
        • Pay-as-you-go: A pay-as-you-go instance is billed by hour. The hourly fee is calculated based on the instance type that you specified in the purchase order and is deducted from the balance of your Alibaba Cloud account.
        • Subscription: You must pay the subscription fee when you create a subscription instance.

        For more information about how to select a billing method, see Billing method.

        VSwitch Select a vSwitch from the drop-down list.
        Edition The edition of the ApsaraDB for Redis instance. Valid values:
        • Community Edition
        • Enterprise Edition

        For more information about how to select the instance edition, see What is ApsaraDB for Redis?

        Database Engine Version The version of the database engine that your business requires.
        • Valid values if you set the Edition parameter to Community Edition:
          • 5.0
          • 4.0
          • 2.8
        • Valid value if you set the Edition parameter to Enterprise Edition:
          • 5.0
        Architecture The architecture that your business requires. Valid values:
        • Standard Instance
        • Cluster Instance
        • Read/write Splitting Instance

        For more information about how to select the architecture, see Overview.

        Node Type The type of nodes that your business requires.
        • If you set the Architecture parameter to Standard Instance or Cluster Instance, only master-replica is supported.
        • If you set the Architecture parameter to Read/write Splitting Instance, only read-only nodes are supported.
        Instance Type The specifications of the ApsaraDB for Redis instance.

        For more information about how to select specifications, see Overview.

        Instance Name The name of the ApsaraDB for Redis instance.
        Password The password that corresponds to the database account.
        Confirm Password Enter the password again to confirm the password.
      • If you set the Purchase Method parameter to Imported, set the following parameters.
        Parameter Description
        ApsaraDB for Redis The ApsaraDB for Redis instance to be imported.
        Note You must select an ApsaraDB for Redis instance that is deployed in the same VPC as the application.
        Password The password that corresponds to the database account.
      After the application is associated with ApsaraDB for Redis, you can view the information about the associated database in the ApsaraDB for Redis section on the Resource tab. link_REDIS
      In addition, the system synchronizes the related configuration to the environment variables of the application. You can view the related information in the Environment Variable Settings section on the Settings tab. link_redis
    • Associate the application with Apsara File Storage NAS

      After the application is created, the system automatically associate the application with a NAS file system. You can also associate the application with a new NAS file system.

      Notice A web application must be associated with at least one NAS file system. Otherwise, the uploaded code package whose size is too large fails to be deployed.
      GUI element Description
      Section The type of the resource. Select Apsara File Storage NAS.
      UserId The user ID required to access the NAS file system.
      GroupId The ID of the user group that is required to access the NAS file system.
      NAS Mount Point The mount target created in NAS. For more information, see Manage mount targets.
      Remote Path The directory of the mount target for the NAS file system.
      Local Mount Path The directory of the on-premises mount target.
      After the application is associated with the NAS file system, you can view the information about the associated NAS file system in the Apsara File Storage NAS section on the Resource tab. In addition, the system synchronizes the related configuration to the corresponding service in Function Compute. link_NAS

Deploy versions

After the major version is released, you can release a new version. You can also configure a canary release version as needed.

  1. Log on to the Function Compute console.
  2. In the top navigation bar, select a region.
  3. In the left-side navigation pane, click Application center .
  4. In the Application center Page, click My Applications .
  5. In the My Applications Page, click the application name.
    yingyongzhongxin1
  6. Click the Deployment tab.
  7. Release a new version.
    1. Click Publish.
    2. Upload a code package and enter the version information in the Version Information section. Click OK.
      set_version_information
      GUI element Description
      Version Information Upload Code Package Click Select File and select the on-premises code package of the new version.
      Version Name The name of the new version.
      Version Description Optional. The description of the new version.
      Canary Release Weight Optional. To release a canary release version, you must turn on Canary Release Weight and set the weight of the canary release version.
      Environment Variable Key-value pair After environment variables are configured, they are deployed to the operating system where the function is runs. You can add multiple key-value pairs. For more information, see Introduction.
      You can view the major version and canary release version in the Versions section on the Deployment tab.
      Note If a canary release version exists, no new version can be released. If you need to release a new version when a canary release version exists, click Back to Major Version to roll back the version to the major version or click Full Deployment to release all canary release versions.