You can perform lifecycle management on applications in the Enterprise Distributed Application Service (EDAS) console, such as application deployment, startup, and scaling. You can view the changes in the application lifecycle on the application details page or go to the Change List page to view change records.

View change details

This section describes how to view application changes during application deployment.

  1. After you perform the application change, return to the Application Overview page.
    In the upper part of the Application Overview page, the message Application change in progress...View Details appears.
  2. Click View Details to view the detailed process of the application change.
    • If the process is in the Progressing, Executed, or Fail state, and this state is not in line with your expectations, click RollBack in the upper-right corner to roll back the application instances to the previous version.
    • You can click Termination in the upper-right corner to stop the rollback process. After the rollback is terminated, you can deploy the application of a version that you want to use to fix the issue. For more information about how to deploy an application, see Overview.
    • Change overview in the release sheet (section 1 in the figure): an overview of the latest change. You can also view a previous change by selecting it from the drop-down list. To view more change records, click ReleaseSheet in recent three months. This section displays the ProcessID, BatchesReleased, Batch processing mode, Execution status, and Publisher fields of the selected change. For more information, see Table 1.
    • Change subitems (section 2 in the figure): different types of resources involved in this change. A blue icon indicates that the resource change is in progress, a green icon indicates that the resource change succeeded, and a red icon indicates that the resource change failed. For more information, see Table 2.

      If a release is in progress, the console page refreshes periodically to display the latest change status. If the refresh affects troubleshooting or event observation, you can turn off StatusRefresh in the upper-right corner of section 2 on the page. If StatusRefresh is turned off, the page does not refresh but the change process still continues in the background.

    • Detailed resource changes (section 3 in the figure): the change information of the current release batch, resource information, application metrics, application exceptions, and system metrics. You can obtain the release status in this section during the change process. This information can be used for troubleshooting. For more information, see Table 3.
    Table 1. Change overview
    Field Description
    ProcessID The ID is the unique identifier of the release sheet. If an unknown exception occurs, you can submit this ID to the EDAS technical support team for troubleshooting.
    BatchesReleased If your application is deployed on multiple instances, you can use a phased release or canary release policy to change the application. This field specifies the number of batches.
    Batch processing mode You can switch between automatic or manual release for different batches if a phased release or canary release policy is used.
    Execution status The change state can be Progressing, Executed, Fail, or Terminated.
    • Progressing: indicates that the change is in progress.
    • Executed: indicates that the change process is complete.
    • Fail: indicates that the change failed due to an exception. For example, an image fails to be pulled, or resources are insufficient in a pod.
    • Terminated: indicates that a pending change process is terminated by a rollback operation. You can also click Termination to stop the rollback process.
    Publisher The operator that performs the application change.
    Release time The start time of the change.
    Description The version of the change.
    Change type The action type of the application change.
    Table 2. Resources and descriptions
    Resource Description
    Rollout Used to control underlying Kubernetes workloads, such as stateless Deployments.
    ServiceTrait Used to configure the service of Kubernetes or Server Load Balancer (SLB).
    ImageBuilder Used to create images for WAR or JAR applications.
    LogCollector Used to configure log collection.
    DynamicLabel Used to configure the end-to-end canary release.
    AutoScaling Used to configure auto scaling.
    Table 3. Detailed resource changes
    Tab Description
    Cur Information Of Batch Displays the information about the underlying pods involved in this change. You can view pod monitoring results, events, and logs, and check the execution status of the pods that are listed. If the pod change fails, click Failure Analysis to obtain the related information. For information about troubleshooting, see Troubleshooting of failed EDAS application changes.
    Resource Information Displays the events and details of the resource change. Resources are displayed on the left side of the Resource Information tab. Resources are grouped in a hierarchical structure based on their relationships. Grouped resources are managed by the parent resource under which they are grouped. The top-level resource in the hierarchy tree is used for the changes of all applications. You can click a resource in the hierarchy tree to view specific events or resource details.
    ApplicationIndex Displays the overall metrics of the application, including the response time, number of requests, and number of errors.
    Application Exception Displays the exceptions in the application.
    SystemIndex Displays the CPU utilization and memory usage before and after the application deployment.

View application change records

  1. Log on to the EDAS console.
  2. On the Application Overview page, click Change List in the left-side navigation pane.

    The Change Records page displays all change information of the application, including the Change Type, Release time, and Execution status fields and icons or fields in the Change sub item and Single batch deployment sections.