You may encounter various problems during application O&M. By reviewing the logs, you can locate and diagnose them. Enterprise Distributed Application Service (EDAS) provides various types of logs. You can view them online or download them.
EDAS provides the following four types of logs:
EDAS system logs (general): You can use these logs to locate and diagnose EDAS system problems. By default, the EDAS system logs are added to bookmarks, including the following two directories:
- /home/admin/edas-agent/logs/: when an EDAS Agent exception occurs, view the logs in this directory for troubleshooting.
- /home/admin/edas-container/logs/: when a container exits or an application exception occurs, view the logs in this directory for troubleshooting.
Business logs (general): You can add the related log directories and log files under this directory based on your actual business requirements for locating and diagnosing purpose. For more information, see Bookmark log directories.
Logs configured in the logging framework (general): the EDAS system and business log files that are automatically extracted from processes when an application is running. They conform to logging frameworks, such as JDKLog and Log4J.
Real-time logs (applicable to Kubernetes clusters): the standard output logs of Docker at startup and runtime to help you locate pod problems.
After your application is deployed to an Elastic Compute Service (ECS) cluster or a Container Service Kubernetes cluster, you can view logs in the EDAS console without logging on to the specific ECS instance. It is easier to locate and diagnose application run-time problems.
EDAS allows you to view logs specific to an application or an ECS instance. Specifically, application-level logs support distributed search. For more information, see the following topics:
In addition to viewing logs online, you can download logs to your local device or use log files as materials for application analysis and diagnosis.