Enterprise Distributed Application Service (EDAS) provides a series of operations and maintenance (O&M) features for applications. The features include the lifecycle management, application access management, application scaling, throttling and degradation, change records, event center, and log management.

Application O&M capabilities

Scenario Feature
Lifecycle management After you host an application to a Kubernetes cluster in EDAS, you can manage the lifecycle of the application in the EDAS console. For example, you can upgrade, roll back, scale out, scale in, start, stop, and delete the application. You can also manage the lifecycle of the application at a finer granularity by editing the YAML file. For more information, see Manage the application lifecycle.
Application access management After you host an application to a Kubernetes cluster in EDAS, you may want to expose service ports in the following two scenarios:
  • Expose the service ports externally. You can bind an Internet-facing or internal-facing Server Load Balancer (SLB) instance to the application to provide load balancing capabilities. For more information, see Bind SLB instances or Reuse an SLB instance.
  • Expose the service ports inside the cluster. You can add a service to the application to provide load balancing capabilities. For more information, see Add a service.
Application scaling If traffic fluctuates greatly, you can scale out or in applications by using manual or automatic scaling to increase or decrease the number of instances. This improves resource utilization and reduces the cost of application resources. For more information, see Manual scaling or Auto scaling.
Change record After you perform lifecycle actions in the EDAS console, such as application deployment, startup, scale-out, and scale-in, you can go to the application details page to check the change status. You can also go to the Change List page to check the historical change records of your application. For more information, see View application changes.
Event center The event center supports the following event sources: application change events of EDAS, alert events of Application Real-Time Monitoring Service (ARMS), 0-1 status events, such as deadlocks, out of memory (OOM), and application startup failures, microservice governance events of Microservice Engine (MSE), and events of Kubernetes clusters. If your application uses one of the related services, the event center automatically analyzes and displays the corresponding events in a unified manner. This provides an easy way for you to view and analyze the events. For more information, see View event details in the event center.
Log management EDAS provides the following three types of logs:
  • EDAS provides real-time logs of applications that are deployed in Kubernetes clusters in EDAS. If an application exception occurs, you can view the real-time logs to troubleshoot pod-related problems. For more information, see View real-time logs.
  • EDAS allows you to add log directories to favorites, view logs, and search for logs. You can view logs of instances and applications online to troubleshoot application exceptions. For more information, see View log directories.
  • EDAS is connected to Log Service. If you enable Log Service when you create or deploy an application, you can view the file logs of the application. For more information, see View the log file of an application.