Enterprise Distributed Application Service (EDAS) collects and organizes logs from every deployed application and surfaces them in the EDAS console. Instead of logging on to individual Elastic Compute Service (ECS) instances or Kubernetes pods, view, search, and download logs from a single interface.
Log types
EDAS captures four categories of logs across ECS and Kubernetes clusters.
| Log type | ECS clusters | Kubernetes clusters | Default directory | Description |
|---|---|---|---|---|
| EDAS system logs | Yes | Yes | /home/admin/edas-agent/logs/ (Agent exceptions) /home/admin/edas-container/logs/ (container exits, application exceptions) | Logs generated by the EDAS platform. Use these to troubleshoot EDAS Agent errors or container-level exceptions. |
| Business logs | Yes | Yes | Custom (add to favorites) | Logs from your application's business logic. Add custom log directories to favorites to access them in the console. For details, see Add a log directory to favorites. |
| Logging framework logs | Yes | Yes | Auto-extracted from processes | EDAS system and business log files automatically extracted from running processes. These conform to standard logging frameworks such as Log4J and JDKLog. |
| Real-time logs | No | Yes | stdout | Standard output (stdout) logs generated when Docker starts and runs a container. Use these to troubleshoot pod startup and runtime issues. |
View logs
After you deploy an application to an ECS cluster or a Container Service for Kubernetes (ACK) cluster, view its logs directly in the EDAS console:
Instance logs -- View logs for a specific ECS instance or Kubernetes pod. See View instance logs.
Distributed log search -- Search across all instances of an application to locate specific log entries. See View application logs and perform distributed search.
Download logs
To analyze logs offline or archive them for diagnosis, download log files from the EDAS console to your local device.