AOM enables you to quickly query logs, and use log source information and context to locate faults.
- Log in to the management console.
- Under Application, click Application Operations Management.
- In the navigation pane, choose Log Management > Log Search.
- On the Log Search page, set filter criteria as prompted.
- You can search for logs by service, system, or host.
- For service logs, you can set filter criteria such as Cluster, Namespace, and Service. You can also click Advanced Search and set filter criteria such as Instance, Host, and File Name, and choose whether to enable Hide System Service.
- For system logs, you can set filter criteria such as Cluster and Host.
- For host logs, you can set filter criteria such as Cluster and IP Address.
- Enter a keyword in the search box. Rules are as follows:
- Enter a case-sensitive keyword.
- Enter a keyword for exact search. A keyword refers to a word between two adjacent delimiters.
- Enter a keyword containing an asterisk (*) or a question mark (?) for fuzzy search. For example, enter ER?OR, *ROR, or ER*R.
- Enter a phrase for exact search. For example, enter Start to refresh or Start-to-refresh. Note that hyphens (-) are delimiters.
- Enter a keyword containing AND (&&) or OR (||) for search. For example, enter query logs&&error* or query logs||error.
- If no log is found, you are advised to narrow down the search scope and add an asterisk (*) before and after the keyword for fuzzy match.
- You can search for logs by service, system, or host.
- View the search results of logs.
The search results are sorted based on the log collection time. The keywords in the search results are highlighted.
By default, the descending order is used. You can click
in the Time column to change the order. 
indicates the ascending order by time (that is, the latest log is displayed at the end). 
indicates the descending order by time (that is, the latest log is displayed at the top).- Click
on the left of the log list to view details such as host IP address and source. - AOM allows you to view the surrounding logs of a specified log by clicking View Context in the Operation column, facilitating fault locating. Therefore, you do not need to search for logs in raw files.
- In the Display Rows drop-down list, set the number of rows that display raw context data of the log.
For example, select 200 from the Display Rows drop-down list.
- If there are more than or equal to 100 logs printed prior to a log and more than or equal to 99 logs printed following the log, the preceding 100 logs and following 99 logs are displayed as the context.
- If there are fewer than 100 logs (for example, 90) printed prior to a log and fewer than 99 logs (for example, 80) printed following the log, the preceding 90 logs and following 80 logs are displayed as the context.
- Click Export Current Page to export displayed raw context data of the log to a local PC.
- In the Display Rows drop-down list, set the number of rows that display raw context data of the log.
To ensure that tenant hosts and services run properly, some components (for example, kube-dns) provided by the system will run on the tenant hosts. The logs of these components are also queried during tenant log query.
- Click
- (Optional) Click
on the right of the Log Search page, select an export format, and export the search result to a local PC.Logs are sorted according to the order set in 5 and a maximum of 5000 logs can be exported. For example, when 6000 logs in the search result are sorted in the descending order, only the first 5000 logs can be exported.
Logs can be exported in CSV or TXT format. You can select a format as required. If you select the CSV format, detailed information (such as the log content, host IP address, and source) can be exported, as shown in Figure 1. Only log content will be exported when you select the TXT format (as shown in Figure 2). Each line indicates a log.
