Manage a Logstore - Cloud Monitor - Alibaba Cloud Documentation Center

Log Insight lets you manage Simple Log Service Logstores. You can associate log data with Cloud Monitor 2.0 entities, such as applications, hosts, and container groups, and other data, such as metrics and traces. This process breaks down data silos and enables unified data analysis.

Procedure

Log on to the Cloud Monitor 2.0 console, and select a workspace. In the left navigation pane, choose Application Center > Log Explorer.
Manage Logstore: Select the project and Logstore that you want to manage.
1. Project
2. Logstore
Note
Only log spaces in the current workspace are supported.
LogSet: A LogSet is a topology node in a UModel relationship diagram. It represents a collection of logs that share the same properties. By managing a Simple Log Service project and Logstore as a LogSet, you establish a topology in UModel and define field semantics and field mappings.
1. LogSet Name: The default name format for a LogSet is project - logstore. This name cannot be changed.
2. Display Name: The default display name format is project - logstore. You can change this name to one that better reflects your business needs.
3. Description: Add a description for the LogSet.
4. LogSet Data Structure: The data structure is a core part of the LogSet configuration and defines the structure of the log data. It is generated from the field index configuration of the Simple Log Service (SLS) Logstore and is used for query analysis. You can add semantic descriptions for fields to improve accuracy in scenarios such as machine learning semantic understanding.
Note
The LogSet data structure is generated from the Simple Log Service field index. Plan the log fields that you need in advance and add the corresponding indexes in Simple Log Service.
Associate Entity Set: This step establishes a topology association between the LogSet and an entity set. After they are associated, you can query log data from the LogSet within the entity set.
1. Search for an entity set. For example, for trace data, filter by the apm domain to find the apm.instrace entity set. For Kubernetes ingress data, search for acs.k8s.ingress. Find the desired entity set and click Associate.
2. After you associate an entity set, you must map the fields between the LogSet and the entity set. For example, the ip field in the LogSet might correspond to the ip_address field in the entity set. This mapping connects fields with the same semantics and is a core requirement for association analysis.
  - The chart shows the LogSet fields on the left and the associated entity set fields on the right. Connect the fields to associate them.
  - To connect a field, drag its row from the left table to a row in the right table. To disconnect a field, drag its connected row from the right table to an empty space. Each row on both sides can be part of only one connection.
After the Logstore is managed, you can find the target LogSet in the LogSet list of the log application to perform other operations.
1. To edit a LogSet, select the target LogSet and click Edit in the Operations column.
2. To delete a LogSet, select the target LogSet and click Delete in the Operations column.
3. To query data in a LogSet, click the LogSet name to go to the query analysis page.
You can go to the UModel Explorer page to view the topology of the managed LogSet and perform association analysis.