Overview

What Is Mapping?

AOM logs exist in LTS in the form of a log stream, as shown in Figure 1. You can view raw logs in configured log collection paths on AOM, but cannot view the AOM log stream on LTS. You can create a mapping by adding an access rule on AOM. After the mapping is created, you can view and analyze AOM logs on LTS.

Figure 1 Before mapping

After you create log stream A and an access rule, the mapping from AOM to LTS is created. New AOM logs will be reported to log stream A. You can view all logs on AOM before and after the mapping. Historical logs in the AOM log stream will not be copied or migrated to log stream A, as shown in Figure 2.

Figure 2 After mapping

Modifying a Mapping

If you modify a mapping, for example, change log stream A to log stream B, new logs will be reported to log stream B. You can view the content of AOM log stream and log stream B on AOM, but cannot view the content of log stream A, as shown in Figure 3.

Figure 3 Modifying a mapping

Deleting a Mapping

When you delete an access rule or a mapped log stream, the corresponding mapping is deleted. New logs are reported only to the AOM log stream. In this case, you cannot view the content of log stream A, as shown in Figure 4. If the access rule is deleted but log stream A is not, you can still view the logs that have already been mapped on LTS.

Figure 4 Deleting a mapping

Deleted access rules or mapped log streams cannot be recovered. Exercise caution when performing this operation.

Duplicate Mapping

If a workload or file is mapped to both log streams A and B, new logs will be reported to both of them. Duplicate logs exist on AOM and will be charged. Therefore, duplicate mapping is not recommended.

Figure 5 Duplicate mapping