Which Logs Can I View in APM?

Component Exception Logs

This function monitors application exception logs. Take the monitoring of Java exception logs as an example. Once you use the log system to print logs, they will be collected by APM. The exception collection type varies according to the collector type.

1. Log in to the APM console.
2. Click on the left and choose Application > Application Performance Management.
3. In the navigation pane, choose Application Monitoring > Metrics.
4. In the tree on the left, click next to the target environment.
5. Click the Exception tab. By default, exception logs of all instances are displayed. For details about the metrics, see Table 1. For details, see Exceptions.

   Table 1 Exception and log parameters

   Metric Set	Parameter	Description
   Exception	Class	Exception class
   	Exception Type	Exception type
   	Log Type	Exception log type
   	Total Exceptions	Number of times that an exception has occurred
   	Message	Message returned when the exception occurred
   	Error Stack	Error stack
   	Error Trace ID	Information about the error trace
   Log Version	Log Type	Log type
   	Version	Version

Trace Logs

This function is used to search for span information, that is, the root event of a node. A trace can be found in multiple environments. For example, in the scenario where service A calls service B and then calls service C, the same trace may be found from services A, B, and C.

To view trace logs, perform the following operations:

1. On the LTS console, configure collection. For details, see section "Ingesting ECS Text Logs to LTS" in the Log Tank Service (LTS) User Guide.
2. Click View Logs to go to the LTS page based on the trace ID. For details about how to search for logs on the LTS console, see Searching for Logs .
3. If the function of associating trace IDs with logs is not enabled, a warning dialog box is displayed. Click Associate Now to go to the log association settings page. For details about how to associate logs, see Component Settings.

apm.log

Some issues may occur during JavaAgent connection. To quickly locate and rectify these issues, view apm.log as follows:

• Log in to the node.

  cd /apm

• If apm.log is not in the apm directory, run the following command to search for the apm.log file:

  find / -name apm.log