Enterprise Distributed Application Service (EDAS) provides O&M capabilities for applications hosted on Kubernetes clusters. From the EDAS console, manage the application lifecycle, control traffic routing, scale instances, configure throttling and degradation, track changes, monitor events, and view logs.
| Capability | Description | Learn more |
|---|---|---|
| Lifecycle management | Deploy, upgrade, roll back, start, stop, delete, and scale application instances. | Manage the application lifecycle |
| Traffic routing | Expose service ports through load balancers (external) or Kubernetes Services (internal). | Bind CLB instances |
| Instance scaling | Scale instances manually or automatically to match traffic demand. | Manual scaling, Auto scaling |
| Change records | Track deployment, startup, and scaling changes with full audit history. | View application changes |
| Event center | Collect and analyze events from EDAS, ARMS, MSE, and Kubernetes clusters in a unified view. | Event center |
| Log management | View real-time logs, browse log directories, and query file logs through Simple Log Service. | View real-time logs |
Lifecycle management
After you host an application to a Kubernetes cluster in EDAS, manage the full application lifecycle from the EDAS console:
| Action | Description |
|---|---|
| Upgrade and roll back | Deploy new application versions or revert to a previous version. |
| Start, stop, and delete | Control the running state of applications. |
| Scale out or scale in | Adjust the number of instances that run the application. |
| Edit YAML | Manage the application lifecycle at a finer granularity by editing the YAML file directly. |
For more information, see Manage the application lifecycle.
Traffic routing
Expose application service ports to handle external or internal traffic.
| Scenario | Method | Details |
|---|---|---|
| External access | Bind an Internet-facing or intranet-facing Server Load Balancer (SLB) instance to provide load balancing for traffic from outside the cluster. | Bind CLB instances, Reuse a CLB instance |
| Internal access | Add a Kubernetes Service to route traffic between applications within the cluster. | Add a Service |
Instance scaling
When traffic fluctuates, scale application instances to match demand. This improves resource utilization and reduces costs.
| Scaling method | Description | Details |
|---|---|---|
| Manual scaling | Manually scale application instances out or in. | Manual scaling |
| Auto scaling | Automatically adjust instance count to match demand. | Auto scaling |
Change records
Every lifecycle action -- deployment, startup, scaling -- is recorded and available for review.
| Location | Use case |
|---|---|
| Application details page | Check the status of a specific change. |
| Change List page | View the full change history across all actions. |
For more information, see View application changes.
Event center
The event center automatically collects events from multiple sources and displays them in a unified view:
| Event source | Examples |
|---|---|
| EDAS | Application change events |
| Application Real-Time Monitoring Service (ARMS) | Alert events |
| Application runtime (0-1 status events) | Deadlocks, out of memory (OOM), startup failures |
| Microservices Engine (MSE) | Microservice governance events |
| Kubernetes clusters | Cluster-level events |
If your application uses any of these services, events are collected and analyzed automatically.
For more information, see Event center.
Log management
EDAS provides three ways to access application logs:
| Log type | Use case | Details |
|---|---|---|
| Real-time logs | Troubleshoot pod-level issues as they happen. | View real-time logs |
| Log directories | Browse, search, and bookmark log directories across instances. | View log directories |
| File logs | Query log files through Simple Log Service integration. | View file logs |
To use file logs, enable the logging feature when you create or deploy the application.