diff --git a/docs/lts/umn/ALL_META.TXT.json b/docs/lts/umn/ALL_META.TXT.json
index 8c8af207..06f6b830 100644
--- a/docs/lts/umn/ALL_META.TXT.json
+++ b/docs/lts/umn/ALL_META.TXT.json
@@ -1,481 +1,1520 @@
[
+ {
+ "dockw":"User Guide"
+ },
{
"uri":"lts_01_0001.html",
+ "node_id":"lts_01_0001.xml",
"product_code":"lts",
"code":"1",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"Service Overview",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Service Overview",
"githuburl":""
},
{
"uri":"lts_01_0002.html",
+ "node_id":"lts_01_0002.xml",
"product_code":"lts",
"code":"2",
- "des":"Log Tank Service (LTS) enables you to collect logs from hosts and cloud services for centralized management, and analyze large volumes of logs efficiently, securely, and ",
+ "des":"Log Tank Service (LTS) is a high-performance, cost-effective log platform with diverse functions and high reliability. It offers full-stack log collection, search through",
"doc_type":"productdesc",
- "kw":"Introduction,Service Overview,User Guide",
- "title":"Introduction",
+ "kw":"What Is LTS?,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"productdesc"
+ }
+ ],
+ "title":"What Is LTS?",
"githuburl":""
},
{
"uri":"lts_01_0003.html",
+ "node_id":"lts_01_0003.xml",
"product_code":"lts",
"code":"3",
- "des":"A log group is the basic unit for LTS to manage logs. You can query and transfer logs in log groups. Up to 100 log groups can be created in your account.Up to 100 streams",
+ "des":"A log group is a collection of log streams. It is similar to a folder and is used to classify and manage log streams. You can create log streams in a log group.A log stre",
"doc_type":"usermanual",
"kw":"Basic Concepts,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Basic Concepts",
"githuburl":""
},
{
"uri":"lts_01_0004.html",
+ "node_id":"lts_01_0004.xml",
"product_code":"lts",
"code":"4",
- "des":"You can view real-time logs to keep track of the status of the services connected to LTS. You can also check logs in the last 7 days.You can set search criteria to filter",
+ "des":"Before using LTS, learn its main features in Table 1.",
"doc_type":"productdesc",
- "kw":"Basic Functions,Service Overview,User Guide",
- "title":"Basic Functions",
+ "kw":"Features,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"productdesc"
+ }
+ ],
+ "title":"Features",
"githuburl":""
},
{
"uri":"lts-0740.html",
+ "node_id":"lts-0740.xml",
"product_code":"",
"code":"5",
"des":"This section describes the restrictions on LTS log read/write.",
"doc_type":"",
"kw":"Usage Restrictions,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
"title":"Usage Restrictions",
"githuburl":""
},
{
"uri":"lts-03205.html",
+ "node_id":"lts-03205.xml",
"product_code":"lts",
"code":"6",
- "des":"If you need to assign different permissions to employees in your enterprise to access your LTS resources, is a good choice for fine-grained permissions management. IAM p",
+ "des":"If you need to grant your enterprise personnel permission to access your LTS resources, use Identity and Access Management (IAM). IAM provides identity authentication, fi",
"doc_type":"productdesc",
- "kw":"Permissions Management,Service Overview,User Guide",
- "title":"Permissions Management",
+ "kw":"Permissions,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"productdesc"
+ }
+ ],
+ "title":"Permissions",
"githuburl":""
},
{
"uri":"lts_01_0005.html",
+ "node_id":"lts_01_0005.xml",
"product_code":"lts",
"code":"7",
- "des":"LTS provides a platform to store and analyze log data for Virtual Private Cloud (VPC). After VPC is associated with a log group and log stream in LTS, Network Interface C",
+ "des":"The relationships between LTS and other services are described in Table 1.",
"doc_type":"productdesc",
"kw":"Related Services,Service Overview,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"productdesc",
+ "prodname":"lts"
+ }
+ ],
"title":"Related Services",
"githuburl":""
},
{
"uri":"lts_01_0008.html",
+ "node_id":"lts_01_0008.xml",
"product_code":"lts",
"code":"8",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"Getting Started",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Getting Started",
"githuburl":""
},
{
- "uri":"lts_01_0009.html",
+ "uri":"lts_08300.html",
+ "node_id":"lts_08300.xml",
"product_code":"lts",
"code":"9",
- "des":"A Virtual Private Cloud (VPC) flow log captures information about the traffic going to and from your VPC. You can use flow logs to monitor network traffic, analyze networ",
+ "des":"To help you quickly get started with Log Tank Service (LTS), the following sections will show you how to install ICAgent on a Linux host and ingest logs from the host to ",
"doc_type":"usermanual",
- "kw":"Configuring the VPC Flow Log Function,Getting Started,User Guide",
- "title":"Configuring the VPC Flow Log Function",
+ "kw":"Overview,Getting Started,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Overview",
"githuburl":""
},
{
- "uri":"lts_01_0010.html",
+ "uri":"lts_08301.html",
+ "node_id":"lts_08301.xml",
"product_code":"lts",
"code":"10",
- "des":"This section describes how to enable trace analysis on the Cloud Trace Service (CTS) console to report traces to LTS, so you can query the traces on the LTS console.Opera",
+ "des":"You have obtained an account and its password for logging in to the console.Log in to the management console and choose Management & Deployment > Log Tank Service.On the ",
"doc_type":"usermanual",
- "kw":"Configuring CTS to Upload Traces to LTS,Getting Started,User Guide",
- "title":"Configuring CTS to Upload Traces to LTS",
+ "kw":"Creating Log Groups and Log Streams,Getting Started,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Creating Log Groups and Log Streams",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_0829.html",
+ "node_id":"lts_0829.xml",
+ "product_code":"lts",
+ "code":"11",
+ "des":"ICAgent is the log collection tool of LTS. Install ICAgent on a host from which you want to collect logs.If ICAgent has been installed on the host when you use other clou",
+ "doc_type":"usermanual",
+ "kw":"Installing ICAgent,Getting Started,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Installing ICAgent",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_08302.html",
+ "node_id":"lts_08302.xml",
+ "product_code":"lts",
+ "code":"12",
+ "des":"The following shows how you can ingest host logs to LTS.When ICAgent is installed, configure the paths of host logs that you want to collect in log streams. ICAgent will ",
+ "doc_type":"usermanual",
+ "kw":"Ingesting Logs,Getting Started,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Ingesting Logs",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_08303.html",
+ "node_id":"lts_08303.xml",
+ "product_code":"lts",
+ "code":"13",
+ "des":"After the log ingestion is configured, you can view the reported logs on the LTS console in real time.You have created log groups and log streams.You have installed ICAge",
+ "doc_type":"usermanual",
+ "kw":"Viewing Logs in Real Time,Getting Started,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Viewing Logs in Real Time",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0015.html",
+ "node_id":"lts_04_0015.xml",
+ "product_code":"lts",
+ "code":"14",
+ "des":"You can use Identity and Access Management (IAM) for fine-grained permissions control for your LTS. With IAM, you can:Create IAM users for personnel based on your enterpr",
+ "doc_type":"usermanual",
+ "kw":"Granting LTS Permissions to IAM Users,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Granting LTS Permissions to IAM Users",
"githuburl":""
},
{
"uri":"lts_04_1053.html",
+ "node_id":"lts_04_1053.xml",
"product_code":"",
- "code":"11",
+ "code":"15",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"",
"kw":"Log Management",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
"title":"Log Management",
"githuburl":""
},
{
"uri":"lts_04_1153.html",
+ "node_id":"lts_04_1153.xml",
"product_code":"",
- "code":"12",
- "des":"The LTS console provides resource statistics, your favorite log streams/favorite log streams (local cache), and recently visited log streams.This area shows the read/writ",
+ "code":"16",
+ "des":"LTS manages logs by log group and stream for easy classification. Before using LTS, create a log group and then multiple log streams in the group. By collecting and stori",
"doc_type":"",
- "kw":"LTS Console,Log Management,User Guide",
- "title":"LTS Console",
- "githuburl":""
- },
- {
- "uri":"lts_04_1154.html",
- "product_code":"",
- "code":"13",
- "des":"Log resource statistics are classified into read/write traffic, index traffic, and log volume. The statistics are for reference only. You can also visualize log resource ",
- "doc_type":"",
- "kw":"Resource Statistics,Log Management,User Guide",
- "title":"Resource Statistics",
+ "kw":"Overview,Log Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Overview",
"githuburl":""
},
{
"uri":"lts_04_0003.html",
+ "node_id":"lts_04_0003.xml",
"product_code":"lts",
- "code":"14",
- "des":"A log group is a group of log streams. Up to 100 log groups can be created for a single account.Log groups can be created in two ways. They are automatically created when",
+ "code":"17",
+ "des":"A log group is the basic unit for LTS to manage logs. It classifies and consists of log streams, but does not store any log data. Up to 100 log groups can be created for ",
"doc_type":"usermanual",
"kw":"Managing Log Groups,Log Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Managing Log Groups",
"githuburl":""
},
{
"uri":"lts_04_0004.html",
+ "node_id":"lts_04_0004.xml",
"product_code":"lts",
- "code":"15",
- "des":"A log stream is the basic unit for reading and writing logs. Sorting logs into different log streams makes it easier to find specific logs when you need them.Up to 100 lo",
+ "code":"18",
+ "des":"LTS manages logs by log stream. Collected logs of different types are classified and stored in different log streams for easier log management. If there are a large numbe",
"doc_type":"usermanual",
"kw":"Managing Log Streams,Log Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Managing Log Streams",
"githuburl":""
},
+ {
+ "uri":"lts_04_1154.html",
+ "node_id":"lts_04_1154.xml",
+ "product_code":"",
+ "code":"19",
+ "des":"The log management page displays resource statistics, your favorite log streams/favorite log streams (local cache), alarm statistics, latest alarms, and recently viewed l",
+ "doc_type":"",
+ "kw":"Viewing Log Management,Log Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Viewing Log Management",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_1217.html",
+ "node_id":"lts_04_1217.xml",
+ "product_code":"",
+ "code":"20",
+ "des":"You can tag log groups, log streams, host groups, and log ingestion configurations.Users can add, delete, modify, and query tags on the log group page.Log in to the manag",
+ "doc_type":"",
+ "kw":"Managing Tags,Log Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Managing Tags",
+ "githuburl":""
+ },
{
"uri":"lts_02_0030.html",
+ "node_id":"lts_02_0030.xml",
"product_code":"lts",
- "code":"16",
+ "code":"21",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"Log Ingestion",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Log Ingestion",
"githuburl":""
},
{
"uri":"lts_04_0105.html",
+ "node_id":"lts_04_0105.xml",
"product_code":"lts",
- "code":"17",
+ "code":"22",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
- "kw":"Collecting Logs from Cloud Services",
- "title":"Collecting Logs from Cloud Services",
+ "kw":"Ingesting Cloud Service Logs to LTS",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Ingesting Cloud Service Logs to LTS",
"githuburl":""
},
{
"uri":"lts_04_0511.html",
+ "node_id":"lts_04_0511.xml",
"product_code":"",
- "code":"18",
- "des":"LTS can collect logs from Cloud Container Engine (CCE).ICAgent has been installed and added to the host group.You have disabled Output to AOM.CCE cluster nodes whose cont",
+ "code":"23",
+ "des":"CCE provides highly scalable, high-performance, enterprise-class Kubernetes clusters. With CCE, you can easily deploy, manage, and scale containerized applications.After ",
"doc_type":"",
- "kw":"Collecting Logs from CCE,Collecting Logs from Cloud Services,User Guide",
- "title":"Collecting Logs from CCE",
+ "kw":"Ingesting CCE Application Logs to LTS,Ingesting Cloud Service Logs to LTS,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Ingesting CCE Application Logs to LTS",
"githuburl":""
},
{
"uri":"lts_04_1031.html",
+ "node_id":"lts_04_1031.xml",
"product_code":"",
- "code":"19",
- "des":"ICAgent collects logs from hosts based on your specified collection rules, and packages and sends the collected log data to LTS on a log stream basis. You can view logs o",
+ "code":"24",
+ "des":"Elastic Cloud Server (ECS) provides scalable, on-demand cloud servers to build secure, flexible, and efficient environment for your applications.After you configure ECS l",
"doc_type":"",
- "kw":"Collecting Logs from ECS,Collecting Logs from Cloud Services,User Guide",
- "title":"Collecting Logs from ECS",
+ "kw":"Ingesting ECS Text Logs to LTS,Ingesting Cloud Service Logs to LTS,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Ingesting ECS Text Logs to LTS",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_1121.html",
+ "node_id":"lts_04_1121.xml",
+ "product_code":"",
+ "code":"25",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Other Ingestion Modes",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Other Ingestion Modes",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_1112.html",
+ "node_id":"lts_04_1112.xml",
+ "product_code":"",
+ "code":"26",
+ "des":"If you choose Cross-Account Ingestion - Log Stream Mapping as the log ingestion type, you can create an agency to map the log stream of the delegator account to that of t",
+ "doc_type":"",
+ "kw":"Ingesting Logs to LTS Across IAM Accounts,Other Ingestion Modes,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Ingesting Logs to LTS Across IAM Accounts",
"githuburl":""
},
{
"uri":"lts_02_1032.html",
+ "node_id":"lts_02_1032.xml",
"product_code":"",
- "code":"20",
+ "code":"27",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"",
"kw":"Host Management",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
"title":"Host Management",
"githuburl":""
},
{
"uri":"lts_02_1033.html",
+ "node_id":"lts_02_1033.xml",
"product_code":"",
- "code":"21",
- "des":"Host groups allow you to configure host log ingestion efficiently. You can sort multiple hosts to a host group and associate the host group with log ingestion configurati",
+ "code":"28",
+ "des":"Host groups allow you to configure host log ingestion efficiently. You can add multiple hosts to a host group and associate the host group with log ingestion configuratio",
"doc_type":"",
"kw":"Managing Host Groups,Host Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
"title":"Managing Host Groups",
"githuburl":""
},
{
"uri":"lts_04_0012.html",
+ "node_id":"lts_04_0012.xml",
"product_code":"",
- "code":"22",
+ "code":"29",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"",
"kw":"Managing Hosts",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
"title":"Managing Hosts",
"githuburl":""
},
{
"uri":"lts_02_0013.html",
+ "node_id":"lts_02_0013.xml",
"product_code":"lts",
- "code":"23",
- "des":"ICAgent is a log collection tool for LTS. To use LTS to collect logs from hosts, you need to install ICAgent on the hosts.Ensure that the time and time zone of your local",
+ "code":"30",
+ "des":"To use LTS to collect logs (such as host metrics, container metrics, node logs, container logs, and standard output logs) from intra-region hosts, you need to install ICA",
"doc_type":"usermanual",
- "kw":"Installing ICAgent,Managing Hosts,User Guide",
- "title":"Installing ICAgent",
+ "kw":"Installing ICAgent (Intra-Region Hosts),Managing Hosts,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Installing ICAgent (Intra-Region Hosts)",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_02_0828.html",
+ "node_id":"lts_02_0828.xml",
+ "product_code":"lts",
+ "code":"31",
+ "des":"ICAgent is a log collection tool for LTS. To use LTS to collect logs from extra-region hosts, you need to install ICAgent on the hosts.Before installing ICAgent, ensure t",
+ "doc_type":"usermanual",
+ "kw":"Installing ICAgent (Extra-Region Hosts),Managing Hosts,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Installing ICAgent (Extra-Region Hosts)",
"githuburl":""
},
{
"uri":"lts_02_0014.html",
+ "node_id":"lts_02_0014.xml",
"product_code":"lts",
- "code":"24",
- "des":"To deliver a better collection experience, LTS regularly upgrades ICAgent. When LTS prompts you that a new ICAgent version is available, you can follow the directions her",
+ "code":"32",
+ "des":"After ICAgent is installed, you can upgrade and uninstall it, and view its status.To deliver a better collection experience, LTS regularly upgrades ICAgent. When LTS prom",
"doc_type":"usermanual",
- "kw":"Upgrading ICAgent,Managing Hosts,User Guide",
- "title":"Upgrading ICAgent",
- "githuburl":""
- },
- {
- "uri":"lts_02_0015.html",
- "product_code":"lts",
- "code":"25",
- "des":"If ICAgent is uninstalled from a host, log collection will be affected. Exercise caution when performing this operation.Only ICAgent installed on Linux hosts can be unins",
- "doc_type":"usermanual",
- "kw":"Uninstalling ICAgent,Managing Hosts,User Guide",
- "title":"Uninstalling ICAgent",
- "githuburl":""
- },
- {
- "uri":"lts_04_0013.html",
- "product_code":"lts",
- "code":"26",
- "des":"The following table lists the ICAgent statuses.",
- "doc_type":"usermanual",
- "kw":"ICAgent Statuses,Managing Hosts,User Guide",
- "title":"ICAgent Statuses",
+ "kw":"Managing ICAgent,Managing Hosts,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Managing ICAgent",
"githuburl":""
},
{
"uri":"lts_05_0004.html",
+ "node_id":"lts_05_0004.xml",
"product_code":"lts",
- "code":"27",
+ "code":"33",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
- "kw":"Log Search and View",
- "title":"Log Search and View",
+ "kw":"Log Search and Analysis",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Log Search and Analysis",
"githuburl":""
},
{
- "uri":"lts_05_0005.html",
+ "uri":"lts_05_0100.html",
+ "node_id":"lts_05_0100.xml",
"product_code":"",
- "code":"28",
- "des":"Follow the directions below to search logs by keyword and time range:On the LTS console, choose Log Management in the navigation pane on the left.In the log group list, c",
+ "code":"34",
+ "des":"Log search and analysis are indispensable to O&M. After configuring log ingestion, you can search and analyze the collected log data on LTS. Its efficient and professiona",
"doc_type":"",
- "kw":"Log Search,Log Search and View,User Guide",
- "title":"Log Search",
+ "kw":"Overview,Log Search and Analysis,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Overview",
"githuburl":""
},
{
- "uri":"lts_05_0006.html",
- "product_code":"lts",
- "code":"29",
- "des":"You can view reported logs on the LTS console in real time.You have created log groups and log streams.You have installed ICAgent.You have configured log collection rules",
- "doc_type":"usermanual",
- "kw":"Viewing Real-Time Logs,Log Search and View,User Guide",
- "title":"Viewing Real-Time Logs",
- "githuburl":""
- },
- {
- "uri":"lts_05_0009.html",
- "product_code":"lts",
- "code":"30",
- "des":"To search for logs using a keyword repeatedly, perform the following operations to configure quick search.On the LTS console, choose Log Management in the navigation pane",
- "doc_type":"usermanual",
- "kw":"Quick Search,Log Search and View,User Guide",
- "title":"Quick Search",
- "githuburl":""
- },
- {
- "uri":"lts_05_0007.html",
- "product_code":"lts",
- "code":"31",
- "des":"Monitoring keywords in logs helps you keep track of system performance and services. For example, the number of ERROR keywords indicates the system health, and the number",
- "doc_type":"usermanual",
- "kw":"Quick Analysis,Log Search and View,User Guide",
- "title":"Quick Analysis",
- "githuburl":""
- },
- {
- "uri":"lts_04_0002.html",
- "product_code":"lts",
- "code":"32",
- "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
- "doc_type":"usermanual",
- "kw":"Log Analysis",
- "title":"Log Analysis",
+ "uri":"lts_05_0008.html",
+ "node_id":"lts_05_0008.xml",
+ "product_code":"",
+ "code":"35",
+ "des":"An index is a storage structure used to query and analyze logs. Different index settings will generate different query and analysis results. Configure the index settings ",
+ "doc_type":"",
+ "kw":"Setting Indexes,Log Search and Analysis,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Setting Indexes",
"githuburl":""
},
{
"uri":"lts_0821.html",
- "product_code":"lts",
- "code":"33",
+ "node_id":"lts_0821.xml",
+ "product_code":"",
+ "code":"36",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Setting Cloud Structuring Parsing",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Setting Cloud Structuring Parsing",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_0822.html",
+ "node_id":"lts_0822.xml",
+ "product_code":"",
+ "code":"37",
"des":"Log data can be structured or unstructured. Structured data is quantitative data or can be defined by unified data models. It has a fixed length and format. Unstructured ",
+ "doc_type":"",
+ "kw":"Overview,Setting Cloud Structuring Parsing,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Overview",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_0823.html",
+ "node_id":"lts_0823.xml",
+ "product_code":"",
+ "code":"38",
+ "des":"LTS provides five log structuring modes: regular expressions, JSON, delimiters, Nginx, and structuring templates. You can make your choice flexibly.Regular Expressions: T",
+ "doc_type":"",
+ "kw":"Setting Cloud Structuring Parsing,Setting Cloud Structuring Parsing,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Setting Cloud Structuring Parsing",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_0824.html",
+ "node_id":"lts_0824.xml",
+ "product_code":"",
+ "code":"39",
+ "des":"LTS supports two types of structuring templates: system and custom templates.You can choose from multiple system templates, but cannot modify the field types in them or d",
+ "doc_type":"",
+ "kw":"Setting a Structuring Template,Setting Cloud Structuring Parsing,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Setting a Structuring Template",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_0825.html",
+ "node_id":"lts_0825.xml",
+ "product_code":"",
+ "code":"40",
+ "des":"You can set extracted fields after cloud structuring. For details, see Table 1.When you use regular expressions (manually entered), JSON, delimiters, Nginx, or custom tem",
+ "doc_type":"",
+ "kw":"Setting Structured and Tag Fields,Setting Cloud Structuring Parsing,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Setting Structured and Tag Fields",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_0826.html",
+ "node_id":"lts_0826.xml",
+ "product_code":"",
+ "code":"41",
+ "des":"When configuring log ingestion, you can enable User-defined log time to set a time field in the logs as the ingestion configuration time.A time deviation may occur around",
+ "doc_type":"",
+ "kw":"Setting User-defined Log Time,Setting Cloud Structuring Parsing,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Setting User-defined Log Time",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_05_0110.html",
+ "node_id":"lts_05_0110.xml",
+ "product_code":"",
+ "code":"42",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Searching Logs",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Searching Logs",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_05_0005.html",
+ "node_id":"lts_05_0005.xml",
+ "product_code":"",
+ "code":"43",
+ "des":"After configuring log structuring parsing and indexing, you can enter statements to search for log records that contain specific keywords. You can also search for log dat",
+ "doc_type":"",
+ "kw":"Accessing the Log Search Page,Searching Logs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Accessing the Log Search Page",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_05_0111.html",
+ "node_id":"lts_05_0111.xml",
+ "product_code":"",
+ "code":"44",
+ "des":"LTS provides a range of search syntax to set search criteria and filtering rules for filtering records that meet the search criteria. Then, you can apply analysis stateme",
+ "doc_type":"",
+ "kw":"Using LTS Search Syntax,Searching Logs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Using LTS Search Syntax",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_05_0009.html",
+ "node_id":"lts_05_0009.xml",
+ "product_code":"lts",
+ "code":"45",
+ "des":"If you need to repeatedly use a keyword to search for logs, you can set and save the keyword as a quick query statement for faster log querying and analysis.A quick searc",
"doc_type":"usermanual",
- "kw":"Log Structuring,Log Analysis,User Guide",
- "title":"Log Structuring",
+ "kw":"Saving Conditions for Quick Search,Searching Logs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Saving Conditions for Quick Search",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_05_0007.html",
+ "node_id":"lts_05_0007.xml",
+ "product_code":"lts",
+ "code":"46",
+ "des":"Logs contain information such as system performance and business status. For example, the frequency of keyword ERROR indicates the system health, and the frequency of key",
+ "doc_type":"usermanual",
+ "kw":"Creating an LTS Quick Analysis Task,Searching Logs,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Creating an LTS Quick Analysis Task",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_05_0006.html",
+ "node_id":"lts_05_0006.xml",
+ "product_code":"lts",
+ "code":"47",
+ "des":"Logs are reported to LTS about every minute, allowing you to view them on the Real-Time Logs page within 1 minute after configuring log ingestion. This enables rapid sear",
+ "doc_type":"usermanual",
+ "kw":"Viewing Real-Time Logs,Log Search and Analysis,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Viewing Real-Time Logs",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0057.html",
+ "node_id":"lts_04_0057.xml",
+ "product_code":"lts",
+ "code":"48",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Log Alarms",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Log Alarms",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_1122.html",
+ "node_id":"lts_04_1122.xml",
+ "product_code":"",
+ "code":"49",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Alarm Rules",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Alarm Rules",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0062.html",
+ "node_id":"lts_04_0062.xml",
+ "product_code":"",
+ "code":"50",
+ "des":"You can set alarm rules based on keywords in log streams to monitor service status in real time. Currently, up to 200 keyword alarms can be created for each account.A log",
+ "doc_type":"",
+ "kw":"Configuring Log Alarm Rules,Alarm Rules,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring Log Alarm Rules",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_1123.html",
+ "node_id":"lts_04_1123.xml",
+ "product_code":"",
+ "code":"51",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Configuring Log Alarm Notifications",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Configuring Log Alarm Notifications",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_06_0011.html",
+ "node_id":"lts_06_0011.xml",
+ "product_code":"",
+ "code":"52",
+ "des":"A message template defines the format of alarm notification messages sent to subscribers. LTS provides built-in keywords_template and sql_template. Subscribers can select",
+ "doc_type":"",
+ "kw":"Creating a Message Template on the LTS Console,Configuring Log Alarm Notifications,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Creating a Message Template on the LTS Console",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_02_0926.html",
+ "node_id":"lts_02_0926.xml",
+ "product_code":"aom",
+ "code":"53",
+ "des":"LTS allows you to customize alarm action rules. You can create an alarm action rule to associate an SMN topic with a message template. You can also customize notification",
+ "doc_type":"usermanual",
+ "kw":"Creating an Alarm Action Rule,Configuring Log Alarm Notifications,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "IsBot":"Yes",
+ "prodname":"aom",
+ "opensource":"true",
+ "documenttype":"usermanual",
+ "IsMulti":"Yes"
+ }
+ ],
+ "title":"Creating an Alarm Action Rule",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0060.html",
+ "node_id":"lts_04_0060.xml",
+ "product_code":"lts",
+ "code":"54",
+ "des":"LTS allows you to configure keyword alarm rules to periodically query log data. When an alarm rule is met, an alarm will be reported. You can view the alarms on the LTS c",
+ "doc_type":"usermanual",
+ "kw":"Viewing Alarms in LTS,Log Alarms,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Viewing Alarms in LTS",
"githuburl":""
},
{
"uri":"lts_04_0040.html",
+ "node_id":"lts_04_0040.xml",
"product_code":"lts",
- "code":"34",
+ "code":"55",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"Log Transfer",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Log Transfer",
"githuburl":""
},
{
"uri":"lts_04_0011.html",
+ "node_id":"lts_04_0011.xml",
"product_code":"lts",
- "code":"35",
- "des":"Logs reported from hosts and cloud services are retained in LTS for seven days by default. You can set the retention period to be 1 to 30 days. Retained logs are deleted ",
+ "code":"56",
+ "des":"Logs reported from hosts and cloud services are retained in LTS. You can set the retention period. Retained logs are deleted once the retention period is over. For long-t",
"doc_type":"usermanual",
"kw":"Overview,Log Transfer,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Overview",
"githuburl":""
},
{
"uri":"lts_04_0041.html",
+ "node_id":"lts_04_0041.xml",
"product_code":"lts",
- "code":"36",
- "des":"You can transfer logs to OBS and download log files from the OBS console.To transfer logs, you must have the OBS Administrator permissions apart from the LTS permissions.",
+ "code":"57",
+ "des":"You can transfer logs to OBS and download log files from the OBS console. You can choose scheduled or one-time transfers.To use this function, you must have the OBS Admin",
"doc_type":"usermanual",
"kw":"Transferring Logs to OBS,Log Transfer,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Transferring Logs to OBS",
"githuburl":""
},
- {
- "uri":"lts_04_0043.html",
- "product_code":"lts",
- "code":"37",
- "des":"You can use DMS APIs to retrieve logs in real time.Logs have been ingested to LTS.Before registering a DMS Kafka instance, configure an inbound rule to allow access from ",
- "doc_type":"usermanual",
- "kw":"Transferring Logs to DMS,Log Transfer,User Guide",
- "title":"Transferring Logs to DMS",
- "githuburl":""
- },
{
"uri":"lts_06_0003.html",
+ "node_id":"lts_06_0003.xml",
"product_code":"",
- "code":"38",
+ "code":"58",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"",
"kw":"Configuration Center",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
"title":"Configuration Center",
"githuburl":""
},
{
- "uri":"lts_05_0003.html",
- "product_code":"",
- "code":"39",
- "des":"To reduce the memory, database, and disk space usage, you can set log collection as required. The log collection switch is used to determine whether to collect log data.T",
- "doc_type":"",
- "kw":"Log Collection,Configuration Center,User Guide",
- "title":"Log Collection",
+ "uri":"lts_0904.html",
+ "node_id":"lts_0904.xml",
+ "product_code":"lts",
+ "code":"59",
+ "des":"When the monthly free quota (500 MB) is used up, you will be billed for any excess usage on a pay-per-use basis. To avoid extra expenses, you can configure log collection",
+ "doc_type":"usermanual",
+ "kw":"Setting LTS Log Collection Quota,Configuration Center,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Setting LTS Log Collection Quota",
"githuburl":""
},
{
- "uri":"lts_04_0015.html",
+ "uri":"lts_04_0052.html",
+ "node_id":"lts_04_0052.xml",
"product_code":"lts",
- "code":"40",
- "des":"This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions control for your LTS. With IAM, you can:Create IAM users for personnel",
+ "code":"60",
+ "des":"You can configure delimiters to split log content into words, so you can search for logs by these words. LTS has preconfigured the following delimiters:If the default del",
"doc_type":"usermanual",
- "kw":"Permissions Management,User Guide",
- "title":"Permissions Management",
+ "kw":"Configuring Log Content Delimiters,Configuration Center,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Configuring Log Content Delimiters",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_05_0003.html",
+ "node_id":"lts_05_0003.xml",
+ "product_code":"",
+ "code":"61",
+ "des":"On the ICAgent Collection tab page, you can disable or enable ICAgent collection (that is, specify whether ICAgent collects log data), syslog log collection to AOM, and c",
+ "doc_type":"",
+ "kw":"Setting ICAgent Collection,Configuration Center,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Setting ICAgent Collection",
"githuburl":""
},
{
"uri":"lts_04_0058.html",
+ "node_id":"lts_04_0058.xml",
"product_code":"",
- "code":"41",
+ "code":"62",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"",
"kw":"FAQs",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
"title":"FAQs",
"githuburl":""
},
{
- "uri":"lts_03_0015.html",
+ "uri":"lts_faq_0010.html",
+ "node_id":"lts_faq_0010.xml",
"product_code":"lts",
- "code":"42",
- "des":"Obtain and use the AK/SK of a public account.Log in to the console, hover your cursor over your username in the upper right corner, and select My Credentials.Click the Ac",
+ "code":"63",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
- "kw":"How Do I Obtain an AK/SK Pair?,FAQs,User Guide",
- "title":"How Do I Obtain an AK/SK Pair?",
+ "kw":"Host Management",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Host Management",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0120.html",
+ "node_id":"lts_faq_0120.xml",
+ "product_code":"lts",
+ "code":"64",
+ "des":"The ICAgent installation fails and the message SERVICE STOP is displayed.The following issues may occur after the installation fails:No ICAgent task exists in the task ma",
+ "doc_type":"usermanual",
+ "kw":"What Do I Do If ICAgent Installation Fails in Windows and the Message \"SERVICE STOP\" Is Displayed?,H",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"What Do I Do If ICAgent Installation Fails in Windows and the Message \"SERVICE STOP\" Is Displayed?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0121.html",
+ "node_id":"lts_faq_0121.xml",
+ "product_code":"lts",
+ "code":"65",
+ "des":"ICAgent is installed in overwrite mode. If an upgrade fails, directly run the installation command again and re-upgrade ICAgent.",
+ "doc_type":"usermanual",
+ "kw":"What Do I Do If ICAgent Upgrade Fails on the LTS Console?,Host Management,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"What Do I Do If ICAgent Upgrade Fails on the LTS Console?",
+ "githuburl":""
+ },
+ {
+ "uri":"en-us_topic_0000001727118868.html",
+ "node_id":"en-us_topic_0000001727118868.xml",
+ "product_code":"",
+ "code":"66",
+ "des":"In this case, perform the following steps:Log in to the host where ICAgent is installed.Run the netstat -nap | grep icagent command to check whether the network connectio",
+ "doc_type":"",
+ "kw":"What Do I Do If ICAgent Is Displayed as Offline on the LTS Console After Installation?,Host Manageme",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"What Do I Do If ICAgent Is Displayed as Offline on the LTS Console After Installation?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0072.html",
+ "node_id":"lts_faq_0072.xml",
+ "product_code":"",
+ "code":"67",
+ "des":"If a host with ICAgent installed is not displayed on the Hosts tab page on the LTS console, perform the following steps:If you are configuring ECS log ingestion and do no",
+ "doc_type":"",
+ "kw":"What Do I Do If I Do Not See a Host with ICAgent Installed on the LTS Console?,Host Management,User ",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"What Do I Do If I Do Not See a Host with ICAgent Installed on the LTS Console?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0020.html",
+ "node_id":"lts_faq_0020.xml",
+ "product_code":"lts",
+ "code":"68",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Log Ingestion",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Log Ingestion",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0008.html",
+ "node_id":"lts_faq_0008.xml",
+ "product_code":"lts",
+ "code":"69",
+ "des":"If the CPU usage is high when ICAgent is collecting logs (causing issues like slow running or program breakdown), check whether there are a large number of logs in the lo",
+ "doc_type":"usermanual",
+ "kw":"What Do I Do If the CPU Usage Is High When ICAgent Is Collecting Logs?,Log Ingestion,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"What Do I Do If the CPU Usage Is High When ICAgent Is Collecting Logs?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0003.html",
+ "node_id":"lts_faq_0003.xml",
+ "product_code":"lts",
+ "code":"70",
+ "des":"Host logs. ICAgent should be installed on the target hosts for log collection.Cloud service logs. To collect logs from cloud services, such as Elastic Load Balance (ELB) ",
+ "doc_type":"usermanual",
+ "kw":"What Kinds of Logs and Files Does LTS Collect?,Log Ingestion,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"What Kinds of Logs and Files Does LTS Collect?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0022.html",
+ "node_id":"lts_faq_0022.xml",
+ "product_code":"lts",
+ "code":"71",
+ "des":"Yes.The enablement/disablement status of log collection is synchronized between LTS and AOM. Likewise, if you set the log collection to be stopped when the free quota is ",
+ "doc_type":"usermanual",
+ "kw":"Will LTS Stop Collecting Logs After the Free Quota Is Used Up If I Disable \"Continue to Collect Logs",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Will LTS Stop Collecting Logs After the Free Quota Is Used Up If I Disable \"Continue to Collect Logs When the Free Quota Is Exceeded\" in AOM?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0070.html",
+ "node_id":"lts_faq_0070.xml",
+ "product_code":"lts",
+ "code":"72",
+ "des":"As the products evolve, the default collection of CCE standard output logs to AOM is no longer recommended, but for compatibility with old user habits, the default config",
+ "doc_type":"usermanual",
+ "kw":"How Do I Disable the Function of Collecting CCE Standard Output Logs to AOM on the LTS Console?,Log ",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"How Do I Disable the Function of Collecting CCE Standard Output Logs to AOM on the LTS Console?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0030.html",
+ "node_id":"lts_faq_0030.xml",
+ "product_code":"lts",
+ "code":"73",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Log Search and Analysis",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Log Search and Analysis",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0001.html",
+ "node_id":"lts_faq_0001.xml",
+ "product_code":"lts",
+ "code":"74",
+ "des":"Generally, the real-time logs are loaded to the LTS console every 5 seconds. However, if no data is generated in a 5-second interval, no new data will be displayed. Log d",
+ "doc_type":"usermanual",
+ "kw":"How Often Is the Data Loaded in the Real-Time Log View in LTS?,Log Search and Analysis,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"How Often Is the Data Loaded in the Real-Time Log View in LTS?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0031.html",
+ "node_id":"lts_faq_0031.xml",
+ "product_code":"lts",
+ "code":"75",
+ "des":"Logs reported to LTS are not displayed on the LTS console.ICAgent has not been installed.The collection path is incorrectly configured.ICAgent Collection in Configuration",
+ "doc_type":"usermanual",
+ "kw":"What Do I Do If I Cannot View Reported Logs in LTS?,Log Search and Analysis,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"What Do I Do If I Cannot View Reported Logs in LTS?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0032.html",
+ "node_id":"lts_faq_0032.xml",
+ "product_code":"lts",
+ "code":"76",
+ "des":"No. Manual deletion is not supported. LTS automatically deletes logs when the retention duration ends.",
+ "doc_type":"usermanual",
+ "kw":"Can I Manually Delete Logs on the LTS Console?,Log Search and Analysis,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Can I Manually Delete Logs on the LTS Console?",
+ "githuburl":""
+ },
+ {
+ "uri":"en-us_topic_0000001795709689.html",
+ "node_id":"en-us_topic_0000001795709689.xml",
+ "product_code":"",
+ "code":"77",
+ "des":"When you search for logs on the LTS console, if a message is displayed indicating that the query result is inaccurate, too many log results are matched, or field XXX with",
+ "doc_type":"",
+ "kw":"What Do I Do If I Could Not Search for Logs on LTS?,Log Search and Analysis,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"What Do I Do If I Could Not Search for Logs on LTS?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0040.html",
+ "node_id":"lts_faq_0040.xml",
+ "product_code":"lts",
+ "code":"78",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Log Transfer",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Log Transfer",
"githuburl":""
},
{
"uri":"lts_faq_0044.html",
+ "node_id":"lts_faq_0044.xml",
"product_code":"lts",
- "code":"43",
- "des":"No. During log transfer, logs are \"replicated\" to OBS buckets. To view transferred log files, click the name of the corresponding OBS bucket on the Log Transfer page of t",
+ "code":"79",
+ "des":"The log transfer function only forwards existing logs and does not delete them. LTS deletes retained logs once the retention period is over, but the logs that have been t",
"doc_type":"usermanual",
- "kw":"Does LTS Delete Logs That Have Been Transferred to OBS Buckets?,FAQs,User Guide",
+ "kw":"Does LTS Delete Logs That Have Been Transferred to OBS Buckets?,Log Transfer,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Does LTS Delete Logs That Have Been Transferred to OBS Buckets?",
"githuburl":""
},
{
"uri":"lts_faq_0314.html",
+ "node_id":"lts_faq_0314.xml",
"product_code":"lts",
- "code":"44",
- "des":"The OBS bucket used for log transfer has been deleted. Specify another bucket.Access control on the OBS bucket is incorrectly configured. Go to the OBS console to correct",
+ "code":"80",
+ "des":"If a log transfer task is in the abnormal state on the Log Transfer page of the LTS console:Possible cause: The OBS bucket policy is incorrect.Solution: Go to the OBS con",
"doc_type":"usermanual",
- "kw":"What Are the Common Causes of Abnormal Log Transfer?,FAQs,User Guide",
- "title":"What Are the Common Causes of Abnormal Log Transfer?",
+ "kw":"What Are the Common Causes of LTS Log Transfer Abnormalities?,Log Transfer,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"What Are the Common Causes of LTS Log Transfer Abnormalities?",
"githuburl":""
},
{
"uri":"lts_faq_0610.html",
+ "node_id":"lts_faq_0610.xml",
"product_code":"lts",
- "code":"45",
+ "code":"81",
"des":"When Cloud Trace Service (CTS) is connected to LTS, a log group and log stream are automatically created for CTS on the LTS console. To transfer CTS logs to OBS, do as fo",
"doc_type":"usermanual",
- "kw":"How Do I Transfer CTS Logs to an OBS Bucket?,FAQs,User Guide",
+ "kw":"How Do I Transfer CTS Logs to an OBS Bucket?,Log Transfer,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"How Do I Transfer CTS Logs to an OBS Bucket?",
"githuburl":""
},
{
- "uri":"lts_faq_0031.html",
- "product_code":"lts",
- "code":"46",
- "des":"No log events are displayed on the Raw Logs tab in a log stream on the LTS console.ICAgent has not been installed.The collection path is incorrectly configured.The Log Co",
- "doc_type":"usermanual",
- "kw":"What Can I Do If I Cannot View Raw Logs on the LTS Console?,FAQs,User Guide",
- "title":"What Can I Do If I Cannot View Raw Logs on the LTS Console?",
+ "uri":"lts_faq_0142.html",
+ "node_id":"lts_faq_0142.xml",
+ "product_code":"",
+ "code":"82",
+ "des":"This occurs because LTS only transfers logs generated after you configure the transfer task to OBS buckets. Logs that already exist before the configuration will not be t",
+ "doc_type":"",
+ "kw":"What Do I Do If I Cannot View Historical Data in an OBS Bucket After Transferring Data from LTS to O",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"What Do I Do If I Cannot View Historical Data in an OBS Bucket After Transferring Data from LTS to OBS?",
"githuburl":""
},
{
- "uri":"lts_faq_0003.html",
+ "uri":"lts_faq_0060.html",
+ "node_id":"lts_faq_0060.xml",
"product_code":"lts",
- "code":"47",
- "des":"Host logs. ICAgent should be installed on the target hosts for log collection.Cloud service logs. To collect logs from cloud services, such as Elastic Load Balance (ELB) ",
+ "code":"83",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
- "kw":"What Kind of Logs and Files Can LTS Collect?,FAQs,User Guide",
- "title":"What Kind of Logs and Files Can LTS Collect?",
+ "kw":"Consultation",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Consultation",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_03_0015.html",
+ "node_id":"lts_03_0015.xml",
+ "product_code":"lts",
+ "code":"84",
+ "des":"An access key ID and secret access key (AK/SK) constitute an access key.AK: access key ID, which is a unique identifier used in conjunction with a secret access key to si",
+ "doc_type":"usermanual",
+ "kw":"How Do I Obtain an AK/SK Pair?,Consultation,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"How Do I Obtain an AK/SK Pair?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_faq_0071.html",
+ "node_id":"lts_faq_0071.xml",
+ "product_code":"",
+ "code":"85",
+ "des":"After configuring log ingestion on the Log Ingestion page of the LTS console, click the target log group on the Log Management page to access the details page, choose the",
+ "doc_type":"",
+ "kw":"How Long Does It Take to Generate Logs After Configuring Log Ingestion?,Consultation,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"How Long Does It Take to Generate Logs After Configuring Log Ingestion?",
"githuburl":""
},
{
"uri":"lts_01_0033.html",
+ "node_id":"lts_01_0033.xml",
"product_code":"lts",
- "code":"48",
+ "code":"86",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"Change History,User Guide",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"lts",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Change History",
"githuburl":""
}
diff --git a/docs/lts/umn/CLASS.TXT.json b/docs/lts/umn/CLASS.TXT.json
index 0f20c330..0361888e 100644
--- a/docs/lts/umn/CLASS.TXT.json
+++ b/docs/lts/umn/CLASS.TXT.json
@@ -9,16 +9,16 @@
"code":"1"
},
{
- "desc":"Log Tank Service (LTS) enables you to collect logs from hosts and cloud services for centralized management, and analyze large volumes of logs efficiently, securely, and ",
+ "desc":"Log Tank Service (LTS) is a high-performance, cost-effective log platform with diverse functions and high reliability. It offers full-stack log collection, search through",
"product_code":"lts",
- "title":"Introduction",
+ "title":"What Is LTS?",
"uri":"lts_01_0002.html",
"doc_type":"usermanual",
"p_code":"1",
"code":"2"
},
{
- "desc":"A log group is the basic unit for LTS to manage logs. You can query and transfer logs in log groups. Up to 100 log groups can be created in your account.Up to 100 streams",
+ "desc":"A log group is a collection of log streams. It is similar to a folder and is used to classify and manage log streams. You can create log streams in a log group.A log stre",
"product_code":"lts",
"title":"Basic Concepts",
"uri":"lts_01_0003.html",
@@ -27,9 +27,9 @@
"code":"3"
},
{
- "desc":"You can view real-time logs to keep track of the status of the services connected to LTS. You can also check logs in the last 7 days.You can set search criteria to filter",
+ "desc":"Before using LTS, learn its main features in Table 1.",
"product_code":"lts",
- "title":"Basic Functions",
+ "title":"Features",
"uri":"lts_01_0004.html",
"doc_type":"usermanual",
"p_code":"1",
@@ -45,16 +45,16 @@
"code":"5"
},
{
- "desc":"If you need to assign different permissions to employees in your enterprise to access your LTS resources, is a good choice for fine-grained permissions management. IAM p",
+ "desc":"If you need to grant your enterprise personnel permission to access your LTS resources, use Identity and Access Management (IAM). IAM provides identity authentication, fi",
"product_code":"lts",
- "title":"Permissions Management",
+ "title":"Permissions",
"uri":"lts-03205.html",
"doc_type":"usermanual",
"p_code":"1",
"code":"6"
},
{
- "desc":"LTS provides a platform to store and analyze log data for Virtual Private Cloud (VPC). After VPC is associated with a log group and log stream in LTS, Network Interface C",
+ "desc":"The relationships between LTS and other services are described in Table 1.",
"product_code":"lts",
"title":"Related Services",
"uri":"lts_01_0005.html",
@@ -72,23 +72,59 @@
"code":"8"
},
{
- "desc":"A Virtual Private Cloud (VPC) flow log captures information about the traffic going to and from your VPC. You can use flow logs to monitor network traffic, analyze networ",
+ "desc":"To help you quickly get started with Log Tank Service (LTS), the following sections will show you how to install ICAgent on a Linux host and ingest logs from the host to ",
"product_code":"lts",
- "title":"Configuring the VPC Flow Log Function",
- "uri":"lts_01_0009.html",
+ "title":"Overview",
+ "uri":"lts_08300.html",
"doc_type":"usermanual",
"p_code":"8",
"code":"9"
},
{
- "desc":"This section describes how to enable trace analysis on the Cloud Trace Service (CTS) console to report traces to LTS, so you can query the traces on the LTS console.Opera",
+ "desc":"You have obtained an account and its password for logging in to the console.Log in to the management console and choose Management & Deployment > Log Tank Service.On the ",
"product_code":"lts",
- "title":"Configuring CTS to Upload Traces to LTS",
- "uri":"lts_01_0010.html",
+ "title":"Creating Log Groups and Log Streams",
+ "uri":"lts_08301.html",
"doc_type":"usermanual",
"p_code":"8",
"code":"10"
},
+ {
+ "desc":"ICAgent is the log collection tool of LTS. Install ICAgent on a host from which you want to collect logs.If ICAgent has been installed on the host when you use other clou",
+ "product_code":"lts",
+ "title":"Installing ICAgent",
+ "uri":"lts_0829.html",
+ "doc_type":"usermanual",
+ "p_code":"8",
+ "code":"11"
+ },
+ {
+ "desc":"The following shows how you can ingest host logs to LTS.When ICAgent is installed, configure the paths of host logs that you want to collect in log streams. ICAgent will ",
+ "product_code":"lts",
+ "title":"Ingesting Logs",
+ "uri":"lts_08302.html",
+ "doc_type":"usermanual",
+ "p_code":"8",
+ "code":"12"
+ },
+ {
+ "desc":"After the log ingestion is configured, you can view the reported logs on the LTS console in real time.You have created log groups and log streams.You have installed ICAge",
+ "product_code":"lts",
+ "title":"Viewing Logs in Real Time",
+ "uri":"lts_08303.html",
+ "doc_type":"usermanual",
+ "p_code":"8",
+ "code":"13"
+ },
+ {
+ "desc":"You can use Identity and Access Management (IAM) for fine-grained permissions control for your LTS. With IAM, you can:Create IAM users for personnel based on your enterpr",
+ "product_code":"lts",
+ "title":"Granting LTS Permissions to IAM Users",
+ "uri":"lts_04_0015.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "code":"14"
+ },
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"product_code":"lts",
@@ -96,43 +132,52 @@
"uri":"lts_04_1053.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"11"
+ "code":"15"
},
{
- "desc":"The LTS console provides resource statistics, your favorite log streams/favorite log streams (local cache), and recently visited log streams.This area shows the read/writ",
+ "desc":"LTS manages logs by log group and stream for easy classification. Before using LTS, create a log group and then multiple log streams in the group. By collecting and stori",
"product_code":"lts",
- "title":"LTS Console",
+ "title":"Overview",
"uri":"lts_04_1153.html",
"doc_type":"usermanual",
- "p_code":"11",
- "code":"12"
+ "p_code":"15",
+ "code":"16"
},
{
- "desc":"Log resource statistics are classified into read/write traffic, index traffic, and log volume. The statistics are for reference only. You can also visualize log resource ",
- "product_code":"lts",
- "title":"Resource Statistics",
- "uri":"lts_04_1154.html",
- "doc_type":"usermanual",
- "p_code":"11",
- "code":"13"
- },
- {
- "desc":"A log group is a group of log streams. Up to 100 log groups can be created for a single account.Log groups can be created in two ways. They are automatically created when",
+ "desc":"A log group is the basic unit for LTS to manage logs. It classifies and consists of log streams, but does not store any log data. Up to 100 log groups can be created for ",
"product_code":"lts",
"title":"Managing Log Groups",
"uri":"lts_04_0003.html",
"doc_type":"usermanual",
- "p_code":"11",
- "code":"14"
+ "p_code":"15",
+ "code":"17"
},
{
- "desc":"A log stream is the basic unit for reading and writing logs. Sorting logs into different log streams makes it easier to find specific logs when you need them.Up to 100 lo",
+ "desc":"LTS manages logs by log stream. Collected logs of different types are classified and stored in different log streams for easier log management. If there are a large numbe",
"product_code":"lts",
"title":"Managing Log Streams",
"uri":"lts_04_0004.html",
"doc_type":"usermanual",
- "p_code":"11",
- "code":"15"
+ "p_code":"15",
+ "code":"18"
+ },
+ {
+ "desc":"The log management page displays resource statistics, your favorite log streams/favorite log streams (local cache), alarm statistics, latest alarms, and recently viewed l",
+ "product_code":"lts",
+ "title":"Viewing Log Management",
+ "uri":"lts_04_1154.html",
+ "doc_type":"usermanual",
+ "p_code":"15",
+ "code":"19"
+ },
+ {
+ "desc":"You can tag log groups, log streams, host groups, and log ingestion configurations.Users can add, delete, modify, and query tags on the log group page.Log in to the manag",
+ "product_code":"lts",
+ "title":"Managing Tags",
+ "uri":"lts_04_1217.html",
+ "doc_type":"usermanual",
+ "p_code":"15",
+ "code":"20"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -141,34 +186,52 @@
"uri":"lts_02_0030.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"16"
+ "code":"21"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"product_code":"lts",
- "title":"Collecting Logs from Cloud Services",
+ "title":"Ingesting Cloud Service Logs to LTS",
"uri":"lts_04_0105.html",
"doc_type":"usermanual",
- "p_code":"16",
- "code":"17"
+ "p_code":"21",
+ "code":"22"
},
{
- "desc":"LTS can collect logs from Cloud Container Engine (CCE).ICAgent has been installed and added to the host group.You have disabled Output to AOM.CCE cluster nodes whose cont",
+ "desc":"CCE provides highly scalable, high-performance, enterprise-class Kubernetes clusters. With CCE, you can easily deploy, manage, and scale containerized applications.After ",
"product_code":"lts",
- "title":"Collecting Logs from CCE",
+ "title":"Ingesting CCE Application Logs to LTS",
"uri":"lts_04_0511.html",
"doc_type":"usermanual",
- "p_code":"17",
- "code":"18"
+ "p_code":"22",
+ "code":"23"
},
{
- "desc":"ICAgent collects logs from hosts based on your specified collection rules, and packages and sends the collected log data to LTS on a log stream basis. You can view logs o",
+ "desc":"Elastic Cloud Server (ECS) provides scalable, on-demand cloud servers to build secure, flexible, and efficient environment for your applications.After you configure ECS l",
"product_code":"lts",
- "title":"Collecting Logs from ECS",
+ "title":"Ingesting ECS Text Logs to LTS",
"uri":"lts_04_1031.html",
"doc_type":"usermanual",
- "p_code":"17",
- "code":"19"
+ "p_code":"22",
+ "code":"24"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"lts",
+ "title":"Other Ingestion Modes",
+ "uri":"lts_04_1121.html",
+ "doc_type":"usermanual",
+ "p_code":"21",
+ "code":"25"
+ },
+ {
+ "desc":"If you choose Cross-Account Ingestion - Log Stream Mapping as the log ingestion type, you can create an agency to map the log stream of the delegator account to that of t",
+ "product_code":"lts",
+ "title":"Ingesting Logs to LTS Across IAM Accounts",
+ "uri":"lts_04_1112.html",
+ "doc_type":"usermanual",
+ "p_code":"25",
+ "code":"26"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -177,16 +240,16 @@
"uri":"lts_02_1032.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"20"
+ "code":"27"
},
{
- "desc":"Host groups allow you to configure host log ingestion efficiently. You can sort multiple hosts to a host group and associate the host group with log ingestion configurati",
+ "desc":"Host groups allow you to configure host log ingestion efficiently. You can add multiple hosts to a host group and associate the host group with log ingestion configuratio",
"product_code":"lts",
"title":"Managing Host Groups",
"uri":"lts_02_1033.html",
"doc_type":"usermanual",
- "p_code":"20",
- "code":"21"
+ "p_code":"27",
+ "code":"28"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -194,107 +257,233 @@
"title":"Managing Hosts",
"uri":"lts_04_0012.html",
"doc_type":"usermanual",
- "p_code":"20",
- "code":"22"
- },
- {
- "desc":"ICAgent is a log collection tool for LTS. To use LTS to collect logs from hosts, you need to install ICAgent on the hosts.Ensure that the time and time zone of your local",
- "product_code":"lts",
- "title":"Installing ICAgent",
- "uri":"lts_02_0013.html",
- "doc_type":"usermanual",
- "p_code":"22",
- "code":"23"
- },
- {
- "desc":"To deliver a better collection experience, LTS regularly upgrades ICAgent. When LTS prompts you that a new ICAgent version is available, you can follow the directions her",
- "product_code":"lts",
- "title":"Upgrading ICAgent",
- "uri":"lts_02_0014.html",
- "doc_type":"usermanual",
- "p_code":"22",
- "code":"24"
- },
- {
- "desc":"If ICAgent is uninstalled from a host, log collection will be affected. Exercise caution when performing this operation.Only ICAgent installed on Linux hosts can be unins",
- "product_code":"lts",
- "title":"Uninstalling ICAgent",
- "uri":"lts_02_0015.html",
- "doc_type":"usermanual",
- "p_code":"22",
- "code":"25"
- },
- {
- "desc":"The following table lists the ICAgent statuses.",
- "product_code":"lts",
- "title":"ICAgent Statuses",
- "uri":"lts_04_0013.html",
- "doc_type":"usermanual",
- "p_code":"22",
- "code":"26"
- },
- {
- "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
- "product_code":"lts",
- "title":"Log Search and View",
- "uri":"lts_05_0004.html",
- "doc_type":"usermanual",
- "p_code":"",
- "code":"27"
- },
- {
- "desc":"Follow the directions below to search logs by keyword and time range:On the LTS console, choose Log Management in the navigation pane on the left.In the log group list, c",
- "product_code":"lts",
- "title":"Log Search",
- "uri":"lts_05_0005.html",
- "doc_type":"usermanual",
- "p_code":"27",
- "code":"28"
- },
- {
- "desc":"You can view reported logs on the LTS console in real time.You have created log groups and log streams.You have installed ICAgent.You have configured log collection rules",
- "product_code":"lts",
- "title":"Viewing Real-Time Logs",
- "uri":"lts_05_0006.html",
- "doc_type":"usermanual",
"p_code":"27",
"code":"29"
},
{
- "desc":"To search for logs using a keyword repeatedly, perform the following operations to configure quick search.On the LTS console, choose Log Management in the navigation pane",
+ "desc":"To use LTS to collect logs (such as host metrics, container metrics, node logs, container logs, and standard output logs) from intra-region hosts, you need to install ICA",
"product_code":"lts",
- "title":"Quick Search",
- "uri":"lts_05_0009.html",
+ "title":"Installing ICAgent (Intra-Region Hosts)",
+ "uri":"lts_02_0013.html",
"doc_type":"usermanual",
- "p_code":"27",
+ "p_code":"29",
"code":"30"
},
{
- "desc":"Monitoring keywords in logs helps you keep track of system performance and services. For example, the number of ERROR keywords indicates the system health, and the number",
+ "desc":"ICAgent is a log collection tool for LTS. To use LTS to collect logs from extra-region hosts, you need to install ICAgent on the hosts.Before installing ICAgent, ensure t",
"product_code":"lts",
- "title":"Quick Analysis",
- "uri":"lts_05_0007.html",
+ "title":"Installing ICAgent (Extra-Region Hosts)",
+ "uri":"lts_02_0828.html",
"doc_type":"usermanual",
- "p_code":"27",
+ "p_code":"29",
"code":"31"
},
+ {
+ "desc":"After ICAgent is installed, you can upgrade and uninstall it, and view its status.To deliver a better collection experience, LTS regularly upgrades ICAgent. When LTS prom",
+ "product_code":"lts",
+ "title":"Managing ICAgent",
+ "uri":"lts_02_0014.html",
+ "doc_type":"usermanual",
+ "p_code":"29",
+ "code":"32"
+ },
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"product_code":"lts",
- "title":"Log Analysis",
- "uri":"lts_04_0002.html",
+ "title":"Log Search and Analysis",
+ "uri":"lts_05_0004.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"32"
+ "code":"33"
+ },
+ {
+ "desc":"Log search and analysis are indispensable to O&M. After configuring log ingestion, you can search and analyze the collected log data on LTS. Its efficient and professiona",
+ "product_code":"lts",
+ "title":"Overview",
+ "uri":"lts_05_0100.html",
+ "doc_type":"usermanual",
+ "p_code":"33",
+ "code":"34"
+ },
+ {
+ "desc":"An index is a storage structure used to query and analyze logs. Different index settings will generate different query and analysis results. Configure the index settings ",
+ "product_code":"lts",
+ "title":"Setting Indexes",
+ "uri":"lts_05_0008.html",
+ "doc_type":"usermanual",
+ "p_code":"33",
+ "code":"35"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"lts",
+ "title":"Setting Cloud Structuring Parsing",
+ "uri":"lts_0821.html",
+ "doc_type":"usermanual",
+ "p_code":"33",
+ "code":"36"
},
{
"desc":"Log data can be structured or unstructured. Structured data is quantitative data or can be defined by unified data models. It has a fixed length and format. Unstructured ",
"product_code":"lts",
- "title":"Log Structuring",
- "uri":"lts_0821.html",
+ "title":"Overview",
+ "uri":"lts_0822.html",
"doc_type":"usermanual",
- "p_code":"32",
- "code":"33"
+ "p_code":"36",
+ "code":"37"
+ },
+ {
+ "desc":"LTS provides five log structuring modes: regular expressions, JSON, delimiters, Nginx, and structuring templates. You can make your choice flexibly.Regular Expressions: T",
+ "product_code":"lts",
+ "title":"Setting Cloud Structuring Parsing",
+ "uri":"lts_0823.html",
+ "doc_type":"usermanual",
+ "p_code":"36",
+ "code":"38"
+ },
+ {
+ "desc":"LTS supports two types of structuring templates: system and custom templates.You can choose from multiple system templates, but cannot modify the field types in them or d",
+ "product_code":"lts",
+ "title":"Setting a Structuring Template",
+ "uri":"lts_0824.html",
+ "doc_type":"usermanual",
+ "p_code":"36",
+ "code":"39"
+ },
+ {
+ "desc":"You can set extracted fields after cloud structuring. For details, see Table 1.When you use regular expressions (manually entered), JSON, delimiters, Nginx, or custom tem",
+ "product_code":"lts",
+ "title":"Setting Structured and Tag Fields",
+ "uri":"lts_0825.html",
+ "doc_type":"usermanual",
+ "p_code":"36",
+ "code":"40"
+ },
+ {
+ "desc":"When configuring log ingestion, you can enable User-defined log time to set a time field in the logs as the ingestion configuration time.A time deviation may occur around",
+ "product_code":"lts",
+ "title":"Setting User-defined Log Time",
+ "uri":"lts_0826.html",
+ "doc_type":"usermanual",
+ "p_code":"36",
+ "code":"41"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"lts",
+ "title":"Searching Logs",
+ "uri":"lts_05_0110.html",
+ "doc_type":"usermanual",
+ "p_code":"33",
+ "code":"42"
+ },
+ {
+ "desc":"After configuring log structuring parsing and indexing, you can enter statements to search for log records that contain specific keywords. You can also search for log dat",
+ "product_code":"lts",
+ "title":"Accessing the Log Search Page",
+ "uri":"lts_05_0005.html",
+ "doc_type":"usermanual",
+ "p_code":"42",
+ "code":"43"
+ },
+ {
+ "desc":"LTS provides a range of search syntax to set search criteria and filtering rules for filtering records that meet the search criteria. Then, you can apply analysis stateme",
+ "product_code":"lts",
+ "title":"Using LTS Search Syntax",
+ "uri":"lts_05_0111.html",
+ "doc_type":"usermanual",
+ "p_code":"42",
+ "code":"44"
+ },
+ {
+ "desc":"If you need to repeatedly use a keyword to search for logs, you can set and save the keyword as a quick query statement for faster log querying and analysis.A quick searc",
+ "product_code":"lts",
+ "title":"Saving Conditions for Quick Search",
+ "uri":"lts_05_0009.html",
+ "doc_type":"usermanual",
+ "p_code":"42",
+ "code":"45"
+ },
+ {
+ "desc":"Logs contain information such as system performance and business status. For example, the frequency of keyword ERROR indicates the system health, and the frequency of key",
+ "product_code":"lts",
+ "title":"Creating an LTS Quick Analysis Task",
+ "uri":"lts_05_0007.html",
+ "doc_type":"usermanual",
+ "p_code":"42",
+ "code":"46"
+ },
+ {
+ "desc":"Logs are reported to LTS about every minute, allowing you to view them on the Real-Time Logs page within 1 minute after configuring log ingestion. This enables rapid sear",
+ "product_code":"lts",
+ "title":"Viewing Real-Time Logs",
+ "uri":"lts_05_0006.html",
+ "doc_type":"usermanual",
+ "p_code":"33",
+ "code":"47"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"lts",
+ "title":"Log Alarms",
+ "uri":"lts_04_0057.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "code":"48"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"lts",
+ "title":"Alarm Rules",
+ "uri":"lts_04_1122.html",
+ "doc_type":"usermanual",
+ "p_code":"48",
+ "code":"49"
+ },
+ {
+ "desc":"You can set alarm rules based on keywords in log streams to monitor service status in real time. Currently, up to 200 keyword alarms can be created for each account.A log",
+ "product_code":"lts",
+ "title":"Configuring Log Alarm Rules",
+ "uri":"lts_04_0062.html",
+ "doc_type":"usermanual",
+ "p_code":"49",
+ "code":"50"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"lts",
+ "title":"Configuring Log Alarm Notifications",
+ "uri":"lts_04_1123.html",
+ "doc_type":"usermanual",
+ "p_code":"48",
+ "code":"51"
+ },
+ {
+ "desc":"A message template defines the format of alarm notification messages sent to subscribers. LTS provides built-in keywords_template and sql_template. Subscribers can select",
+ "product_code":"lts",
+ "title":"Creating a Message Template on the LTS Console",
+ "uri":"lts_06_0011.html",
+ "doc_type":"usermanual",
+ "p_code":"51",
+ "code":"52"
+ },
+ {
+ "desc":"LTS allows you to customize alarm action rules. You can create an alarm action rule to associate an SMN topic with a message template. You can also customize notification",
+ "product_code":"lts",
+ "title":"Creating an Alarm Action Rule",
+ "uri":"lts_02_0926.html",
+ "doc_type":"usermanual",
+ "p_code":"51",
+ "code":"53"
+ },
+ {
+ "desc":"LTS allows you to configure keyword alarm rules to periodically query log data. When an alarm rule is met, an alarm will be reported. You can view the alarms on the LTS c",
+ "product_code":"lts",
+ "title":"Viewing Alarms in LTS",
+ "uri":"lts_04_0060.html",
+ "doc_type":"usermanual",
+ "p_code":"48",
+ "code":"54"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -303,34 +492,25 @@
"uri":"lts_04_0040.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"34"
+ "code":"55"
},
{
- "desc":"Logs reported from hosts and cloud services are retained in LTS for seven days by default. You can set the retention period to be 1 to 30 days. Retained logs are deleted ",
+ "desc":"Logs reported from hosts and cloud services are retained in LTS. You can set the retention period. Retained logs are deleted once the retention period is over. For long-t",
"product_code":"lts",
"title":"Overview",
"uri":"lts_04_0011.html",
"doc_type":"usermanual",
- "p_code":"34",
- "code":"35"
+ "p_code":"55",
+ "code":"56"
},
{
- "desc":"You can transfer logs to OBS and download log files from the OBS console.To transfer logs, you must have the OBS Administrator permissions apart from the LTS permissions.",
+ "desc":"You can transfer logs to OBS and download log files from the OBS console. You can choose scheduled or one-time transfers.To use this function, you must have the OBS Admin",
"product_code":"lts",
"title":"Transferring Logs to OBS",
"uri":"lts_04_0041.html",
"doc_type":"usermanual",
- "p_code":"34",
- "code":"36"
- },
- {
- "desc":"You can use DMS APIs to retrieve logs in real time.Logs have been ingested to LTS.Before registering a DMS Kafka instance, configure an inbound rule to allow access from ",
- "product_code":"lts",
- "title":"Transferring Logs to DMS",
- "uri":"lts_04_0043.html",
- "doc_type":"usermanual",
- "p_code":"34",
- "code":"37"
+ "p_code":"55",
+ "code":"57"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -339,25 +519,34 @@
"uri":"lts_06_0003.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"38"
+ "code":"58"
},
{
- "desc":"To reduce the memory, database, and disk space usage, you can set log collection as required. The log collection switch is used to determine whether to collect log data.T",
+ "desc":"When the monthly free quota (500 MB) is used up, you will be billed for any excess usage on a pay-per-use basis. To avoid extra expenses, you can configure log collection",
"product_code":"lts",
- "title":"Log Collection",
+ "title":"Setting LTS Log Collection Quota",
+ "uri":"lts_0904.html",
+ "doc_type":"usermanual",
+ "p_code":"58",
+ "code":"59"
+ },
+ {
+ "desc":"You can configure delimiters to split log content into words, so you can search for logs by these words. LTS has preconfigured the following delimiters:If the default del",
+ "product_code":"lts",
+ "title":"Configuring Log Content Delimiters",
+ "uri":"lts_04_0052.html",
+ "doc_type":"usermanual",
+ "p_code":"58",
+ "code":"60"
+ },
+ {
+ "desc":"On the ICAgent Collection tab page, you can disable or enable ICAgent collection (that is, specify whether ICAgent collects log data), syslog log collection to AOM, and c",
+ "product_code":"lts",
+ "title":"Setting ICAgent Collection",
"uri":"lts_05_0003.html",
"doc_type":"usermanual",
- "p_code":"38",
- "code":"39"
- },
- {
- "desc":"This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions control for your LTS. With IAM, you can:Create IAM users for personnel",
- "product_code":"lts",
- "title":"Permissions Management",
- "uri":"lts_04_0015.html",
- "doc_type":"usermanual",
- "p_code":"",
- "code":"40"
+ "p_code":"58",
+ "code":"61"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -366,34 +555,169 @@
"uri":"lts_04_0058.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"41"
+ "code":"62"
},
{
- "desc":"Obtain and use the AK/SK of a public account.Log in to the console, hover your cursor over your username in the upper right corner, and select My Credentials.Click the Ac",
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"product_code":"lts",
- "title":"How Do I Obtain an AK/SK Pair?",
- "uri":"lts_03_0015.html",
+ "title":"Host Management",
+ "uri":"lts_faq_0010.html",
"doc_type":"usermanual",
- "p_code":"41",
- "code":"42"
+ "p_code":"62",
+ "code":"63"
},
{
- "desc":"No. During log transfer, logs are \"replicated\" to OBS buckets. To view transferred log files, click the name of the corresponding OBS bucket on the Log Transfer page of t",
+ "desc":"The ICAgent installation fails and the message SERVICE STOP is displayed.The following issues may occur after the installation fails:No ICAgent task exists in the task ma",
+ "product_code":"lts",
+ "title":"What Do I Do If ICAgent Installation Fails in Windows and the Message \"SERVICE STOP\" Is Displayed?",
+ "uri":"lts_faq_0120.html",
+ "doc_type":"usermanual",
+ "p_code":"63",
+ "code":"64"
+ },
+ {
+ "desc":"ICAgent is installed in overwrite mode. If an upgrade fails, directly run the installation command again and re-upgrade ICAgent.",
+ "product_code":"lts",
+ "title":"What Do I Do If ICAgent Upgrade Fails on the LTS Console?",
+ "uri":"lts_faq_0121.html",
+ "doc_type":"usermanual",
+ "p_code":"63",
+ "code":"65"
+ },
+ {
+ "desc":"In this case, perform the following steps:Log in to the host where ICAgent is installed.Run the netstat -nap | grep icagent command to check whether the network connectio",
+ "product_code":"lts",
+ "title":"What Do I Do If ICAgent Is Displayed as Offline on the LTS Console After Installation?",
+ "uri":"en-us_topic_0000001727118868.html",
+ "doc_type":"usermanual",
+ "p_code":"63",
+ "code":"66"
+ },
+ {
+ "desc":"If a host with ICAgent installed is not displayed on the Hosts tab page on the LTS console, perform the following steps:If you are configuring ECS log ingestion and do no",
+ "product_code":"lts",
+ "title":"What Do I Do If I Do Not See a Host with ICAgent Installed on the LTS Console?",
+ "uri":"lts_faq_0072.html",
+ "doc_type":"usermanual",
+ "p_code":"63",
+ "code":"67"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"lts",
+ "title":"Log Ingestion",
+ "uri":"lts_faq_0020.html",
+ "doc_type":"usermanual",
+ "p_code":"62",
+ "code":"68"
+ },
+ {
+ "desc":"If the CPU usage is high when ICAgent is collecting logs (causing issues like slow running or program breakdown), check whether there are a large number of logs in the lo",
+ "product_code":"lts",
+ "title":"What Do I Do If the CPU Usage Is High When ICAgent Is Collecting Logs?",
+ "uri":"lts_faq_0008.html",
+ "doc_type":"usermanual",
+ "p_code":"68",
+ "code":"69"
+ },
+ {
+ "desc":"Host logs. ICAgent should be installed on the target hosts for log collection.Cloud service logs. To collect logs from cloud services, such as Elastic Load Balance (ELB) ",
+ "product_code":"lts",
+ "title":"What Kinds of Logs and Files Does LTS Collect?",
+ "uri":"lts_faq_0003.html",
+ "doc_type":"usermanual",
+ "p_code":"68",
+ "code":"70"
+ },
+ {
+ "desc":"Yes.The enablement/disablement status of log collection is synchronized between LTS and AOM. Likewise, if you set the log collection to be stopped when the free quota is ",
+ "product_code":"lts",
+ "title":"Will LTS Stop Collecting Logs After the Free Quota Is Used Up If I Disable \"Continue to Collect Logs When the Free Quota Is Exceeded\" in AOM?",
+ "uri":"lts_faq_0022.html",
+ "doc_type":"usermanual",
+ "p_code":"68",
+ "code":"71"
+ },
+ {
+ "desc":"As the products evolve, the default collection of CCE standard output logs to AOM is no longer recommended, but for compatibility with old user habits, the default config",
+ "product_code":"lts",
+ "title":"How Do I Disable the Function of Collecting CCE Standard Output Logs to AOM on the LTS Console?",
+ "uri":"lts_faq_0070.html",
+ "doc_type":"usermanual",
+ "p_code":"68",
+ "code":"72"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"lts",
+ "title":"Log Search and Analysis",
+ "uri":"lts_faq_0030.html",
+ "doc_type":"usermanual",
+ "p_code":"62",
+ "code":"73"
+ },
+ {
+ "desc":"Generally, the real-time logs are loaded to the LTS console every 5 seconds. However, if no data is generated in a 5-second interval, no new data will be displayed. Log d",
+ "product_code":"lts",
+ "title":"How Often Is the Data Loaded in the Real-Time Log View in LTS?",
+ "uri":"lts_faq_0001.html",
+ "doc_type":"usermanual",
+ "p_code":"73",
+ "code":"74"
+ },
+ {
+ "desc":"Logs reported to LTS are not displayed on the LTS console.ICAgent has not been installed.The collection path is incorrectly configured.ICAgent Collection in Configuration",
+ "product_code":"lts",
+ "title":"What Do I Do If I Cannot View Reported Logs in LTS?",
+ "uri":"lts_faq_0031.html",
+ "doc_type":"usermanual",
+ "p_code":"73",
+ "code":"75"
+ },
+ {
+ "desc":"No. Manual deletion is not supported. LTS automatically deletes logs when the retention duration ends.",
+ "product_code":"lts",
+ "title":"Can I Manually Delete Logs on the LTS Console?",
+ "uri":"lts_faq_0032.html",
+ "doc_type":"usermanual",
+ "p_code":"73",
+ "code":"76"
+ },
+ {
+ "desc":"When you search for logs on the LTS console, if a message is displayed indicating that the query result is inaccurate, too many log results are matched, or field XXX with",
+ "product_code":"lts",
+ "title":"What Do I Do If I Could Not Search for Logs on LTS?",
+ "uri":"en-us_topic_0000001795709689.html",
+ "doc_type":"usermanual",
+ "p_code":"73",
+ "code":"77"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"lts",
+ "title":"Log Transfer",
+ "uri":"lts_faq_0040.html",
+ "doc_type":"usermanual",
+ "p_code":"62",
+ "code":"78"
+ },
+ {
+ "desc":"The log transfer function only forwards existing logs and does not delete them. LTS deletes retained logs once the retention period is over, but the logs that have been t",
"product_code":"lts",
"title":"Does LTS Delete Logs That Have Been Transferred to OBS Buckets?",
"uri":"lts_faq_0044.html",
"doc_type":"usermanual",
- "p_code":"41",
- "code":"43"
+ "p_code":"78",
+ "code":"79"
},
{
- "desc":"The OBS bucket used for log transfer has been deleted. Specify another bucket.Access control on the OBS bucket is incorrectly configured. Go to the OBS console to correct",
+ "desc":"If a log transfer task is in the abnormal state on the Log Transfer page of the LTS console:Possible cause: The OBS bucket policy is incorrect.Solution: Go to the OBS con",
"product_code":"lts",
- "title":"What Are the Common Causes of Abnormal Log Transfer?",
+ "title":"What Are the Common Causes of LTS Log Transfer Abnormalities?",
"uri":"lts_faq_0314.html",
"doc_type":"usermanual",
- "p_code":"41",
- "code":"44"
+ "p_code":"78",
+ "code":"80"
},
{
"desc":"When Cloud Trace Service (CTS) is connected to LTS, a log group and log stream are automatically created for CTS on the LTS console. To transfer CTS logs to OBS, do as fo",
@@ -401,26 +725,44 @@
"title":"How Do I Transfer CTS Logs to an OBS Bucket?",
"uri":"lts_faq_0610.html",
"doc_type":"usermanual",
- "p_code":"41",
- "code":"45"
+ "p_code":"78",
+ "code":"81"
},
{
- "desc":"No log events are displayed on the Raw Logs tab in a log stream on the LTS console.ICAgent has not been installed.The collection path is incorrectly configured.The Log Co",
+ "desc":"This occurs because LTS only transfers logs generated after you configure the transfer task to OBS buckets. Logs that already exist before the configuration will not be t",
"product_code":"lts",
- "title":"What Can I Do If I Cannot View Raw Logs on the LTS Console?",
- "uri":"lts_faq_0031.html",
+ "title":"What Do I Do If I Cannot View Historical Data in an OBS Bucket After Transferring Data from LTS to OBS?",
+ "uri":"lts_faq_0142.html",
"doc_type":"usermanual",
- "p_code":"41",
- "code":"46"
+ "p_code":"78",
+ "code":"82"
},
{
- "desc":"Host logs. ICAgent should be installed on the target hosts for log collection.Cloud service logs. To collect logs from cloud services, such as Elastic Load Balance (ELB) ",
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"product_code":"lts",
- "title":"What Kind of Logs and Files Can LTS Collect?",
- "uri":"lts_faq_0003.html",
+ "title":"Consultation",
+ "uri":"lts_faq_0060.html",
"doc_type":"usermanual",
- "p_code":"41",
- "code":"47"
+ "p_code":"62",
+ "code":"83"
+ },
+ {
+ "desc":"An access key ID and secret access key (AK/SK) constitute an access key.AK: access key ID, which is a unique identifier used in conjunction with a secret access key to si",
+ "product_code":"lts",
+ "title":"How Do I Obtain an AK/SK Pair?",
+ "uri":"lts_03_0015.html",
+ "doc_type":"usermanual",
+ "p_code":"83",
+ "code":"84"
+ },
+ {
+ "desc":"After configuring log ingestion on the Log Ingestion page of the LTS console, click the target log group on the Log Management page to access the details page, choose the",
+ "product_code":"lts",
+ "title":"How Long Does It Take to Generate Logs After Configuring Log Ingestion?",
+ "uri":"lts_faq_0071.html",
+ "doc_type":"usermanual",
+ "p_code":"83",
+ "code":"85"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -429,6 +771,6 @@
"uri":"lts_01_0033.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"48"
+ "code":"86"
}
]
\ No newline at end of file
diff --git a/docs/lts/umn/en-us_image_0000001119722454.png b/docs/lts/umn/en-us_image_0000001119722454.png
deleted file mode 100644
index dce0ff9b..00000000
Binary files a/docs/lts/umn/en-us_image_0000001119722454.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001119722456.png b/docs/lts/umn/en-us_image_0000001119722456.png
new file mode 100644
index 00000000..71d02b43
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001119722456.png differ
diff --git a/docs/lts/umn/en-us_image_0000001119882372.png b/docs/lts/umn/en-us_image_0000001119882372.png
new file mode 100644
index 00000000..71d02b43
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001119882372.png differ
diff --git a/docs/lts/umn/en-us_image_0000001123555094.png b/docs/lts/umn/en-us_image_0000001123555094.png
deleted file mode 100644
index b4eed81e..00000000
Binary files a/docs/lts/umn/en-us_image_0000001123555094.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001123715432.png b/docs/lts/umn/en-us_image_0000001123715432.png
deleted file mode 100644
index 88bc7990..00000000
Binary files a/docs/lts/umn/en-us_image_0000001123715432.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001126336076.png b/docs/lts/umn/en-us_image_0000001126336076.png
new file mode 100644
index 00000000..e2360257
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001126336076.png differ
diff --git a/docs/lts/umn/en-us_image_0000001155057118.png b/docs/lts/umn/en-us_image_0000001155057118.png
new file mode 100644
index 00000000..f8294b4b
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001155057118.png differ
diff --git a/docs/lts/umn/en-us_image_0000001165793419.png b/docs/lts/umn/en-us_image_0000001165793419.png
deleted file mode 100644
index 88bc7990..00000000
Binary files a/docs/lts/umn/en-us_image_0000001165793419.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001166602145.png b/docs/lts/umn/en-us_image_0000001166602145.png
new file mode 100644
index 00000000..71d02b43
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001166602145.png differ
diff --git a/docs/lts/umn/en-us_image_0000001200507455.png b/docs/lts/umn/en-us_image_0000001200507455.png
new file mode 100644
index 00000000..f8294b4b
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001200507455.png differ
diff --git a/docs/lts/umn/en-us_image_0000001252099070.png b/docs/lts/umn/en-us_image_0000001252099070.png
deleted file mode 100644
index 97cad98b..00000000
Binary files a/docs/lts/umn/en-us_image_0000001252099070.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001259071431.png b/docs/lts/umn/en-us_image_0000001259071431.png
deleted file mode 100644
index 509394a5..00000000
Binary files a/docs/lts/umn/en-us_image_0000001259071431.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001259310901.png b/docs/lts/umn/en-us_image_0000001259310901.png
deleted file mode 100644
index de71ab7e..00000000
Binary files a/docs/lts/umn/en-us_image_0000001259310901.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001309911389.png b/docs/lts/umn/en-us_image_0000001309911389.png
deleted file mode 100644
index f31159ba..00000000
Binary files a/docs/lts/umn/en-us_image_0000001309911389.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001343684921.png b/docs/lts/umn/en-us_image_0000001343684921.png
new file mode 100644
index 00000000..e4387ce8
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001343684921.png differ
diff --git a/docs/lts/umn/en-us_image_0000001380340913.png b/docs/lts/umn/en-us_image_0000001380340913.png
deleted file mode 100644
index b7cb3079..00000000
Binary files a/docs/lts/umn/en-us_image_0000001380340913.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001381829696.png b/docs/lts/umn/en-us_image_0000001381829696.png
new file mode 100644
index 00000000..35c248d7
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001381829696.png differ
diff --git a/docs/lts/umn/en-us_image_0000001408943272.png b/docs/lts/umn/en-us_image_0000001408943272.png
deleted file mode 100644
index 02efcbce..00000000
Binary files a/docs/lts/umn/en-us_image_0000001408943272.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001409026272.png b/docs/lts/umn/en-us_image_0000001409026272.png
deleted file mode 100644
index 03c68b81..00000000
Binary files a/docs/lts/umn/en-us_image_0000001409026272.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001409428384.png b/docs/lts/umn/en-us_image_0000001409428384.png
deleted file mode 100644
index c569018a..00000000
Binary files a/docs/lts/umn/en-us_image_0000001409428384.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001409812490.png b/docs/lts/umn/en-us_image_0000001409812490.png
deleted file mode 100644
index fa3b559f..00000000
Binary files a/docs/lts/umn/en-us_image_0000001409812490.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001409813242.png b/docs/lts/umn/en-us_image_0000001409813242.png
deleted file mode 100644
index d86961cc..00000000
Binary files a/docs/lts/umn/en-us_image_0000001409813242.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001409870506.png b/docs/lts/umn/en-us_image_0000001409870506.png
deleted file mode 100644
index 9868734e..00000000
Binary files a/docs/lts/umn/en-us_image_0000001409870506.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001410024590.png b/docs/lts/umn/en-us_image_0000001410024590.png
deleted file mode 100644
index 85f45715..00000000
Binary files a/docs/lts/umn/en-us_image_0000001410024590.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001410029766.png b/docs/lts/umn/en-us_image_0000001410029766.png
deleted file mode 100644
index 6393cade..00000000
Binary files a/docs/lts/umn/en-us_image_0000001410029766.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001410131678.png b/docs/lts/umn/en-us_image_0000001410131678.png
deleted file mode 100644
index 5e676426..00000000
Binary files a/docs/lts/umn/en-us_image_0000001410131678.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001410422998.png b/docs/lts/umn/en-us_image_0000001410422998.png
deleted file mode 100644
index 642987f4..00000000
Binary files a/docs/lts/umn/en-us_image_0000001410422998.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001424310404.png b/docs/lts/umn/en-us_image_0000001424310404.png
deleted file mode 100644
index b0db4e32..00000000
Binary files a/docs/lts/umn/en-us_image_0000001424310404.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001424418870.png b/docs/lts/umn/en-us_image_0000001424418870.png
deleted file mode 100644
index 8a2ad03e..00000000
Binary files a/docs/lts/umn/en-us_image_0000001424418870.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001424467768.png b/docs/lts/umn/en-us_image_0000001424467768.png
deleted file mode 100644
index 5fb3b98f..00000000
Binary files a/docs/lts/umn/en-us_image_0000001424467768.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001424573742.png b/docs/lts/umn/en-us_image_0000001424573742.png
deleted file mode 100644
index c124a272..00000000
Binary files a/docs/lts/umn/en-us_image_0000001424573742.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001424625748.png b/docs/lts/umn/en-us_image_0000001424625748.png
deleted file mode 100644
index 8a2ad03e..00000000
Binary files a/docs/lts/umn/en-us_image_0000001424625748.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001424736642.png b/docs/lts/umn/en-us_image_0000001424736642.png
deleted file mode 100644
index 8b48bcbf..00000000
Binary files a/docs/lts/umn/en-us_image_0000001424736642.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001424778604.png b/docs/lts/umn/en-us_image_0000001424778604.png
deleted file mode 100644
index a2359b99..00000000
Binary files a/docs/lts/umn/en-us_image_0000001424778604.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001424794336.png b/docs/lts/umn/en-us_image_0000001424794336.png
deleted file mode 100644
index 0c0cccaf..00000000
Binary files a/docs/lts/umn/en-us_image_0000001424794336.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001427369668.png b/docs/lts/umn/en-us_image_0000001427369668.png
deleted file mode 100644
index bef994c4..00000000
Binary files a/docs/lts/umn/en-us_image_0000001427369668.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001432189445.png b/docs/lts/umn/en-us_image_0000001432189445.png
new file mode 100644
index 00000000..8e01a6b0
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001432189445.png differ
diff --git a/docs/lts/umn/en-us_image_0000001459223293.png b/docs/lts/umn/en-us_image_0000001459223293.png
deleted file mode 100644
index 1af4d8c9..00000000
Binary files a/docs/lts/umn/en-us_image_0000001459223293.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001459223925.png b/docs/lts/umn/en-us_image_0000001459223925.png
deleted file mode 100644
index 647d79eb..00000000
Binary files a/docs/lts/umn/en-us_image_0000001459223925.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001459387853.png b/docs/lts/umn/en-us_image_0000001459387853.png
deleted file mode 100644
index 33204f60..00000000
Binary files a/docs/lts/umn/en-us_image_0000001459387853.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001459614217.png b/docs/lts/umn/en-us_image_0000001459614217.png
deleted file mode 100644
index 81ea8619..00000000
Binary files a/docs/lts/umn/en-us_image_0000001459614217.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001459633297.png b/docs/lts/umn/en-us_image_0000001459633297.png
deleted file mode 100644
index 9f76b8ee..00000000
Binary files a/docs/lts/umn/en-us_image_0000001459633297.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001459871273.png b/docs/lts/umn/en-us_image_0000001459871273.png
deleted file mode 100644
index 58f396c3..00000000
Binary files a/docs/lts/umn/en-us_image_0000001459871273.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001459892873.png b/docs/lts/umn/en-us_image_0000001459892873.png
deleted file mode 100644
index fd4ce154..00000000
Binary files a/docs/lts/umn/en-us_image_0000001459892873.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001459933005.png b/docs/lts/umn/en-us_image_0000001459933005.png
deleted file mode 100644
index 04334fee..00000000
Binary files a/docs/lts/umn/en-us_image_0000001459933005.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001460010097.png b/docs/lts/umn/en-us_image_0000001460010097.png
deleted file mode 100644
index 2b15d3fa..00000000
Binary files a/docs/lts/umn/en-us_image_0000001460010097.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001460235561.png b/docs/lts/umn/en-us_image_0000001460235561.png
deleted file mode 100644
index 18116816..00000000
Binary files a/docs/lts/umn/en-us_image_0000001460235561.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001460330173.png b/docs/lts/umn/en-us_image_0000001460330173.png
deleted file mode 100644
index 41413064..00000000
Binary files a/docs/lts/umn/en-us_image_0000001460330173.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001460332517.png b/docs/lts/umn/en-us_image_0000001460332517.png
deleted file mode 100644
index d522b4d4..00000000
Binary files a/docs/lts/umn/en-us_image_0000001460332517.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001460346829.png b/docs/lts/umn/en-us_image_0000001460346829.png
deleted file mode 100644
index af78b5c9..00000000
Binary files a/docs/lts/umn/en-us_image_0000001460346829.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001460349521.png b/docs/lts/umn/en-us_image_0000001460349521.png
deleted file mode 100644
index 8665bf2e..00000000
Binary files a/docs/lts/umn/en-us_image_0000001460349521.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001460358861.png b/docs/lts/umn/en-us_image_0000001460358861.png
deleted file mode 100644
index 64cb8dc0..00000000
Binary files a/docs/lts/umn/en-us_image_0000001460358861.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001460416749.png b/docs/lts/umn/en-us_image_0000001460416749.png
deleted file mode 100644
index 459a0046..00000000
Binary files a/docs/lts/umn/en-us_image_0000001460416749.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001460454221.png b/docs/lts/umn/en-us_image_0000001460454221.png
deleted file mode 100644
index 9bd9a998..00000000
Binary files a/docs/lts/umn/en-us_image_0000001460454221.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001460456897.png b/docs/lts/umn/en-us_image_0000001460456897.png
deleted file mode 100644
index b0eed24b..00000000
Binary files a/docs/lts/umn/en-us_image_0000001460456897.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001463823649.png b/docs/lts/umn/en-us_image_0000001463823649.png
deleted file mode 100644
index dd00276e..00000000
Binary files a/docs/lts/umn/en-us_image_0000001463823649.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001463903813.png b/docs/lts/umn/en-us_image_0000001463903813.png
deleted file mode 100644
index dd00276e..00000000
Binary files a/docs/lts/umn/en-us_image_0000001463903813.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001474096881.png b/docs/lts/umn/en-us_image_0000001474096881.png
deleted file mode 100644
index d91746c8..00000000
Binary files a/docs/lts/umn/en-us_image_0000001474096881.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001474342201.png b/docs/lts/umn/en-us_image_0000001474342201.png
deleted file mode 100644
index 2af5afe7..00000000
Binary files a/docs/lts/umn/en-us_image_0000001474342201.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001474668261.png b/docs/lts/umn/en-us_image_0000001474668261.png
deleted file mode 100644
index 71160afb..00000000
Binary files a/docs/lts/umn/en-us_image_0000001474668261.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001477332293.png b/docs/lts/umn/en-us_image_0000001477332293.png
deleted file mode 100644
index 8a2dd43e..00000000
Binary files a/docs/lts/umn/en-us_image_0000001477332293.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001500031545.png b/docs/lts/umn/en-us_image_0000001500031545.png
deleted file mode 100644
index f26f3424..00000000
Binary files a/docs/lts/umn/en-us_image_0000001500031545.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001536874781.png b/docs/lts/umn/en-us_image_0000001536874781.png
deleted file mode 100644
index be2c9ea1..00000000
Binary files a/docs/lts/umn/en-us_image_0000001536874781.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001557984216.png b/docs/lts/umn/en-us_image_0000001557984216.png
new file mode 100644
index 00000000..db7d7f9d
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001557984216.png differ
diff --git a/docs/lts/umn/en-us_image_0000001565005278.png b/docs/lts/umn/en-us_image_0000001565005278.png
deleted file mode 100644
index 02efcbce..00000000
Binary files a/docs/lts/umn/en-us_image_0000001565005278.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001576175974.png b/docs/lts/umn/en-us_image_0000001576175974.png
deleted file mode 100644
index c9d020ac..00000000
Binary files a/docs/lts/umn/en-us_image_0000001576175974.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001576328724.png b/docs/lts/umn/en-us_image_0000001576328724.png
deleted file mode 100644
index 04bc317c..00000000
Binary files a/docs/lts/umn/en-us_image_0000001576328724.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001576333032.png b/docs/lts/umn/en-us_image_0000001576333032.png
deleted file mode 100644
index 513fef15..00000000
Binary files a/docs/lts/umn/en-us_image_0000001576333032.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001579917292.png b/docs/lts/umn/en-us_image_0000001579917292.png
new file mode 100644
index 00000000..dbe846dd
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001579917292.png differ
diff --git a/docs/lts/umn/en-us_image_0000001580789472.png b/docs/lts/umn/en-us_image_0000001580789472.png
new file mode 100644
index 00000000..a20e7cdb
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001580789472.png differ
diff --git a/docs/lts/umn/en-us_image_0000001605059081.png b/docs/lts/umn/en-us_image_0000001605059081.png
new file mode 100644
index 00000000..153f42eb
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001605059081.png differ
diff --git a/docs/lts/umn/en-us_image_0000001476964177.png b/docs/lts/umn/en-us_image_0000001608069337.png
similarity index 100%
rename from docs/lts/umn/en-us_image_0000001476964177.png
rename to docs/lts/umn/en-us_image_0000001608069337.png
diff --git a/docs/lts/umn/en-us_image_0000001611907193.png b/docs/lts/umn/en-us_image_0000001611907193.png
new file mode 100644
index 00000000..ce9d4239
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001611907193.png differ
diff --git a/docs/lts/umn/en-us_image_0000001611940613.png b/docs/lts/umn/en-us_image_0000001611940613.png
new file mode 100644
index 00000000..9fc07ae3
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001611940613.png differ
diff --git a/docs/lts/umn/en-us_image_0000001612024421.png b/docs/lts/umn/en-us_image_0000001612024421.png
new file mode 100644
index 00000000..15aa9752
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001612024421.png differ
diff --git a/docs/lts/umn/en-us_image_0000001612061257.png b/docs/lts/umn/en-us_image_0000001612061257.png
new file mode 100644
index 00000000..cd1a47ba
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001612061257.png differ
diff --git a/docs/lts/umn/en-us_image_0000001614981805.png b/docs/lts/umn/en-us_image_0000001614981805.png
deleted file mode 100644
index 814fbce3..00000000
Binary files a/docs/lts/umn/en-us_image_0000001614981805.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001615509865.png b/docs/lts/umn/en-us_image_0000001615509865.png
deleted file mode 100644
index 02efcbce..00000000
Binary files a/docs/lts/umn/en-us_image_0000001615509865.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001626564893.png b/docs/lts/umn/en-us_image_0000001626564893.png
deleted file mode 100644
index 3c9fba2b..00000000
Binary files a/docs/lts/umn/en-us_image_0000001626564893.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001626584937.png b/docs/lts/umn/en-us_image_0000001626584937.png
deleted file mode 100644
index 0d894863..00000000
Binary files a/docs/lts/umn/en-us_image_0000001626584937.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0000001217747176.png b/docs/lts/umn/en-us_image_0000001637679773.png
similarity index 100%
rename from docs/lts/umn/en-us_image_0000001217747176.png
rename to docs/lts/umn/en-us_image_0000001637679773.png
diff --git a/docs/lts/umn/en-us_image_0000001658312108.png b/docs/lts/umn/en-us_image_0000001658312108.png
new file mode 100644
index 00000000..7d815e01
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001658312108.png differ
diff --git a/docs/lts/umn/en-us_image_0000001658469148.png b/docs/lts/umn/en-us_image_0000001658469148.png
new file mode 100644
index 00000000..fc900c80
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001658469148.png differ
diff --git a/docs/lts/umn/en-us_image_0000001674961080.png b/docs/lts/umn/en-us_image_0000001674961080.png
new file mode 100644
index 00000000..5fd20a4e
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001674961080.png differ
diff --git a/docs/lts/umn/en-us_image_0000001706710657.png b/docs/lts/umn/en-us_image_0000001706710657.png
new file mode 100644
index 00000000..fc900c80
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001706710657.png differ
diff --git a/docs/lts/umn/en-us_image_0000001262717056.png b/docs/lts/umn/en-us_image_0000001706749901.png
similarity index 100%
rename from docs/lts/umn/en-us_image_0000001262717056.png
rename to docs/lts/umn/en-us_image_0000001706749901.png
diff --git a/docs/lts/umn/en-us_image_0000001748544704.png b/docs/lts/umn/en-us_image_0000001748544704.png
new file mode 100644
index 00000000..00499ee0
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001748544704.png differ
diff --git a/docs/lts/umn/en-us_image_0000001748704148.png b/docs/lts/umn/en-us_image_0000001748704148.png
new file mode 100644
index 00000000..cb4f13d9
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001748704148.png differ
diff --git a/docs/lts/umn/en-us_image_0000001748707920.png b/docs/lts/umn/en-us_image_0000001748707920.png
new file mode 100644
index 00000000..9fc8a3cc
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001748707920.png differ
diff --git a/docs/lts/umn/en-us_image_0000001748708036.png b/docs/lts/umn/en-us_image_0000001748708036.png
new file mode 100644
index 00000000..349eb5af
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001748708036.png differ
diff --git a/docs/lts/umn/en-us_image_0000001748984554.png b/docs/lts/umn/en-us_image_0000001748984554.png
new file mode 100644
index 00000000..74594e18
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001748984554.png differ
diff --git a/docs/lts/umn/en-us_image_0000001791568973.png b/docs/lts/umn/en-us_image_0000001791568973.png
new file mode 100644
index 00000000..75729a66
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001791568973.png differ
diff --git a/docs/lts/umn/en-us_image_0000001795704605.png b/docs/lts/umn/en-us_image_0000001795704605.png
new file mode 100644
index 00000000..0bc2280e
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001795704605.png differ
diff --git a/docs/lts/umn/en-us_image_0000001795707481.png b/docs/lts/umn/en-us_image_0000001795707481.png
new file mode 100644
index 00000000..ec42d80c
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001795707481.png differ
diff --git a/docs/lts/umn/en-us_image_0000001795825789.png b/docs/lts/umn/en-us_image_0000001795825789.png
new file mode 100644
index 00000000..cacee91a
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001795825789.png differ
diff --git a/docs/lts/umn/en-us_image_0000001795826161.png b/docs/lts/umn/en-us_image_0000001795826161.png
new file mode 100644
index 00000000..8a6c6f65
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001795826161.png differ
diff --git a/docs/lts/umn/en-us_image_0000001795840149.png b/docs/lts/umn/en-us_image_0000001795840149.png
new file mode 100644
index 00000000..c3735dc5
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001795840149.png differ
diff --git a/docs/lts/umn/en-us_image_0000001795947797.png b/docs/lts/umn/en-us_image_0000001795947797.png
new file mode 100644
index 00000000..f154ffc9
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001795947797.png differ
diff --git a/docs/lts/umn/en-us_image_0000001809715517.png b/docs/lts/umn/en-us_image_0000001809715517.png
new file mode 100644
index 00000000..5fd20a4e
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001809715517.png differ
diff --git a/docs/lts/umn/en-us_image_0000001924745402.png b/docs/lts/umn/en-us_image_0000001924745402.png
new file mode 100644
index 00000000..6345c8ed
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001924745402.png differ
diff --git a/docs/lts/umn/en-us_image_0000001413544114.png b/docs/lts/umn/en-us_image_0000001924750582.png
similarity index 100%
rename from docs/lts/umn/en-us_image_0000001413544114.png
rename to docs/lts/umn/en-us_image_0000001924750582.png
diff --git a/docs/lts/umn/en-us_image_0000001459383609.png b/docs/lts/umn/en-us_image_0000001924750594.png
similarity index 100%
rename from docs/lts/umn/en-us_image_0000001459383609.png
rename to docs/lts/umn/en-us_image_0000001924750594.png
diff --git a/docs/lts/umn/en-us_image_0000001947827468.png b/docs/lts/umn/en-us_image_0000001947827468.png
new file mode 100644
index 00000000..fe6af109
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001947827468.png differ
diff --git a/docs/lts/umn/en-us_image_0000001217754022.png b/docs/lts/umn/en-us_image_0000001951869649.png
similarity index 100%
rename from docs/lts/umn/en-us_image_0000001217754022.png
rename to docs/lts/umn/en-us_image_0000001951869649.png
diff --git a/docs/lts/umn/en-us_image_0000001261967201.png b/docs/lts/umn/en-us_image_0000001952029417.png
similarity index 100%
rename from docs/lts/umn/en-us_image_0000001261967201.png
rename to docs/lts/umn/en-us_image_0000001952029417.png
diff --git a/docs/lts/umn/en-us_image_0000001262550041.png b/docs/lts/umn/en-us_image_0000001952029421.png
similarity index 100%
rename from docs/lts/umn/en-us_image_0000001262550041.png
rename to docs/lts/umn/en-us_image_0000001952029421.png
diff --git a/docs/lts/umn/en-us_image_0000001954290198.png b/docs/lts/umn/en-us_image_0000001954290198.png
new file mode 100644
index 00000000..e0482693
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001954290198.png differ
diff --git a/docs/lts/umn/en-us_image_0000001954290246.png b/docs/lts/umn/en-us_image_0000001954290246.png
new file mode 100644
index 00000000..4e10a017
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001954290246.png differ
diff --git a/docs/lts/umn/en-us_image_0000001310281889.png b/docs/lts/umn/en-us_image_0000001955235130.png
similarity index 100%
rename from docs/lts/umn/en-us_image_0000001310281889.png
rename to docs/lts/umn/en-us_image_0000001955235130.png
diff --git a/docs/lts/umn/en-us_image_0000001956646332.png b/docs/lts/umn/en-us_image_0000001956646332.png
new file mode 100644
index 00000000..9f4508e5
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001956646332.png differ
diff --git a/docs/lts/umn/en-us_image_0000001960165240.png b/docs/lts/umn/en-us_image_0000001960165240.png
new file mode 100644
index 00000000..9f4508e5
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001960165240.png differ
diff --git a/docs/lts/umn/en-us_image_0000001960332596.png b/docs/lts/umn/en-us_image_0000001960332596.png
new file mode 100644
index 00000000..a262e8b8
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001960332596.png differ
diff --git a/docs/lts/umn/en-us_image_0000001965754048.png b/docs/lts/umn/en-us_image_0000001965754048.png
new file mode 100644
index 00000000..482b05a2
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001965754048.png differ
diff --git a/docs/lts/umn/en-us_image_0000001966867180.png b/docs/lts/umn/en-us_image_0000001966867180.png
new file mode 100644
index 00000000..d6e3fe6f
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001966867180.png differ
diff --git a/docs/lts/umn/en-us_image_0000001966970380.png b/docs/lts/umn/en-us_image_0000001966970380.png
new file mode 100644
index 00000000..a77ae741
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001966970380.png differ
diff --git a/docs/lts/umn/en-us_image_0000001966970384.png b/docs/lts/umn/en-us_image_0000001966970384.png
new file mode 100644
index 00000000..cbf97393
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001966970384.png differ
diff --git a/docs/lts/umn/en-us_image_0000001967130160.png b/docs/lts/umn/en-us_image_0000001967130160.png
new file mode 100644
index 00000000..3a2dd4c7
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001967130160.png differ
diff --git a/docs/lts/umn/en-us_image_0000001972605366.png b/docs/lts/umn/en-us_image_0000001972605366.png
new file mode 100644
index 00000000..ca8ca6c8
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001972605366.png differ
diff --git a/docs/lts/umn/en-us_image_0000001972798404.png b/docs/lts/umn/en-us_image_0000001972798404.png
new file mode 100644
index 00000000..5b93ee7b
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001972798404.png differ
diff --git a/docs/lts/umn/en-us_image_0000001972864060.png b/docs/lts/umn/en-us_image_0000001972864060.png
new file mode 100644
index 00000000..b3395b31
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001972864060.png differ
diff --git a/docs/lts/umn/en-us_image_0000001976408865.png b/docs/lts/umn/en-us_image_0000001976408865.png
new file mode 100644
index 00000000..fe6af109
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001976408865.png differ
diff --git a/docs/lts/umn/en-us_image_0000001981261620.png b/docs/lts/umn/en-us_image_0000001981261620.png
new file mode 100644
index 00000000..6e6b96c3
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001981261620.png differ
diff --git a/docs/lts/umn/en-us_image_0000001991154261.png b/docs/lts/umn/en-us_image_0000001991154261.png
new file mode 100644
index 00000000..6c9f5a79
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001991154261.png differ
diff --git a/docs/lts/umn/en-us_image_0000001991274437.png b/docs/lts/umn/en-us_image_0000001991274437.png
new file mode 100644
index 00000000..9f4508e5
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001991274437.png differ
diff --git a/docs/lts/umn/en-us_image_0000001992368877.png b/docs/lts/umn/en-us_image_0000001992368877.png
new file mode 100644
index 00000000..84a6c850
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001992368877.png differ
diff --git a/docs/lts/umn/en-us_image_0000001992588517.png b/docs/lts/umn/en-us_image_0000001992588517.png
new file mode 100644
index 00000000..32e9be03
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001992588517.png differ
diff --git a/docs/lts/umn/en-us_image_0000001993925213.png b/docs/lts/umn/en-us_image_0000001993925213.png
new file mode 100644
index 00000000..9f4508e5
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001993925213.png differ
diff --git a/docs/lts/umn/en-us_image_0000001993925293.png b/docs/lts/umn/en-us_image_0000001993925293.png
new file mode 100644
index 00000000..9f4508e5
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001993925293.png differ
diff --git a/docs/lts/umn/en-us_image_0000001996772965.png b/docs/lts/umn/en-us_image_0000001996772965.png
new file mode 100644
index 00000000..ac16d845
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001996772965.png differ
diff --git a/docs/lts/umn/en-us_image_0000001996805997.png b/docs/lts/umn/en-us_image_0000001996805997.png
new file mode 100644
index 00000000..835fd5da
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001996805997.png differ
diff --git a/docs/lts/umn/en-us_image_0000001999720813.png b/docs/lts/umn/en-us_image_0000001999720813.png
new file mode 100644
index 00000000..0fe93c0a
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001999720813.png differ
diff --git a/docs/lts/umn/en-us_image_0000002003650313.png b/docs/lts/umn/en-us_image_0000002003650313.png
new file mode 100644
index 00000000..caf772d4
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000002003650313.png differ
diff --git a/docs/lts/umn/en-us_image_0000002003770857.png b/docs/lts/umn/en-us_image_0000002003770857.png
new file mode 100644
index 00000000..be16e59d
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000002003770857.png differ
diff --git a/docs/lts/umn/en-us_image_0000002003770861.png b/docs/lts/umn/en-us_image_0000002003770861.png
new file mode 100644
index 00000000..767edf80
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000002003770861.png differ
diff --git a/docs/lts/umn/en-us_image_0000002009164357.png b/docs/lts/umn/en-us_image_0000002009164357.png
new file mode 100644
index 00000000..f199359f
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000002009164357.png differ
diff --git a/docs/lts/umn/en-us_image_0000002009165089.png b/docs/lts/umn/en-us_image_0000002009165089.png
new file mode 100644
index 00000000..293cf4bc
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000002009165089.png differ
diff --git a/docs/lts/umn/en-us_image_0000002009219465.png b/docs/lts/umn/en-us_image_0000002009219465.png
new file mode 100644
index 00000000..64b28805
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000002009219465.png differ
diff --git a/docs/lts/umn/en-us_image_0000002017782149.png b/docs/lts/umn/en-us_image_0000002017782149.png
new file mode 100644
index 00000000..8fb7744a
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000002017782149.png differ
diff --git a/docs/lts/umn/en-us_image_0000001262713829.png b/docs/lts/umn/en-us_image_0000002029238830.png
similarity index 100%
rename from docs/lts/umn/en-us_image_0000001262713829.png
rename to docs/lts/umn/en-us_image_0000002029238830.png
diff --git a/docs/lts/umn/en-us_image_0000002065396965.png b/docs/lts/umn/en-us_image_0000002065396965.png
new file mode 100644
index 00000000..bffa40ef
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000002065396965.png differ
diff --git a/docs/lts/umn/en-us_image_0000002065402777.png b/docs/lts/umn/en-us_image_0000002065402777.png
new file mode 100644
index 00000000..51b66435
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000002065402777.png differ
diff --git a/docs/lts/umn/en-us_image_0224007651.png b/docs/lts/umn/en-us_image_0224007651.png
deleted file mode 100644
index 17ffb3e6..00000000
Binary files a/docs/lts/umn/en-us_image_0224007651.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0224007665.png b/docs/lts/umn/en-us_image_0224007665.png
deleted file mode 100644
index 929bab9a..00000000
Binary files a/docs/lts/umn/en-us_image_0224007665.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0224007675.png b/docs/lts/umn/en-us_image_0224007675.png
deleted file mode 100644
index 20b8afa5..00000000
Binary files a/docs/lts/umn/en-us_image_0224007675.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0224007681.png b/docs/lts/umn/en-us_image_0224007681.png
deleted file mode 100644
index 7da509bf..00000000
Binary files a/docs/lts/umn/en-us_image_0224007681.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_image_0231061605.png b/docs/lts/umn/en-us_image_0231061605.png
deleted file mode 100644
index 7ab00e59..00000000
Binary files a/docs/lts/umn/en-us_image_0231061605.png and /dev/null differ
diff --git a/docs/lts/umn/en-us_topic_0000001727118868.html b/docs/lts/umn/en-us_topic_0000001727118868.html
new file mode 100644
index 00000000..704197b2
--- /dev/null
+++ b/docs/lts/umn/en-us_topic_0000001727118868.html
@@ -0,0 +1,17 @@
+
+
+
What Do I Do If ICAgent Is Displayed as Offline on the LTS Console After Installation?
+In this case, perform the following steps:
+
- Check whether the ICAgent network connection is normal.
- Log in to the host where ICAgent is installed.
- Run the netstat -nap | grep icagent command to check whether the network connection status of the ICAgent process is ESTABLISHED. If yes, the network connection is normal.
Check whether the connection status of ports 30200 and 30201 on the server is ESTABLISHED. If not, check whether these ports are allowed in the security group.
+
+
+ - Check whether the ICAgent authentication is successful.
- Run the cd /var/ICAgent command to go to the ICAgent log directory.
- Run the zgrep 'msworkflow' * | grep 'retCode\[' command to query the ICAgent authentication log.
- If 200 is returned, the authentication is successful. If ICAgent is still offline, contact technical support.
- If the return code is not 200, check whether the AK/SK pair entered during ICAgent installation is correct. If not, go to the next step.
+
+ - Obtain the correct AK/SK pair and install ICAgent again.
+
+
+
diff --git a/docs/lts/umn/en-us_topic_0000001795709689.html b/docs/lts/umn/en-us_topic_0000001795709689.html
new file mode 100644
index 00000000..e8e2e5cd
--- /dev/null
+++ b/docs/lts/umn/en-us_topic_0000001795709689.html
@@ -0,0 +1,32 @@
+
+
+What Do I Do If I Could Not Search for Logs on LTS?
+When you search for logs on the LTS console, if a message is displayed indicating that the query result is inaccurate, too many log results are matched, or field XXX without indexing configured cannot be queried, perform the following operations:
+
Message Displayed During Query: Inaccurate Query Results
- Possible causes: There are too many logs in the query time range, and not all logs are displayed.
- Solution: Click the query button multiple times until you obtain all logs, or shorten the query time range and query again.
+
+
Too Many Logs Results from Log Query
- Possible cause: Only searches with phrase #"value" can ensure the sequence of keywords. For example, if the query statement is abc def, logs that contain either abc or def and logs that contain the phrase abc def will be matched.
- Solution: Use phrase #"abc def" to accurately match logs containing phrase abc def.
+
+
Expected Logs Not Obtained with Specific Search Statements and No Error Message Displayed
- Possible causes: Search delimiters are not supported, or * and ? in a search statement are regarded as common characters and are not used as wildcards.
- Solution: Use the correct query statement.
+
+
Message Displayed During Query: Field XXX Is Not Configured with Indexing and Cannot Be Queried
- Possible cause: No field indexing is configured.
- Solution: Create an index for field XXX on the Index Settings tab page and run the query statement again.
+
+
Message Displayed During Query: Full-Text Index Not Enabled and content Field and Full-Text Query Unsupported
- Possible cause: Full-text indexing is disabled.
- Solution: Enable Index Whole Text on the Index Settings tab page and run the query statement again.
+
+
Message Displayed During Query: Do Not Start with an Asterisk (*) or a Question Mark (?)
- Possible cause: An asterisk (*) or question mark (?) is placed before the query statement.
- Solution: Modify the query statement or use a correct delimiter.
+
+
Message Displayed During Query: long and float Fields Do Not Support Fuzzy Query Using Asterisks (*) or Question Marks (?)
- Possible cause: An asterisk (*) or question mark (?) is used to query fields of the long and float types.
- Solution: Modify the query statement and use operators (>=<) or IN syntax for range query.
+
+
Message Displayed During Query: string Fields Do Not Support Range Query Using the Operator (>=<) or IN Syntax
- Possible cause: Operators (>=<) or the IN syntax is used to query fields of the string type.
- Solutions:
- Modify the query statement and use the asterisk (*) or question mark (?) to perform fuzzy query.
- Change the value of this field to a number.
+
+
+
Message Displayed During Query: The Search Syntax Is Incorrect and the Query Statement Needs to Be Modified
- Possible cause: The syntax of the operator is incorrect.
Solution: Each operator has its syntax rule. Modify the search statement based on the rule. For example, operator = requires that the value on the right must be digits.
+ - Possible cause: The search statement contains syntax keywords.
Solution: If the log to search contains syntax keywords, the search statement must be enclosed in double quotation marks to convert the keywords into common characters. For example, if and is a syntax keyword, change the query statement field:and to field:"and".
+
+
+
+
+
diff --git a/docs/lts/umn/lts-03205.html b/docs/lts/umn/lts-03205.html
index bac45c40..788cbcd3 100644
--- a/docs/lts/umn/lts-03205.html
+++ b/docs/lts/umn/lts-03205.html
@@ -1,707 +1,229 @@
-Permissions Management
-Description
If you need to assign different permissions to employees in your enterprise to access your LTS resources, is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your LTS resources.
-
With IAM, you can use your account to create IAM users for your employees, and assign permissions to the users to control their access to LTS resources. For example, some software developers in your enterprise need to use LTS resources but should not delete them or perform other high-risk operations. In this case, you can create IAM users for the software developers and grant them only the permissions required.
-
If your account does not need individual IAM users for permissions management, you may skip over this section.
-
IAM can be used for free. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.
+
Permissions
+
Description
If you need to grant your enterprise personnel permission to access your LTS resources, use Identity and Access Management (IAM). IAM provides identity authentication, fine-grained permissions management, and access control. IAM helps you secure access to your LTS resources.
+
With IAM, you can create IAM users and grant them permission to access only specific resources. For example, if you want some software developers in your enterprise to be able to use LTS resources but do not want them to be able to delete resources or perform any other high-risk operations, you can create IAM users and grant permission to use LTS resources but not permission to delete them.
+
If your account does not require individual IAM users for permissions management, you can skip this section.
+
IAM is a free service. You only pay for the resources in your account. For more information about IAM, see IAM Service Overview.
-
LTS Permissions
By default, new IAM users do not have permissions assigned. You need to add users to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.
-
LTS is a project-level service deployed and accessed in specific physical regions. To assign LTS permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing LTS, the users need to switch to a region where they have been authorized to use LTS.
-
Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant Elastic Cloud Server (ECS) users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs.
+
LTS Permissions
New users do not have any permissions assigned by default. You need to first add them to one or more groups and then attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on LTS based on the permissions they have been assigned.
+
LTS is a project-level service deployed for specific regions. When you set Scope to Region-specific projects and select the specified projects in the specified regions, the users only have permissions for LTS in the selected projects. If you select All projects, the users have permissions for LTS in all region-specific projects. When accessing LTS, the users need to switch to the authorized region.
+
You can grant permissions by using roles and policies.
+
- Roles: A coarse-grained authorization strategy that defines permissions by job responsibility. Only a limited number of service-level roles are available for authorization. Cloud services often depend on each other. When you grant permissions using roles, you also need to attach any existing role dependencies. Roles are not ideal for fine-grained authorization and least privilege access.
- Policies: A fine-grained authorization strategy that defines permissions required to perform operations on specific cloud resources under certain conditions. This type of authorization is more flexible and is ideal for least privilege access.
The system permissions supported by LTS are listed in Table 1.
-
Table 1 LTS system permissionsName
+Table 1 System-defined permissions for LTSRole/Policy Name
|
-Description
+ | Description
|
-Type
+ | Type
|
-Dependency
+ | Dependencies
|
-LTS FullAccess
+ | LTS FullAccess
|
-Full permissions for LTS. Users with these permissions can perform operations on LTS.
+ | Full permissions for LTS. Users with these permissions can perform operations on LTS.
|
-System-defined policy
+ | System-defined policy
|
-CCE Administrator, OBS Administrator, and AOM FullAccess
+ | CCE Administrator, OBS Administrator, and AOM FullAccess
|
-LTS ReadOnlyAccess
+ | LTS ReadOnlyAccess
|
-Read-only permissions for LTS. Users with these permissions can only view LTS data.
+ | Read-only permissions for LTS. Users with these permissions can only view LTS data.
|
-System-defined policy
+ | System-defined policy
|
-CCE Administrator, OBS Administrator, and AOM FullAccess
+ | CCE Administrator, OBS Administrator, and AOM FullAccess
|
-LTS Administrator
+ | LTS Administrator
|
-Administrator permissions for LTS.
+ | Administrator permissions for LTS.
|
-System-defined role
+ | System-defined role
|
-This role is dependent on the Tenant Guest and Tenant Administrator roles.
+ | Tenant Guest and Tenant Administrator
|
-Table 2 lists the common operations supported by each system-defined policy and role of LTS. Choose the appropriate policies and roles according to this table.
+Table 2 lists the common operations supported by system-defined permissions for LTS.
-Table 2 Common operations supported by each LTS system policy or roleOperation
+Table 2 Common operations supported by system-defined permissionsOperation
|
-LTS FullAccess
+ | LTS FullAccess
|
-LTS ReadOnlyAccess
+ | LTS ReadOnlyAccess
|
-LTS Administrator
+ | LTS Administrator
|
-Querying a log group
+ | Querying a log group
|
-√
+ | √
|
-√
+ | √
|
-√
+ | √
|
-Creating a log group
+ | Creating a log group
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Modifying a log group
+ | Modifying a log group
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Deleting a log group
+ | Deleting a log group
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Querying a log stream
+ | Querying a log stream
|
-√
+ | √
|
-√
+ | √
|
-√
+ | √
|
-Creating a log stream
+ | Creating a log stream
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Modifying a log stream
+ | Modifying a log stream
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Deleting a log stream
+ | Deleting a log stream
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Configuring log collection from hosts
+ | Configuring log collection from hosts
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Viewing a log transfer task
+ | Viewing a log transfer task
|
-√
+ | √
|
-√
+ | √
|
-√
+ | √
|
-Creating a log transfer task
+ | Creating a log transfer task
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Modifying a log transfer task
+ | Modifying a log transfer task
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Deleting a log transfer task
+ | Deleting a log transfer task
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Enabling a log transfer task
+ | Enabling a log transfer task
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Disabling a log transfer task
+ | Disabling a log transfer task
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Installing ICAgent
+ | Installing ICAgent
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Upgrading ICAgent
+ | Upgrading ICAgent
|
-√
+ | √
|
-×
+ | ×
|
-√
+ | √
|
-Uninstalling ICAgent
+ | Uninstalling ICAgent
|
-√
+ | √
|
-×
+ | ×
|
-√
- |
-
-
-
-
-To use a custom fine-grained policy, log in to IAM as the administrator and select fine-grained permissions of LTS as required.
-Table 3 describes fine-grained permission dependencies of LTS.
-
-Table 3 Fine-grained permission dependencies of LTSPermission
- |
-Description
- |
-Dependency
- |
-
-
-lts:agents:list
- |
-List agents
- |
-None
- |
-
-lts:buckets:get
- |
-Get bucket
- |
-None
- |
-
-lts:groups:put
- |
-Put log group
- |
-None
- |
-
-lts:transfers:create
- |
-Create transfer
- |
-obs:bucket:PutBucketAcl
-obs:bucket:GetBucketAcl
-obs:bucket:GetEncryptionConfiguration
-obs:bucket:HeadBucket
-dis:streams:list
-dis:streamPolicies:list
- |
-
-lts:groups:get
- |
-Get log group
- |
-None
- |
-
-lts:transfers:put
- |
-Put transfer
- |
-obs:bucket:PutBucketAcl
-obs:bucket:GetBucketAcl
-obs:bucket:GetEncryptionConfiguration
-obs:bucket:HeadBucket
-dis:streams:list
-dis:streamPolicies:list
- |
-
-lts:resourceTags:delete
- |
-Delete resource tag
- |
-None
- |
-
-lts:ecsOsLogPaths:list
- |
-List ecs os logs paths
- |
-None
- |
-
-lts:structConfig:create
- |
-Create struct config
- |
-None
- |
-
-lts:agentsConf:get
- |
-Get agent conf
- |
-None
- |
-
-lts:logIndex:list
- |
-Get log index
- |
-None
- |
-
-lts:transfers:delete
- |
-Delete transfer
- |
-None
- |
-
-lts:regex:create
- |
-Create struct regex
- |
-None
- |
-
-lts:subscriptions:delete
- |
-Delete subscription
- |
-None
- |
-
-lts:overviewLogsLast:list
- |
-List overview last logs
- |
-None
- |
-
-lts:logIndex:get
- |
-Get log index
- |
-None
- |
-
-lts:sqlalarmrules:create
- |
-Create alarm options
- |
-None
- |
-
-lts:agentsConf:create
- |
-Create agent conf
- |
-None
- |
-
-lts:sqlalarmrules:get
- |
-Get alarm options
- |
-None
- |
-
-lts:datasources:batchdelete
- |
-Batch delete datasource
- |
-None
- |
-
-lts:structConfig:put
- |
-Update struct config
- |
-None
- |
-
-lts:groups:list
- |
-List log groups
- |
-None
- |
-
-lts:sqlalarmrules:delete
- |
-Delete alarm options
- |
-None
- |
-
-lts:transfers:action
- |
-Enabled transfer
- |
-None
- |
-
-lts:datasources:post
- |
-Post datasource
- |
-None
- |
-
-lts:topics:create
- |
-Create log topic
- |
-None
- |
-
-lts:resourceTags:get
- |
-Query resource tags
- |
-None
- |
-
-lts:logs:list
- |
-List logs
- |
-None
- |
-
-lts:subscriptions:create
- |
-Create subscription
- |
-None
- |
-
-lts:overviewLogsTopTopic:get
- |
-List overview top logs
- |
-None
- |
-
-lts:datasources:put
- |
-Put datasource
- |
-None
- |
-
-lts:structConfig:delete
- |
-Delete struct config
- |
-None
- |
-
-lts:logIndex:delete
- |
-Deleting a specified log index
- |
-None
- |
-
-lts:topics:delete
- |
-Delete log topics
- |
-None
- |
-
-lts:agentSupportedOsLogPaths:list
- |
-List agent supported os logs paths
- |
-None
- |
-
-lts:topics:put
- |
-Put log topic
- |
-None
- |
-
-lts:agentHeartbeat:post
- |
-Post agent heartbeat
- |
-None
- |
-
-lts:logsByName:upload
- |
-Upload logs by name
- |
-None
- |
-
-lts:buckets:list
- |
-List buckets
- |
-None
- |
-
-lts:logIndex:post
- |
-Create log index
- |
-None
- |
-
-lts:logContext:list
- |
-List logs context
- |
-None
- |
-
-lts:groups:delete
- |
-Delete log group
- |
-None
- |
-
-lts:resourceTags:put
- |
-Update resource tags
- |
-None
- |
-
-lts:structConfig:get
- |
-Get struct config
- |
-None
- |
-
-lts:overviewLogTotal:get
- |
-Get overview logs total
- |
-None
- |
-
-lts:subscriptions:put
- |
-Put subscription
- |
-None
- |
-
-lts:subscriptions:list
- |
-List subscription
- |
-None
- |
-
-lts:datasources:delete
- |
-Delete datasource
- |
-None
- |
-
-lts:transfersStatus:get
- |
-List transfer status
- |
-None
- |
-
-lts:logIndex:put
- |
-Put log index
- |
-None
- |
-
-lts:sqlalarmrules:put
- |
-Modify alarm options
- |
-None
- |
-
-lts:logs:upload
- |
-Upload logs
- |
-None
- |
-
-lts:agentDetails:list
- |
-List agent diagnostic log
- |
-None
- |
-
-lts:agentsConf:put
- |
-Put agent conf
- |
-None
- |
-
-lts:logstreams:list
- |
-Check logstream resources
- |
-None
- |
-
-lts:subscriptions:get
- |
-Get subscription
- |
-None
- |
-
-lts:disStreams:list
- |
-Query DIS pipe
- |
-None
- |
-
-lts:groupTopics:put
- |
-Create log group and log topic
- |
-None
- |
-
-lts:resourceInstance:list
- |
-Query resource instance
- |
-None
- |
-
-lts:transfers:list
- |
-List transfers
- |
-None
- |
-
-lts:topics:get
- |
-Get log topic
- |
-None
- |
-
-lts:agentsConf:delete
- |
-Delete agent conf
- |
-None
- |
-
-lts:agentEcs:list
- |
-List agent ecs
- |
-None
- |
-
-lts:indiceLogs:list
- |
-Search indiceLogs
- |
-None
- |
-
-lts:topics:list
- |
-List log topic
- |
-None
+ | √
|
diff --git a/docs/lts/umn/lts-0740.html b/docs/lts/umn/lts-0740.html
index 17c65a08..6191b15c 100644
--- a/docs/lts/umn/lts-0740.html
+++ b/docs/lts/umn/lts-0740.html
@@ -24,12 +24,12 @@
Log writes
|
-Logs can be written up to 1000 times per second in an account.
+ | Logs can be written up to 1,000 times per second in an account.
|
To increase the upper limit, contact technical support engineers.
|
-Log query
+ | Log query traffic
|
Up to 1 MB of logs can be returned in a single API query for an account.
|
@@ -62,7 +62,7 @@
Log query traffic
|
-Up to 10 MB of logs can be returned in a single API query for a log group.
+ | Up to 10 MB of logs are returned in a single API query for a log group.
|
N/A
@@ -94,7 +94,7 @@
|
Log query traffic
|
-Up to 10 MB of logs can be returned in a single API query for a log stream.
+ | Up to 10 MB of logs are returned in a single API query for a log stream.
|
N/A
|
diff --git a/docs/lts/umn/lts_01_0001.html b/docs/lts/umn/lts_01_0001.html
index c943b618..ede70e33 100644
--- a/docs/lts/umn/lts_01_0001.html
+++ b/docs/lts/umn/lts_01_0001.html
@@ -4,15 +4,15 @@
-- Introduction
+ - What Is LTS?
- Basic Concepts
-- Basic Functions
+ - Features
- Usage Restrictions
-- Permissions Management
+ - Permissions
- Related Services
diff --git a/docs/lts/umn/lts_01_0002.html b/docs/lts/umn/lts_01_0002.html
index 1ec37418..e3f267b0 100644
--- a/docs/lts/umn/lts_01_0002.html
+++ b/docs/lts/umn/lts_01_0002.html
@@ -1,8 +1,8 @@
-Introduction
-Log Tank Service (LTS) enables you to collect logs from hosts and cloud services for centralized management, and analyze large volumes of logs efficiently, securely, and in real time. LTS provides you with the insights for optimizing the availability and performance of cloud services and applications. It allows you to make faster data-driven decisions, perform device O&M with ease, and analyze service trends.
- Figure 1 How LTS works
+ What Is LTS?
+ Log Tank Service (LTS) is a high-performance, cost-effective log platform with diverse functions and high reliability. It offers full-stack log collection, search through tens of billions of logs in seconds, PBs of storage, log processing, visual charts, alarms, and transfer functions. It is designed for application O&M, security and compliance, and operations analysis.
+ Figure 1 LTS service diagram
diff --git a/docs/lts/umn/lts_01_0003.html b/docs/lts/umn/lts_01_0003.html
index 4b2ea4c1..aa4d9b19 100644
--- a/docs/lts/umn/lts_01_0003.html
+++ b/docs/lts/umn/lts_01_0003.html
@@ -1,10 +1,11 @@
Basic Concepts
- Log GroupsA log group is the basic unit for LTS to manage logs. You can query and transfer logs in log groups. Up to 100 log groups can be created in your account.
+ Log GroupsA log group is a collection of log streams. It is similar to a folder and is used to classify and manage log streams. You can create log streams in a log group.
- Log StreamsUp to 100 streams can be created in a log group.
- You can separate logs into different log streams based on log types, and name log streams in an easily identifiable way. This helps you quickly find your desired logs.
+ Log StreamsA log stream is the basic unit for log reads and writes.
+ You can sort logs of different types, such as operation logs and access logs, into different log streams. ICAgent will package and send the collected logs to LTS on a log stream basis. It makes it easier to find specific logs when you need them.
+ The use of log streams greatly reduces the number of log reads and writes and improves efficiency.
ICAgentICAgent is the log collection tool of LTS. If you want to use LTS to collect logs from a host, you need to install ICAgent on the host. Batch ICAgent installation is supported if you want to collect logs from multiple hosts. After ICAgent installation, you can check the ICAgent status on the LTS console in real time.
diff --git a/docs/lts/umn/lts_01_0004.html b/docs/lts/umn/lts_01_0004.html
index d223124d..d0ebc394 100644
--- a/docs/lts/umn/lts_01_0004.html
+++ b/docs/lts/umn/lts_01_0004.html
@@ -1,11 +1,32 @@
- Basic Functions
- Real-time Log CollectionYou can view real-time logs to keep track of the status of the services connected to LTS. You can also check logs in the last 7 days.
-
- Log Query and Real-Time AnalysisYou can set search criteria to filter reported logs for fault diagnosis and system tracking. This enables easier device O&M and service trend analysis.
-
- Log TransferReported logs are retained in LTS for 7 days by default. Retained logs are deleted once the period is over. For long-term storage, you can transfer logs to Object Storage Service (OBS) buckets.
+ Features
+ Before using LTS, learn its main features in Table 1.
+
+ Table 1 FeaturesFeature
+ |
+Description
+ |
+
+
+Real-time log collection
+ |
+Collects real-time logs and displays them on the LTS console in an intuitive and orderly manner. You can query logs or transfer logs for long-term storage.
+Collected logs can be structured or unstructured. Log structuring processes logs in log streams by extracting the logs in a fixed format or with a similar pattern based on the extraction rules you set. Then you can use SQL syntax to query the structured logs.
+ |
+
+High-volume storage and search
+ |
+Supports log query by keyword or fuzzy match, search of tens of billions of logs in seconds, and iterative search of hundreds of billions of logs.
+ |
+
+Log transfer
+ |
+- Allows you to transfer logs to OBS for long-term storage. Logs reported from hosts and cloud services are retained in LTS for a custom period. Log transfer is to replicate logs to the target cloud service. The original logs are retained in LTS and will be automatically deleted when the configured retention period ends.
+ |
+
+
+
diff --git a/docs/lts/umn/lts_01_0005.html b/docs/lts/umn/lts_01_0005.html
index 7c78f6a3..9601aa8f 100644
--- a/docs/lts/umn/lts_01_0005.html
+++ b/docs/lts/umn/lts_01_0005.html
@@ -1,17 +1,36 @@
Related Services
- VPCLTS provides a platform to store and analyze log data for Virtual Private Cloud (VPC). After VPC is associated with a log group and log stream in LTS, Network Interface Cards (NICs) logs are uploaded to LTS for preview, search, and storage.
-
- OBSObject Storage Service (OBS) is an object-based massive storage service. Logs can be transferred to OBS buckets for long-term storage.
-
- IAMIdentity and Access Management (IAM) provides identity authentication and permissions management. LTS calls IAM APIs to obtain administrator permissions for log management.
-
- CTSIf you enable Trace Analysis for a tracker in Cloud Trace Service (CTS), traces recorded by the tracker will be synchronized to LTS. You can then set custom filters to search for traces generated in the last 7 days in LTS.
-
- WAFYou can record attack logs and access logs of Web Application Firewall (WAF) in LTS, and use the logs for real-time decision-making, device O&M, and service trend analysis.
-
- ELBYou can ingest access logs of Elastic Load Balance (ELB) to a log stream of a log group in LTS. Then you can check the access logs to view details about HTTP and HTTPS requests sent to layer 7 load balancers and perform log analysis.
+ The relationships between LTS and other services are described in Table 1.
+
+ Table 1 Relationships with other servicesInteraction
+ |
+Related Service
+ |
+
+
+With Cloud Trace Service (CTS), you can record operations associated with LTS for future query, audit, and backtracking.
+ |
+CTS
+ |
+
+You can transfer logs to Object Storage Service (OBS) buckets for long-term storage, preventing log loss.
+ |
+OBS
+ |
+
+Application Operations Management (AOM) can collect site access statistics, monitor logs sent from LTS, and generate alarms.
+ |
+AOM
+ |
+
+Identity and Access Management (IAM) allows you to grant LTS permissions to IAM users under your account.
+ |
+IAM
+ |
+
+
+
diff --git a/docs/lts/umn/lts_01_0008.html b/docs/lts/umn/lts_01_0008.html
index 0730b972..ba1ddfdd 100644
--- a/docs/lts/umn/lts_01_0008.html
+++ b/docs/lts/umn/lts_01_0008.html
@@ -4,9 +4,15 @@
diff --git a/docs/lts/umn/lts_01_0009.html b/docs/lts/umn/lts_01_0009.html
deleted file mode 100644
index 0005ef8b..00000000
--- a/docs/lts/umn/lts_01_0009.html
+++ /dev/null
@@ -1,271 +0,0 @@
-
-
- Configuring the VPC Flow Log Function
- ScenariosA Virtual Private Cloud (VPC) flow log captures information about the traffic going to and from your VPC. You can use flow logs to monitor network traffic, analyze network attacks, and determine whether security groups and firewall rules need to be modified.
- You can obtain traffic details of VPC Network Interface Cards (NICs) from their logs on the LTS console.
- This section describes how to configure VPC flow log reporting.
-
- Constraints- A VPC is available.
- Currently, only C3, M3, and S2 ECSs are supported.
-
- Operation ProcessFigure 1 Flowchart
- Operations in Figure 1 are performed on different consoles:
- - Create log groups and log streams on the LTS console.
- Create and view VPC flow logs on the VPC console.
-
- Creating a Log Group- Log in to the management console.
- Click Service List and choose Management & Deployment > Log Tank Service.
Figure 2 Log management
- - On the Log Management page, click Create Log Group.
Figure 3 Creating a log group
- - On the displayed page, enter a log group name.
-
Table 1 Parameter descriptionParameter
- |
-Description
- |
-Example Value
- |
-
-
-Log Group Name
- |
-Specifies the log group name which must be globally unique. The configuration rules are as follows:
-- Must be a string of 1 to 64 characters.
- Only allows uppercase and lowercase letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot start with a period or underscore, or end with a period.
- |
-lts-group-7hjg
- |
-
-Log Retention Duration
- |
-Specifies the time period, in the unit of days, of storing logs in the LTS database. The default retention period for logs is seven days. Any logs stored longer than the retention period will be deleted.
- |
-7
- |
-
-
-
-
- - Click OK.
-
- Creating a Log StreamTo create a log stream in the log group, perform the following operations:
- - Log in to the management console.
- Click Service List and choose Management & Deployment > Log Tank Service.
- Click
next to the log group name to expand the log stream list.Figure 4 Log stream list
- - Click Create Log Stream.
Figure 5 Creating a log stream
- - On the displayed page, enter a log stream name.
-
Table 2 Log stream parametersParameter
- |
-Description
- |
-Example Value
- |
-
-
-Log Stream Name
- |
-The log stream name must be unique in a log group. The configuration rules are as follows:
-- Must be a string of 1 to 64 characters.
- Cannot start with a period (.) or underscore (_) or end with a period (.).
- |
-lts-topic-ncwm
- |
-
-
-
-
- - Click OK. The log stream is created.
-
- Creating a VPC Flow Log- Log in to the management console.
- In the upper left corner of the management console, select the target region and project.
- Choose Service List > Network > Virtual Private Cloud.
- In the navigation pane on the left, choose VPC Flow Logs.
- In the upper right corner, click Create VPC Flow Log. On the displayed page, configure parameters as prompted.
Figure 6 Creating a VPC flow log
-
- Table 3 Parameter descriptionParameter
- |
-Description
- |
-Example Value
- |
-
-
-Name
- |
-Specifies the VPC flow log name.
-The VPC flow log name can contain a maximum of 64 characters, which may consist of letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot contain spaces.
- |
-flowlog-495d
- |
-
-Resource Type
- |
-Specifies the resource type whose traffic is to be logged. You can select NIC, Subnet, or VPC.
- |
-NIC
- |
-
-Select NIC
- |
-Specifies the specific NIC whose traffic is to be logged. You can select only one NIC.
- |
--
- |
-
-Filter
- |
-- All: specifies that both accepted and rejected traffic of the specified resource will be logged.
- Accepted traffic: specifies that only accepted traffic of the specified resource will be logged. Accepted traffic refers to the traffic permitted by the security group or firewall.
- Rejected traffic: specifies that only rejected traffic of the specified resource will be logged. Rejected traffic refers to the traffic not permitted by the firewall.
- |
-All
- |
-
-Log Group
- |
-Specifies the log group created in LTS.
- |
-lts-group-wule
- |
-
-Log Topic
- |
-Specifies the log stream created in LTS.
- |
-LogTopic1
- |
-
-Description
- |
-Provides supplementary information about the VPC flow log. This parameter is optional.
-The VPC flow log description can contain a maximum of 255 characters and cannot contain angle brackets (< or >).
- |
--
- |
-
-
-
-
-
- - Click OK.
-
- Viewing a VPC Flow LogThe capture window is approximately 10 minutes, which indicates that a flow log record will be generated every 10 minutes. After creating a VPC flow log, you need to wait about 10 minutes before you can view the flow log record.
- - Log in to the management console.
- In the upper left corner of the management console, select the target region and project.
- Choose Service List > Network > Virtual Private Cloud.
- In the navigation pane on the left, choose VPC Flow Logs.
- Locate the target VPC flow log and click View Log Record in the Operation column to view information about the flow log record in LTS.
Figure 7 Viewing a log record
-Figure 8 Viewing details of a log record
-The flow log record is in the following format:
-<version> <project-id> <interface-id> <srcaddr> <dstaddr> <srcport> <dstport> <protocol> <packets> <bytes> <start> <end> <action> <log-status>
-Example 1: The following is an example of a flow log record in which traffic was allowed during the capture window:
-1 5f67944957444bd6bb4fe3b367de8f3d 1d515d18-1b36-47dc-a983-bd6512aed4bd 192.168.0.154 192.168.3.25 38929 53 17 1 96 1548752136 1548752736 ACCEPT OK
-Value 1 indicates the VPC flow log version. Traffic with a size of 96 bytes to NIC 1d515d18-1b36-47dc-a983-bd6512aed4bd during the past 10 minutes (from 16:55:36 to 17:05:36 on January 29, 2019) was allowed. A data packet was transmitted over the UDP protocol from source IP address 192.168.0.154 and port 38929 to destination IP address 192.168.3.25 and port 53.
-Example 2: The following is an example of a flow log record in which no data was recorded during the capture window:
-1 5f67944957444bd6bb4fe3b367de8f3d 1d515d18-1b36-47dc-a983-bd6512aed4bd - - - - - - - 1431280876 1431280934 - NODATA
-Example 3: The following is an example of a flow log record in which records were skipped during the capture window:
-1 5f67944957444bd6bb4fe3b367de8f3d 1d515d18-1b36-47dc-a983-bd6512aed4bd - - - - - - - 1431280876 1431280934 - SKIPDATA
-Table 4 describes the fields of a flow log record.
-
-Table 4 Log field descriptionField
- |
-Description
- |
-Example Value
- |
-
-
-version
- |
-Specifies the VPC flow log version.
- |
-1
- |
-
-project-id
- |
-Specifies the project ID.
- |
-5f67944957444bd6bb4fe3b367de8f3d
- |
-
-interface-id
- |
-Specifies the ID of the NIC for which the traffic is recorded.
- |
-1d515d18-1b36-47dc-a983-bd6512aed4bd
- |
-
-srcaddr
- |
-Specifies the source IP address.
- |
-x.x.x.x
- |
-
-dstaddr
- |
-Specifies the destination IP address.
- |
-x.x.x.x
- |
-
-srcport
- |
-Specifies the source port of the traffic.
- |
-38929
- |
-
-dstport
- |
-Specifies the destination port of the traffic.
- |
-53
- |
-
-protocol
- |
-Specifies the Internet Assigned Numbers Authority (IANA) protocol number of the traffic. For details, see Assigned Internet Protocol Numbers.
- |
-17
- |
-
-packets
- |
-Specifies the number of packets transferred during the capture window.
- |
-1
- |
-
-bytes
- |
-Specifies the number of bytes transferred during the capture window.
- |
-96
- |
-
-start
- |
-Specifies the time, in Unix seconds, of the start of the capture window.
- |
-1548752136
- |
-
-end
- |
-Specifies the time, in Unix seconds, of the end of the capture window.
- |
-1548752736
- |
-
-action
- |
-Specifies the action associated with the traffic:
-- ACCEPT: The recorded traffic was permitted by the security group or firewall.
- REJECT: The recorded traffic was not permitted by the firewall.
- |
-ACCEPT
- |
-
-log-status
- |
-Specifies the logging status of the VPC flow log:
-- OK: Data is logging normally to the chosen destinations.
- NODATA: There was no network traffic to or from the NIC during the capture window.
- SKIPDATA: Some flow log records were skipped during the capture window. This may be caused by an internal capacity constraint or an internal error.
- |
-OK
- |
-
-
-
-
-You can search for flow log records by keyword on the log stream details page on the LTS console.
-
-
-
-
-
diff --git a/docs/lts/umn/lts_01_0010.html b/docs/lts/umn/lts_01_0010.html
deleted file mode 100644
index b58fcb3c..00000000
--- a/docs/lts/umn/lts_01_0010.html
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
- Configuring CTS to Upload Traces to LTS
- ScenariosThis section describes how to enable trace analysis on the Cloud Trace Service (CTS) console to report traces to LTS, so you can query the traces on the LTS console.
-
- Operation processFigure 1 Flowchart
- Operations in Figure 1 are performed on different consoles:
- - CTS console: Enabling CTS and creating and configuring a tracker
- LTS console: Viewing traces reported by CTS
-
- Enabling CTSYou can perform the following operations to enable CTS and create a tracker.
- - Log in to the management console.
- In the upper left corner of the management console, select the target region and project.
- Click Service List and choose Management & Deployment > Cloud Trace Service.
- In the navigation pane on the left, choose Tracker.
- On the Tracker page, click Enable CTS.
- On the displayed page, set OBS Bucket.
Figure 2 Enabling CTS
- - Click OK.
After you enable CTS, tracker system is automatically created. All recorded traces are associated with the tracker.
-Currently, only one tracker can be created for each account.
-
-
- Configuring the TrackerFollow the directions below to enable transfer to LTS so traces can be reported to LTS:
- - On the Tracker page, click Configure in the Operation column.
The Configure Tracker page is displayed.
- - Enable Transfer to LTS.
Figure 3 Configuring a tracker
- A log group and a log stream will be created automatically for the reported traces on the LTS console.
-
- - Click Next to preview the created tracker.
- Click Configure.
-
- Viewing Logs in Real TimeYou can perform the following operations to view logs reported by CTS:
- - Click Service List and choose Management & Deployment > Log Tank Service.
- In the log group list, click
on the left of a log group name. The log stream list is displayed. - Click Log Stream to go to the log details and view real-time logs.
Figure 4 Viewing logs in real time
-Logs are reported to LTS once every five seconds. You may wait for at most five seconds before the logs are displayed.
-You can control log display by clicking Clear or Pause in the upper right corner.
-
-
-
-
-
-
diff --git a/docs/lts/umn/lts_01_0033.html b/docs/lts/umn/lts_01_0033.html
index 1a1b07ce..d46c2fec 100644
--- a/docs/lts/umn/lts_01_0033.html
+++ b/docs/lts/umn/lts_01_0033.html
@@ -8,9 +8,19 @@
-2023-6-30
+ | 2024-08-30
|
-Updated figures in Collecting Logs from CCE.
+ |
+ |
+
+2024-05-30
+ |
+- Added sections Managing Tags, Ingesting Logs to LTS Across IAM Accounts, Installing ICAgent (Extra-Region Hosts), Overview, Setting Indexes, Using LTS Search Syntax, "Phrase Search", Setting User-defined Log Time, Log Alarms, "One-off Transfer", Setting LTS Log Collection Quota, and Configuring Log Content Delimiters.
- Optimized sections Managing Host Groups and Transferring Logs to OBS.
+ |
+
+2023-6-30
+ |
+Updated figures in Ingesting CCE Application Logs to LTS.
|
2023-5-30
@@ -31,8 +41,8 @@
|
2022-11-30
|
- |
diff --git a/docs/lts/umn/lts_02_0013.html b/docs/lts/umn/lts_02_0013.html
index 48da007a..f8b19b0e 100644
--- a/docs/lts/umn/lts_02_0013.html
+++ b/docs/lts/umn/lts_02_0013.html
@@ -1,8 +1,8 @@
-Installing ICAgent
-ICAgent is a log collection tool for LTS. To use LTS to collect logs from hosts, you need to install ICAgent on the hosts.
- PrerequisitesEnsure that the time and time zone of your local browser are consistent with those of the host to install ICAgent. If they are inconsistent, errors may occur during log reporting.
+ Installing ICAgent (Intra-Region Hosts)
+ To use LTS to collect logs (such as host metrics, container metrics, node logs, container logs, and standard output logs) from intra-region hosts, you need to install ICAgent on the hosts. ICAgent is a log collection tool for LTS. It runs on hosts where logs need to be collected.
+ PrerequisitesBefore installing ICAgent, ensure that the time and time zone of your local browser are consistent with those of the host. If they are inconsistent, errors may occur during log reporting.
Installation MethodsThere are two methods to install ICAgent.
@@ -15,56 +15,86 @@
Initial installation
|
You can use this method to install ICAgent on a host that has no ICAgent installed.
+Run the ps -aux | grep icagent command on the host to check whether there is an ICAgent process. If no, the ICAgent has not been installed.
|
Inherited installation (supported only for Linux hosts)
|
-When ICAgent has already been installed on one host but needs to be installed on multiple hosts, you can use this method.
+ | When ICAgent has already been installed on one host but needs to be installed on multiple hosts, you can use this method.
|
-Initial Installation (Linux)- Log in to the LTS console and choose Host Management in the navigation pane on the left.
- Click Install ICAgent in the upper right corner.
Figure 1 Installing ICAgent
- - Set OS to Linux.
- Select an installation mode:
- Obtain AK/SK. For details, see How Do I Obtain an AK/SK Pair?
Obtain and use the AK/SK of a public account. Ensure that the public account and AK/SK will not be deleted or disabled. If the AK/SK is deleted, the ICAgent cannot report data to LTS.
+ Initial Installation (Linux)- Log in to the management console and choose Management & Deployment > Log Tank Service.
- In the navigation pane, choose Host Management.
- Click Install ICAgent in the upper right corner.
Before installing ICAgent, ensure that the time and time zone of your local browser are consistent with those of the host.
+
+
+Table 2 Installing ICAgentParameter
+ |
+Description
+ |
+Example
+ |
+
+
+Host
+ |
+Intra-Region Hosts is selected by default. Check whether the host whose logs need to be collected is in or out of the region.
+ |
+-
+ |
+
+OS
+ |
+Linux is selected by default.
+ |
+-
+ |
+
+Installation Mode
+ |
+
-- Click Copy Command to copy the ICAgent installation command.
- Log in as user root to the host which is deployed in the region same as that you are logged in to (for example, by using a remote login tool such as PuTTY) and run the copied command. If you have chosen Obtain AK/SK as the installation mode, enter the AK/SK pair as prompted.
- When the message ICAgent install success is displayed, ICAgent has been installed in the /opt/oss/servicemgr/ directory of the host. You can then view the ICAgent status on the Host Management > Hosts page of the LTS console.
- If the installation fails, uninstall ICAgent and reinstall it. If the reinstallation fails, contact technical support.
-
-
+ |
+-
+ |
+
+
+
-Initial Installation (Windows)- Log in to the LTS console and choose Host Management in the navigation pane on the left.
- Click Install ICAgent in the upper right corner.
- Set OS to Windows.

- - Download the ICAgent installation package to the host.
You can download it by clicking the name of the package or copying the download URL to the address bar of your browser.
- - Save the ICAgent installation package to a directory, for example, C:\ICAgent, and decompress the package.
- Enter the AK/SK pair to generate the ICAgent installation command. For details about how to obtain an AK/SK pair, see How Do I Obtain an AK/SK Pair?
If the AK/SK pair expires or is deleted, the ICAgent status may become abnormal. In this case, create an AK/SK pair and generate a new installation command. Log in to the host and run the command to reinstall ICAgent.
+ Figure 1 Installing ICAgent
+ - Click Copy Command to copy the ICAgent installation command.
- Log in as user root to the host which is deployed in the region same as that you are logged in to (by using a remote login tool such as PuTTY) and run the copied command. If you have chosen Obtain AK/SK as the installation mode, enter the AK/SK as prompted.
- When message ICAgent install success is displayed, ICAgent has been installed in the /opt/oss/servicemgr/ directory of the host.
- If the installation fails, uninstall ICAgent and then install it again.
- - Open the Command Prompt, go to the directory where the ICAgent installation package is decompressed, and run the copied command.
If the message Service icagent installed successfully is displayed, the installation is successful.
+ - Check wether the ICAgent status is Running by choosing Host Management > Hosts in the navigation pane of the LTS console.
+
+ Initial Installation (Windows)- Click Install ICAgent in the upper right corner.
- Set Host to Intra-Region Hosts.
- Set OS to Windows.
- You can download it to the local PC by clicking the name of the package or copying the download URL to the address bar of your browser.
- Save the ICAgent installation package to a directory on the target host, for example, C:\ICAgent, and decompress the package.
- Obtain an AK/SK pair. For details, see How Do I Obtain an AK/SK Pair?
- On the Install ICAgent page, click Copy Command to copy the ICAgent installation command to the local PC and replace the AK/SK in the command with the obtained one.
- Open the Command Prompt, go to the directory where the ICAgent installation package is decompressed, and run the copied command.
If the message Service icagent installed successfully is displayed, the installation is successful.
-
+ - Check wether the ICAgent status is Running by choosing Host Management > Hosts in the navigation pane of the LTS console.
- Inherited Installation (Linux)Let's assume that you need to install ICAgent on multiple hosts, and one of the hosts already has ICAgent installed. The ICAgent installation package, ICProbeAgent.tar.gz, is in the /opt/ICAgent/ directory. You can follow the directions below to install ICAgent on other hosts one by one.
- - Run the following command on the host where ICAgent has been installed, where x.x.x.x is the IP address of the host you want to install ICAgent on.
bash /opt/oss/servicemgr/ICAgent/bin/remoteInstall/remote_install.sh -ip x.x.x.x
- - Enter the password for user root of the host when prompted.
- If the Expect tool is installed on the host that has ICAgent installed, the ICAgent installation should be able to complete without prompting you for a password. Otherwise, enter the password as prompted.
- Ensure that user root can run SSH or SCP commands on the host where ICAgent has been installed to remotely communicate with the remote host to install ICAgent.
- When the message ICAgent install success is displayed, ICAgent has been installed in the /opt/oss/servicemgr/ directory of the host. You can then view the ICAgent status on the Host Management > Hosts page of the LTS console.
- If the installation fails, uninstall ICAgent and reinstall it. If reinstallation fails, contact technical support.
+ Inherited Installation (Linux)Assume that you need to install ICAgent on multiple hosts, and one of the hosts already has ICAgent installed. The ICAgent installation package, ICProbeAgent.tar.gz, is in the /opt/ICAgent/ directory. To install ICAgent on other hosts one by one:
+ - Run the following command on the host where ICAgent has been installed, where x.x.x.x is the IP address of the host you want to install ICAgent on.
bash /opt/oss/servicemgr/ICAgent/bin/remoteInstall/remote_install.sh -ip x.x.x.x
+ - Enter the password for user root of the host when prompted.
- If the Expect tool is installed on the host that has ICAgent installed, the ICAgent installation should be able to complete without prompting you for a password. Otherwise, enter the password as prompted.
- Ensure that user root can run SSH or SCP commands on the host where ICAgent has been installed to remotely communicate with the remote host to install ICAgent.
- When message ICAgent install success is displayed, ICAgent has been installed in the /opt/oss/servicemgr/ directory of the host. You can then view the ICAgent status by choosing Host Management > Hosts in the navigation pane of the LTS console.
- If ICAgent install success is not displayed, the installation fails. Uninstall ICAgent and install it again.
- Batch Inherited Installation (Linux)Let's assume that you need to install ICAgent on multiple hosts, and one of the hosts already has ICAgent installed. The ICAgent installation package, ICProbeAgent.tar.gz, is in the /opt/ICAgent/ directory. You can follow the directions below to install ICAgent on other hosts in batches.
- - The hosts must all belong to the same Virtual Private Cloud (VPC) and be on the same subnet.
- Python 3.* is required for batch installation. If you are prompted that Python cannot be found during ICAgent installation, install Python of a proper version and try again.
-
+ Batch Inherited Installation (Linux)Assume that you need to install ICAgent on multiple hosts, and one of the hosts already has ICAgent installed. The ICAgent installation package, ICProbeAgent.tar.gz, is in the /opt/ICAgent/ directory. In this case, you can follow the directions below to install ICAgent on other hosts in batches.
+ - The hosts must all belong to the same VPC and be on the same subnet.
- Python 3.* is required for batch installation. If you are prompted that Python cannot be found during ICAgent installation, install Python of a proper version on the host and try again.
Prerequisites
- The IP addresses and passwords of all hosts to install ICAgent have been collected, sorted in the iplist.cfg file, and uploaded to the /opt/ICAgent/ directory on the host that has ICAgent installed. Each IP address and password in the iplist.cfg file must be separated by a space, as shown in the following example:
+ The IP addresses and root's passwords of all hosts to install ICAgent have been collected, sorted in the iplist.cfg file, and uploaded to the /opt/ICAgent/ directory on the host that has ICAgent installed. An IP address and the password of a host's user root in the iplist.cfg file must be separated by a space. Examples:
192.168.0.109 Password (Replace the IP address and password with the actual ones)
192.168.0.39 Password (Replace the IP address and password with the actual ones)
- - Because the iplist.cfg file contains sensitive information, you are advised to clear it after using it.
+ - The iplist.cfg file contains sensitive information. You are advised to clear it after using it.
- If all hosts share a password, list only IP addresses in the iplist.cfg file and enter the password manually during execution. If one of the hosts uses a different password, type the password behind its IP address.
Procedure
- - Run the following command on the host that has ICAgent installed:
bash /opt/oss/servicemgr/ICAgent/bin/remoteInstall/remote_install.sh -batchModeConfig /opt/ICAgent/iplist.cfg
-Enter the default password for user root of the hosts to install ICAgent. If the passwords of all hosts have been configured in the iplist.cfg file, press Enter to skip this step.
+- Run the following command on the host that has ICAgent installed:
bash /opt/oss/servicemgr/ICAgent/bin/remoteInstall/remote_install.sh -batchModeConfig /opt/ICAgent/iplist.cfg
+Enter the default password for user root of the hosts to install ICAgent. If the passwords of all hosts have been configured in the iplist.cfg file, press Enter to skip this step.
batch install begin
Please input default passwd:
send cmd to 192.168.0.109
@@ -75,8 +105,8 @@ send cmd to 192.168.0.39
End of install agent: 192.168.0.39
End of install agent: 192.168.0.109
All hosts install icagent finish.
-If the message All hosts install icagent finish. is displayed, ICAgent has been installed on all the hosts listed in the configuration file.
- - You can then view the ICAgent status on the Host Management > Hosts page of the LTS console.
+Wait for a while. When message All hosts install icagent finish. is displayed, ICAgent has been installed on all the hosts listed in the configuration file.
+ - Check the ICAgent status by choosing Host Management > Hosts in the navigation pane of the LTS console.
diff --git a/docs/lts/umn/lts_02_0014.html b/docs/lts/umn/lts_02_0014.html
index c46038b9..dca4c44b 100644
--- a/docs/lts/umn/lts_02_0014.html
+++ b/docs/lts/umn/lts_02_0014.html
@@ -1,18 +1,110 @@
- Upgrading ICAgent
- To deliver a better collection experience, LTS regularly upgrades ICAgent. When LTS prompts you that a new ICAgent version is available, you can follow the directions here to obtain the latest version.
- Linux hosts support ICAgent upgrade on the Host Management page of the LTS console.
+ Managing ICAgent
+ After ICAgent is installed, you can upgrade and uninstall it, and view its status.
+ Upgrading ICAgentTo deliver a better collection experience, LTS regularly upgrades ICAgent. When LTS prompts you that a new ICAgent version is available, you can follow the directions here to obtain the latest version.
+ Linux hosts support ICAgent upgrade on the Host Management page of the LTS console.
- Procedure- Log in to the LTS console and choose Host Management in the navigation pane on the left.
- On the Host Management page, click the Hosts tab.
- Select Hosts. Select one or more hosts where ICAgent is to be upgraded, and click Upgrade ICAgent.
Select CCE Cluster. In the drop-down list on the right, select the cluster whose ICAgent is to be upgraded, and click Upgrade ICAgent.
-Figure 1 Upgrading ICAgent
- - If you create a CCE cluster for the first time, ICAgents will be installed on hosts in the cluster by default, and logs will be reported to AOM. Output to AOM is enabled by default. To report logs to LTS, disable Output to AOM before upgrading ICAgents. You are advised to choose Log Ingestion > Cloud Service > Cloud Container Engine (CCE) to collect container data and output it to LTS instead of AOM.
- CCE cluster ID (ClusterID): Each cluster has a fixed ID.
- When ICAgent is upgraded, LTS creates log groups and host groups for your CCE cluster. The name of the log group and host group is k8s-log-{ClusterID}. You can create an ingestion configuration (Cloud Services > Cloud Container Engine (CCE)) to add logs of the current CCE cluster to the log group.
- If the ICAgent is not installed on hosts in a cluster or the ICAgent version is too early, click Upgrade ICAgent to install the ICAgent on all hosts in the cluster.
+ - Log in to the management console and choose Management & Deployment > Log Tank Service.
- Choose Host Management in the navigation pane and click the Hosts tab.
- Select Intra-Region Hosts or Extra-Region Hosts. When the system prompts you that a new ICAgent version is available, select one or more check boxes of hosts where ICAgent is to be upgraded, and click Upgrade ICAgent.
- Click the CCE Cluster tab. Search for and select the cluster whose ICAgent is to be upgraded, and click Upgrade ICAgent.
- You need to create a CCE cluster before you can collect container standards and send them to AOM.
- To disable the function of exporting container standards to AOM, you need to have ICAgent 5.12.133 or later.
- If you create a CCE cluster for the first time, ICAgent will be installed on hosts in the cluster by default, and logs will be reported to AOM. Output to AOM is enabled by default. To report logs to LTS, disable Output to AOM before upgrading ICAgent. You are advised to choose Log Ingestion > Cloud Service > Cloud Container Engine (CCE) to collect container data and output it to LTS instead of AOM.
- CCE cluster ID (ClusterID): Each cluster has a fixed ID.
- When ICAgent is upgraded, LTS creates log groups and host groups for your CCE cluster. The name of the log group and host group is k8s-log-{ClusterID}. You can create an ingestion configuration (Cloud Services > Cloud Container Engine (CCE)) to add logs of the current CCE cluster to the log group.
- If the ICAgent is not installed on hosts in a cluster or the ICAgent version is too early, click Upgrade ICAgent to install the ICAgent on all hosts in the cluster.
-
- - In the displayed dialog box, click OK.
The upgrade begins. This process takes about a minute. When the ICAgent status changes from Upgrading to Running, the ICAgent upgrade has completed.
+ - In the displayed dialog box, click OK.
The upgrade begins. This process takes about a minute. When the ICAgent status changes from Upgrading to Running, the ICAgent upgrade has completed.
If the ICAgent is abnormal after the upgrade or if the upgrade fails, log in to the host and run the installation command. ICAgent can be re-installed on top of itself.
+
+
+ Uninstalling ICAgentIf ICAgent is uninstalled from a host, log collection will be affected. Exercise caution when performing this operation.
+ Only ICAgent installed on Linux hosts can be uninstalled from the Host Management page of the LTS console. To uninstall ICAgent from a Windows host, go to \ICProbeAgent\bin\manual\win in the directory where the ICAgent installation package was decompressed, and double-click the script named uninstall.bat. If message ICAgent uninstall success is displayed, the uninstallation is successful.
+ Uninstalling ICAgent does not delete the installation files. You need to delete them manually if necessary.
+
+ You can uninstall ICAgent using either of the following methods:
+ - Uninstalling ICAgent on the console: applies to the scenario where ICAgent has been successfully installed.
- Choose Host Management in the navigation pane and click the Hosts tab.
- Select one or more hosts where ICAgent is to be uninstalled and click Uninstall ICAgent.
- In the displayed dialog box, click OK.
The uninstallation begins. This process takes about a minute.
+The hosts with ICAgent uninstalled will be removed from the host list.
+ To reinstall ICAgent, wait for 5 minutes after it is uninstalled. Otherwise, the ICAgent may be automatically uninstalled again.
+
+ - Logging in to the host to uninstall ICAgent: applies to the scenario where ICAgent fails to be installed.
- Log in to a host where ICAgent is to be uninstalled as user root.
- Run the following command:
bash /opt/oss/servicemgr/ICAgent/bin/manual/uninstall.sh
+If the message ICAgent uninstall success is displayed, the uninstallation has completed.
+
+ - Remotely uninstalling ICAgent: applies to the scenario where the ICAgent has been successfully installed and needs to be remotely uninstalled.
You can uninstall ICAgent on one host remotely from another host.
+- Run the following command on the host where ICAgent has been installed. x.x.x.x indicates the IP address of the host you want to uninstall ICAgent from.
bash /opt/oss/servicemgr/ICAgent/bin/remoteUninstall/remote_uninstall.sh -ip x.x.x.x
+ - Enter the password for user root of the host when prompted.
- If the Expect tool is installed on the host that has ICAgent installed, the ICAgent uninstallation should be able to complete without prompting you for a password. Otherwise, enter the password as prompted.
- Ensure that user root can run SSH or SCP commands on the host where ICAgent has been installed to communicate with the remote host.
- If the message ICAgent uninstall success is displayed, the uninstallation has completed.
+
+
+ - Batch uninstalling ICAgent: applies to the scenario where the ICAgent has been installed and needs to be uninstalled in batches.
If ICAgent has been installed on a host and the ICAgent installation package ICProbeAgent.tar.gz is in the /opt/ICAgent/ directory of the host, you can use this method to uninstall ICAgent from multiple hosts at once.
+ The hosts must all belong to the same VPC and be on the same subnet.
+
+Prerequisites
+The IP addresses and passwords of all hosts to uninstall ICAgent have been collected, sorted in the iplist.cfg file, and uploaded to the /opt/ICAgent/ directory on the host that has ICAgent installed. Each IP address and password in the iplist.cfg file must be separated by a space. Examples:
+192.168.0.109 Password (Replace the IP address and password with the actual ones)
+192.168.0.39 Password (Replace the IP address and password with the actual ones)
+ - The iplist.cfg file contains sensitive information. You are advised to clear it after using it.
+ - If all hosts share a password, list only IP addresses in the iplist.cfg file and enter the password manually during execution. If one of the hosts uses a different password, type the password behind its IP address.
+
+- Run the following command on the host that has ICAgent installed:
bash /opt/oss/servicemgr/ICAgent/bin/remoteUninstall/remote_uninstall.sh -batchModeConfig /opt/ICAgent/iplist.cfg
+Enter the default password for user root of the hosts to uninstall ICAgent. If the passwords of all hosts have been configured in the iplist.cfg file, press Enter to skip this step.
+batch uninstall begin
+Please input default passwd:
+send cmd to 192.168.0.109
+send cmd to 192.168.0.39
+2 tasks running, please wait...
+End of uninstall agent: 192.168.0.109
+End of uninstall agent: 192.168.0.39
+All hosts uninstall icagent finish.
+If message All hosts uninstall icagent finish. is displayed, the batch uninstallation has completed.
+ - Choose Host Management > Hosts in the navigation pane of the LTS console to view the ICAgent status.
+
+
+ Checking the ICAgent StatusOn the Host Management page, click the Hosts tab. Check the ICAgent status of the target host. The following table lists the ICAgent statuses.
+
+ Table 1 ICAgent statusesStatus
+ |
+Description
+ |
+
+
+Running
+ |
+ICAgent is running properly.
+ |
+
+Uninstalled
+ |
+ICAgent is not installed.
+ |
+
+Installing
+ |
+ICAgent is being installed. This process takes about one minute.
+ |
+
+Installation failed
+ |
+ICAgent installation failed.
+ |
+
+Upgrading
+ |
+ICAgent is being upgraded. This process takes about one minute.
+ |
+
+Upgrade failed
+ |
+ICAgent upgrade failed.
+ |
+
+Offline
+ |
+ICAgent is abnormal because the AK/SK pair is incorrect. Obtain the correct AK/SK pair and install ICAgent again.
+ |
+
+Faulty
+ |
+ICAgent is faulty. Contact technical support.
+ |
+
+
+
+
diff --git a/docs/lts/umn/lts_02_0015.html b/docs/lts/umn/lts_02_0015.html
deleted file mode 100644
index a478bf19..00000000
--- a/docs/lts/umn/lts_02_0015.html
+++ /dev/null
@@ -1,56 +0,0 @@
-
-
- Uninstalling ICAgent
- If ICAgent is uninstalled from a host, log collection will be affected. Exercise caution when performing this operation.
- Only ICAgent installed on Linux hosts can be uninstalled from the Host Management page of the LTS console. To uninstall ICAgent from a Windows host, go to \ICProbeAgent\bin\manual\win in the directory where the ICAgent installation package was decompressed, and double-click the script named uninstall.bat. If the message ICAgent uninstall success is displayed, the uninstallation was successful.
- Uninstalling ICAgent does not delete the installation files. You need to delete them manually if necessary.
-
- There are a number of ways to uninstall ICAgent:
-
- Uninstalling ICAgent on the Console- Log in to the LTS console and choose Host Management in the navigation pane on the left.
- Click the Hosts tab.
- Select one or more hosts where ICAgent is to be uninstalled and click Uninstall ICAgent.
- In the displayed dialog box, click OK.
The uninstallation begins. This process takes about a minute.
-The ICAgent uninstalled will be removed from the host list.
- To reinstall ICAgent, wait for 5 minutes after the uninstallation completes, or the reinstalled ICAgent may be unintentionally uninstalled again.
-
-
-
- Uninstalling ICAgent on a Host- Log in to a host where ICAgent is to be uninstalled as user root.
- Run the following command:
bash /opt/oss/servicemgr/ICAgent/bin/manual/uninstall.sh;
-If the message ICAgent uninstall success is displayed, the uninstallation has completed.
-
-
- Remotely Uninstalling ICAgentYou can uninstall ICAgent on one host remotely from another host.
- - Run the following command on the host where ICAgent has been installed, x.x.x.x is the IP address of the host you want to uninstall ICAgent from.
bash /opt/oss/servicemgr/ICAgent/bin/remoteUninstall/remote_uninstall.sh -ip x.x.x.x
- - Enter the password for user root of the host when prompted.
- If the Expect tool is installed on the host that has ICAgent installed, the ICAgent uninstallation should be able to complete without prompting you for a password. Otherwise, enter the password as prompted.
- Ensure that user root can run SSH or SCP commands on the host where ICAgent has been installed to communicate with the remote host to uninstall ICAgent.
- If the message ICAgent uninstall success is displayed, the uninstallation has completed.
-
-
-
- Batch Uninstalling ICAgentIf ICAgent has been installed on a host and the ICAgent installation package ICProbeAgent.tar.gz is in the /opt/ICAgent/ directory of the host, you can use this method to uninstall ICAgent from multiple hosts at once.
- The hosts must all belong to the same Virtual Private Cloud (VPC) and be on the same subnet.
-
- Prerequisites
- The IP addresses and passwords of all hosts to uninstall ICAgent have been collected, sorted in the iplist.cfg file, and uploaded to the /opt/ICAgent/ directory on the host that has ICAgent installed. Each IP address and password in the iplist.cfg file must be separated by a space, as shown in the following example:
- 192.168.0.109 Password (Replace the IP address and password with the actual ones)
- 192.168.0.39 Password (Replace the IP address and password with the actual ones)
- - Because the iplist.cfg file contains sensitive information, you are advised to clear it after using it.
- - If all hosts share a password, list only IP addresses in the iplist.cfg file and enter the password during execution. If one of the hosts uses a different password, type the password behind its IP address.
-
- Procedure
- - Run the following command on the host that has ICAgent installed:
bash /opt/oss/servicemgr/ICAgent/bin/remoteUninstall/remote_uninstall.sh -batchModeConfig /opt/ICAgent/iplist.cfg
-Enter the default password for user root of the hosts to uninstall ICAgent. If the passwords of all hosts have been configured in the iplist.cfg file, press Enter to skip this step.
-batch uninstall begin
-Please input default passwd:
-send cmd to 192.168.0.109
-send cmd to 192.168.0.39
-2 tasks running, please wait...
-End of uninstall agent: 192.168.0.109
-End of uninstall agent: 192.168.0.39
-All hosts uninstall icagent finish.
-If the message All hosts uninstall icagent finish. is displayed, the batch uninstallation has completed.
- - Choose Host Management > Hosts on the LTS console to view the ICAgent status.
-
-
-
-
diff --git a/docs/lts/umn/lts_02_0030.html b/docs/lts/umn/lts_02_0030.html
index 50dda95d..584bbac6 100644
--- a/docs/lts/umn/lts_02_0030.html
+++ b/docs/lts/umn/lts_02_0030.html
@@ -4,7 +4,9 @@
diff --git a/docs/lts/umn/lts_02_0828.html b/docs/lts/umn/lts_02_0828.html
new file mode 100644
index 00000000..38bb2626
--- /dev/null
+++ b/docs/lts/umn/lts_02_0828.html
@@ -0,0 +1,164 @@
+
+
+ Installing ICAgent (Extra-Region Hosts)
+ ICAgent is a log collection tool for LTS. To use LTS to collect logs from extra-region hosts, you need to install ICAgent on the hosts.
+ PrerequisitesBefore installing ICAgent, ensure that the time and time zone of your local browser are consistent with those of the host. If they are inconsistent, errors may occur during log reporting.
+
+ Installation MethodsThere are two methods to install ICAgent.
+
+ Table 1 Installation methodsMethod
+ |
+Scenario
+ |
+
+
+Initial installation
+ |
+You can use this method to install ICAgent on a host that has no ICAgent installed.
+ |
+
+Inherited installation (supported only for Linux hosts)
+ |
+When ICAgent has already been installed on one host but needs to be installed on multiple hosts, you can use this method.
+ |
+
+
+
+
+
+ Initial Installation (Linux)Before installing ICAgent on a host not in this region, apply for an ECS as a jump server on the ECS console. For details, see Using Multiple Jump Servers.
+ The minimum specifications for the ECS are 1 vCPU and 1 GB of memory. The recommended specifications are 2 vCPUs and 4 GB of memory. You are advised to use an image of CentOS 6.5 64bit or later version.
+
+ - Log in to the management console and choose Management & Deployment > Log Tank Service.
- In the navigation pane, choose Host Management.
- Set Host to Extra-Region Hosts.
- Set OS to Linux.
- Set Network Connectivity to Private line. When the network is connected via a private line, hosts in other IDCs are disconnected from LTS backend by default and a network connectivity solution is required. You are advised to select VPCEP.
Private line: Extra-region hosts connect to LTS in the current region through a jump server or VPC Endpoint (VPCEP), offering greater security and stability. In this scenario, extra-region hosts cannot communicate with LTS in the current region by default, and ICAgent installed on these hosts cannot directly access the network segment used by LTS in the current region to report logs. Therefore, you need to configure a network connection solution to use a jump server or VPCEP to connect to the LTS backend and forward data to LTS. - Jump server: functions as a data forwarder and forwards the data collected by ICAgent from extra-region hosts to LTS. This solution is suitable for tests or scenarios with low log traffic. VPCEP is recommended for scenarios with high log traffic.
- VPCEP: provides private channels to connect your VPC to LTS in the current region, enabling resources in the VPC to access VPC endpoint services without the need for EIPs. This solution reduces the risks of data transmission on public networks and improves the transmission security and efficiency.
+
+
+ - If you set LTS Backend Connection to VPCEP, enter the VPCEP domain name and go to 8.
With the assistance of network engineers, configure DNS domain name resolution rules on other clouds to resolve VPCEP domain names to specified IP addresses.
+Then, copy the ping command displayed on this page and run it on the target host whose logs are to be collected. A successful ping test indicates that the network configuration is correct.
+ - Enable forwarding ports on the jump server. This step is mandatory when LTS Backend Connection is set to Jump server.
- Apply for an ECS in the current region as a jump server.
- Add security group rules for the jump server and enable the corresponding inbound ports to ensure data connectivity between the extra-region hosts and the jump server.
- On the ECS console, click the ECS name to access the details page, and click the Security Groups tab. The security group list is displayed.
- Click a security group name and click Modify Security Group Rule.
- On the security group details page, click the Inbound Rules tab and then click Add Rule. On the page displayed, add a security group rule based on Table 2.
+
Table 2 Security group ruleDirection
+ |
+Protocol
+ |
+Port
+ |
+Description
+ |
+
+
+Inbound
+ |
+TCP
+ |
+8149, 8102, 8923, 30200, 30201, and 80
+ |
+Ports used by ICAgent to send data to the jump server, ensuring data connectivity between VMs in other regions and the jump server.
+ |
+
+
+
+
+
+ - Enter the private IP address of the jump server and generate an SSH tunneling command.
Figure 1 Entering the private IP address of the jump server
+ The private IP address of the jump server refers to the internal IP address of the VPC where the jump server is located.
+
+ - Click Copy Command.
- Log in to the jump server as user root and run the SSH tunneling command:
ssh -f -N -L {Jump server IP address}:8149:{ELB IP address}:8149 -L {Jump server IP address}:8102:{ELB IP address}:8102 -L {Jump server IP address}:8923:{ELB IP address}:8923 -L {Jump server IP address}:30200:{ELB IP address}:30200 -L {Jump server IP address}:30201:{ELB IP address}:30201 -L {Jump server IP address}:80:icagent-{Region}.{OBS domain name}:80 {Jump server IP address}
+Enter the password of user root as prompted.
+ - Run the netstat -lnp | grep ssh command to check whether the corresponding TCP ports are being listened to. If the command output similar to Figure 2 is returned, the ports are open.
Figure 2 Open TCP ports
+ If the jump server powers off and restarts, run the preceding command again.
+
+ - Obtain an AK/SK pair and specify DC and Connection IP.
- DC: Specify a name for the data center of the host so it is easier to find the host.
- Connection IP: For EIP connection, use the EIP of the jump server. For VPC peer connection, use the internal IP address of the VPC where the jump server locates.
+
+
+ - Copy the ICAgent installation command.
- Log in as user root to the host which is deployed in the region same as that you are logged in to (by using a remote login tool such as PuTTY) and run the copied command.
- When message ICAgent install success is displayed, ICAgent has been installed in the /opt/oss/servicemgr/ directory of the host. You can then view the ICAgent status by choosing Host Management > Hosts in the navigation pane of the LTS console.
- If the installation fails, uninstall ICAgent and reinstall it. If the reinstallation fails, contact technical support.
+
+
+
+ Initial Installation (Windows)Before installing ICAgent on a host not in this region, apply for a Linux ECS as a jump server on the ECS console. For details, see Using Multiple Jump Servers.
+ The minimum specifications for the ECS are 1 vCPU and 1 GB of memory. The recommended specifications are 2 vCPUs and 4 GB of memory. You are advised to use an image of CentOS 6.5 64bit or later version.
+
+ - Click Install ICAgent in the upper right corner.
- Set Host to Extra-Region Hosts.
- Set OS to Windows.
- Enable forwarding ports on the jump server.
- Apply for a Linux ECS in the current region as a jump server.
- Modify the security group rule used by the jump server.
- On the ECS details page, click the Security Groups tab.
- Click a security group name and click Modify Security Group Rule.
- On the security group details page, click the Inbound Rules tab and then click Add Rule. On the page displayed, add a security group rule based on Table 3.
+
Table 3 Security group ruleDirection
+ |
+Protocol
+ |
+Port
+ |
+Description
+ |
+
+
+Inbound
+ |
+TCP
+ |
+8149, 8102, 8923, 30200, 30201, and 80
+ |
+ICAgent will send data to the jump server through the listed ports.
+ |
+
+
+
+
+
+ - Enter the private IP address of the jump server and generate an SSH tunneling command.
The private IP address of the jump server refers to the internal IP address of the VPC where the jump server is located.
+
+ - Click Copy Command.
- Log in to the jump server as user root and run the SSH tunneling command:
ssh -f -N -L {Jump server IP address}:8149:{ELB IP address}:8149 -L {Jump server IP address}:8102:{ELB IP address}:8102 -L {Jump server IP address}:8923:{ELB IP address}:8923 -L {Jump server IP address}:30200:{ELB IP address}:30200 -L {Jump server IP address}:30201:{ELB IP address}:30201 -L {Jump server IP address}:80:icagent-{Region}.{OBS domain name}:80 {Jump server IP address}
+Enter the password of user root as prompted.
+ - Run the netstat -lnp | grep ssh command to check whether the corresponding TCP ports are being listened to. If the command output similar to Figure 3 is returned, the ports are open.
Figure 3 Open TCP ports
+ If the jump server powers off and restarts, run the preceding command again.
+
+
+ - Download the ICAgent installation package to the local PC as prompted.
- Save the ICAgent installation package to a directory on the Windows host, for example, C:\ICAgent, and decompress the package.
- Obtain an AK/SK.
- Generate and copy the installation command.
- Enter the connection IP in the text box and replace the AK/SK pair to generate the installation command.
Connection IP: For EIP connection, use the EIP of the jump server. For VPC peer connection, use the internal IP address of the VPC where the jump server locates.
+
+ - Click Copy Command to copy the ICAgent installation command.
+ - Open the Command Prompt, go to the directory where the ICAgent installation package is decompressed, and run the copied command.
- If the message Service icagent installed successfully is displayed, the installation is successful. You can then view the ICAgent status by choosing Host Management > Hosts in the navigation pane of the LTS console.
- If the installation fails, uninstall ICAgent and reinstall it. If the reinstallation fails, contact technical support.
+
+
+
+ Using Multiple Jump Servers You can use multiple jump servers to prevent the risk of single point of failures and improve access reliability.
+
+ - Create a Linux ECS that as a jump server.
Configure the CPU and memory based on the service requirements. The recommended specifications are 2 vCPUs and 4 GB of memory, or above.
+
+ - Log in to the jump server as use root and use the internal IP address of the jump server to create an SSH tunnel.
- On the ECS console, locate the jump server and obtain its private IP address.
- On the LTS console, choose Host Management in the navigation pane, and click Install ICAgent in the upper right corner. In the dialog box displayed, select Linux for OS, select Extra-Region Hosts for Host, and enter the private IP address to generate the SSH tunneling command. Log in to the jump server and run the command to create an SSH tunnel.
+
- If there are multiple jump servers, repeat 2 and add them to the same VPC. When creating an ECS, select the same VPC for Network.
- Create a load balancer. When creating the load balancer, you should:
- Select the same VPC as that of the jump servers.
- Create an EIP for connecting to the jump servers.
- Apply for the bandwidth based on the service requirements.
+ - Add listeners for TCP ports 30200, 30201, 8149, 8923, and 8102.
- Add all jump servers to the backend server group.
+
+ Inherited Installation (Linux)Assume that you need to install ICAgent on multiple hosts, and one of the hosts already has ICAgent installed. The ICAgent installation package, ICProbeAgent.tar.gz, is in the /opt/ICAgent/ directory. To install ICAgent on other hosts one by one:
+ - Run the following command on the host where ICAgent has been installed, where x.x.x.x is the IP address of the host you want to install ICAgent on.
bash /opt/oss/servicemgr/ICAgent/bin/remoteInstall/remote_install.sh -ip x.x.x.x
+ - Enter the password for user root of the host when prompted.
- If the Expect tool is installed on the host that has ICAgent installed, the ICAgent installation should be able to complete without prompting you for a password. Otherwise, enter the password as prompted.
- Ensure that user root can run SSH or SCP commands on the host where ICAgent has been installed to remotely communicate with the remote host to install ICAgent.
- When message ICAgent install success is displayed, ICAgent has been installed in the /opt/oss/servicemgr/ directory of the host. You can then view the ICAgent status by choosing Host Management > Hosts in the navigation pane of the LTS console.
- If the installation fails, uninstall ICAgent and reinstall it. If the reinstallation fails, contact technical support.
+
+
+
+ Batch Inherited Installation (Linux)Assume that you need to install ICAgent on multiple hosts, and one of the hosts already has ICAgent installed. The ICAgent installation package, ICProbeAgent.tar.gz, is in the /opt/ICAgent/ directory. In this case, you can follow the directions below to install ICAgent on other hosts in batches.
+ - The hosts must all belong to the same VPC and be on the same subnet.
+
+
+ Prerequisites
+ The IP addresses and passwords of all hosts to install ICAgent have been collected, sorted in the iplist.cfg file, and uploaded to the /opt/ICAgent/ directory on the host that has ICAgent installed. Each IP address and password in the iplist.cfg file must be separated by a space. Examples:
+ 192.168.0.109 Password (Replace the IP address and password with the actual ones)
+ 192.168.0.39 Password (Replace the IP address and password with the actual ones)
+ - The iplist.cfg file contains sensitive information. You are advised to clear it after using it.
+ - If all hosts share a password, list only IP addresses in the iplist.cfg file and enter the password manually during execution. If one of the hosts uses a different password, type the password behind its IP address.
+
+ Procedure
+ - Run the following command on the host that has ICAgent installed:
bash /opt/oss/servicemgr/ICAgent/bin/remoteInstall/remote_install.sh -batchModeConfig /opt/ICAgent/iplist.cfg
+Enter the default password for user root of the hosts to install ICAgent. If the passwords of all hosts have been configured in the iplist.cfg file, press Enter to skip this step.
+batch install begin
+Please input default passwd:
+send cmd to 192.168.0.109
+send cmd to 192.168.0.39
+2 tasks running, please wait...
+2 tasks running, please wait...
+2 tasks running, please wait...
+End of install agent: 192.168.0.39
+End of install agent: 192.168.0.109
+All hosts install icagent finish.
+If the message All hosts install icagent finish. is displayed, ICAgent has been installed on all the hosts listed in the configuration file.
+ - Check the ICAgent status by choosing Host Management > Hosts in the navigation pane of the LTS console.
+
+
+
diff --git a/docs/lts/umn/lts_02_0926.html b/docs/lts/umn/lts_02_0926.html
new file mode 100644
index 00000000..bb4a62e8
--- /dev/null
+++ b/docs/lts/umn/lts_02_0926.html
@@ -0,0 +1,89 @@
+
+
+ Creating an Alarm Action Rule
+ LTS allows you to customize alarm action rules. You can create an alarm action rule to associate an SMN topic with a message template. You can also customize notification content when creating a message template.
+ Prerequisites- A topic has been created.
- A topic policy has been configured.
- A subscriber has been added to the topic. A subscriber is the recipient of the notification, for example, an email or SMS message receiver.
+
+ PrecautionYou can create a maximum of 1,000 alarm action rules. If this number has been reached, delete unnecessary rules.
+
+ Creating an Alarm Action Rule- Log in to the management console and choose Management & Deployment > Log Tank Service.
- Choose Alarms in the navigation pane.
- Click the Alarm Action Rules tab.
- Click Create. Set parameters such as the action rule name and action rule configuration.
+ Table 1 Parameters for configuring an alarm action ruleParameter
+ |
+Description
+ |
+
+
+Action Rule
+ |
+Enter 1 to 64 characters. Only digits, letters, underscores (_), and hyphens (-) are allowed. Do not start or end with an underscore or hyphen.
+ |
+
+Enterprise Project
+ |
+Select an enterprise project.
+This parameter is displayed only when the enterprise project function is enabled for the current account.
+ |
+
+Description
+ |
+Enter a description for the rule. Up to 1,024 characters are allowed.
+ |
+
+Topic
+ |
+SMN topic. Select your desired topic from the drop-down list.
+If there is no topic you want to select, create one on the SMN console.
+ |
+
+Message Template
+ |
+Notification message template. Select your desired template from the drop-down list.
+If there is no message template you want to select, create one by referring to Creating a Message Template on the LTS Console.
+ |
+
+
+
+
+
- Click OK.
+
+ More OperationsAfter an alarm action rule is created, you can perform operations described in Table 2.
+
+ Table 2 Related operationsOperation
+ |
+Description
+ |
+
+
+Modifying an alarm action rule
+ |
+Click Modify in the Operation column.
+ |
+
+Exporting an alarm action rule
+ |
+Select one or more alarm action rules and click Export. If no alarm action rule is selected, clicking Export will export all alarm action rules.
+ |
+
+Deleting an alarm action rule
+ |
+- To delete a single rule, click Delete in the Operation column in the row that contains the rule, and then click Yes on the displayed page.
- To delete one or more rules, select them, click Delete above the rule list, and then click Yes on the displayed page.
NOTE: Before deleting an alarm action rule, you need to delete the alarm rule bound to the action rule.
+
+
+ |
+
+Searching for an alarm action rule
+ |
+Enter a rule name in the search box in the upper right corner and click .
+ |
+
+
+
+
+
+
+
+
diff --git a/docs/lts/umn/lts_02_1033.html b/docs/lts/umn/lts_02_1033.html
index f65548ae..ba8aa54e 100644
--- a/docs/lts/umn/lts_02_1033.html
+++ b/docs/lts/umn/lts_02_1033.html
@@ -1,97 +1,122 @@
Managing Host Groups
- Host groups allow you to configure host log ingestion efficiently. You can sort multiple hosts to a host group and associate the host group with log ingestion configurations. The ingestion configurations will be applied to all the hosts in the host group, saving you the trouble of configuring the hosts individually.
+ Host groups allow you to configure host log ingestion efficiently. You can add multiple hosts to a host group and associate the host group with log ingestion configurations. The ingestion configurations will then be applied to all the hosts in the host group.
- When there is a new host, simply add it to a host group and the host will automatically inherit the log ingestion configurations associated with the host group.
- You can also use host groups to modify the log collection paths for multiple hosts at one go.
- Creating a Host Group (IP Address)- Log in to the LTS console, and choose Host Management in the navigation pane on the left. On the displayed page, click Create Host Group in the upper right corner.
- In the displayed slide-out panel, enter a host group name and select a host OS (Linux).
Figure 1 Creating an IP address host group
-
- - In the host list, select one or more hosts to add to the group and click OK.
- You can filter hosts by host name or host IP address. You can also click
and enter multiple host IP addresses in the displayed search box to search for matches. - If your desired hosts are not in the list, click Install ICAgent. On the displayed page, install ICAgent on the hosts as prompted. For details, see Installing ICAgent.
-
-
- Creating a Host Group (Custom Identifier)- Log in to the LTS console, and choose Host Management in the navigation pane on the left. On the displayed page, click Create Host Group in the upper right corner.
- On the displayed Create Host Group page, enter a host group name in the Host Group field and set Host Group OS to Custom Identifier.
Figure 2 Creating a custom identifier host group
-
- - A host group with a custom ID supports only Linux hosts.
- You can click Learn about the rules for filling in the collection path to learn how to configure paths.
+ You can create host groups of the IP address and custom identifier types.
+ - Creating a Host Group (IP Address): Select hosts of the IP address type and add them to the host group.
- Creating a Host Group (Custom Identifier): You need to create identifiers for each host group and host. Hosts with an identifier will automatically be included in the corresponding host group sharing that identifier.
Host groups with custom identifiers are suitable for the following scenarios:
+ - In custom network environments like VPCs, potential IP address conflicts among hosts may impede ICAgent management in LTS. Using custom identifiers can resolve this issue.
- Multiple servers using the same custom identifier enable auto scaling of host groups. Simply assign a custom identifier for a new host; LTS will then automatically identify the host and add it to corresponding host group with the same identifier.
+
+ Creating a Host Group (IP Address)- Log in to the management console and choose Management & Deployment > Log Tank Service.
- In the navigation pane, choose Host Management.
- Click Create Host Group in the upper right corner.
- In the displayed slide-out panel, enter a host group name, select IP for Host Group Type, and select a host OS (Linux or Windows).
- In the host list, select one or more hosts to add to the group and click OK.
- You can filter hosts by host name or host IP address. You can also click
and enter multiple host IP addresses in the displayed search box to search for matches. - If your desired hosts are not in the list, click Install ICAgent. On the displayed page, install ICAgent on the hosts as prompted. For details, see Installing ICAgent (Intra-Region Hosts).
+
- - Click Add to add a custom identifier.
Up to 10 custom identifiers can be added.
+ Creating a Host Group (Custom Identifier)To create a host group of the custom identifier type, you need to plan the hosts to be identified in advance.
+ - Click Create Host Group in the upper right corner.
- In the displayed slide-out panel, enter a host group name, select Custom Identifier for Host Group Type, and select a host OS (Linux or Windows).
Figure 1 Creating a custom identifier host group
+ - Click
and enter a custom identifier. Up to 10 custom identifiers can be added.
- - Click OK.
- Run the following commands to create the custom_tag file:
- Run the cd /opt/cloud command. In the cloud directory, run the mkdir lts command to create the lts directory.
- Run the chmod 750 lts command to modify the permission on the lts directory.
- Run the touch custom_tag command in the lts directory to create the custom_tag file.
- Run the chmod 640 custom_tag;vi custom_tag command to modify the custom_tag permission and open the file.
- Press i to enter the insert mode, enter a custom identifier, press Esc, enter :wq!, save the modification and exit.
- After 5, you can use either of the following methods to add hosts to a custom host group:
- Method 1 (recommended):
- Linux
- In the custom_tag file of the /opt/cloud/lts directory on the host, view the host identifier and add it to the custom host group identifiers to add the host to the host group. For example, in the custom_tag file of the /opt/cloud/lts directory on the host, the identifier of the host is test1, and the custom identifier of the host group is test1. That is, the host is added to the host group.
- Method 2:
- Linux
- - To add a host to a host group, add the custom host group identifier to the custom_tag file in the /opt/cloud/lts directory on the host. For example, if the custom identifier of the host group is test, enter test in the custom_tag file to add the host to the host group.
- If multiple custom identifiers are added, enter any custom identifier in the custom_tag file of the /opt/cloud/lts directory on the host to add the host to the host group.
-
-
-
-
- Modifying a Host GroupYou can change the name of a host group, add hosts to or remove hosts from a host group, or associate a host group with log ingestion configurations.
-
- Table 1 Operations on host groupsOperation
+- Click OK. After the host group is created, go to 5 to add hosts to it.
- Perform the following operations to create the custom_tag file to save host tags:
- Log in to the host and run the cd /opt/cloud command. If the system indicates that the /opt/cloud directory does not exist, run the mkdir /opt/cloud/ command to create it. If the /opt/cloud directory already exists, navigate to it and run the mkdir lts command to create the lts directory in it.
- Run the chmod 750 lts command to modify the permission on the lts directory.
- Run the touch custom_tag command in the lts directory to create the custom_tag file.
- Run the chmod 640 custom_tag;vi custom_tag command to modify the custom_tag permission and open the file.
- Press i to enter the insert mode, enter a custom identifier, press Esc, enter :wq!, save the modification and exit.
- Use either of the following methods to add a host to the custom identifier host group:
+
Table 1 MethodsType
|
-Procedure
+ | Method 1 (Recommended)
+ |
+Method 2
|
-Changing a host group name
+ | Linux host
|
-- Log in to the LTS console. In the navigation pane on the left, choose Host Management.
- On the Host Groups tab, click
in the Operation column of the row containing the target host group. - On the displayed dialog box, change the host group name and customized identifier.
- Click OK.
+ | View the host's identifier in the custom_tag file of the /opt/cloud/lts directory on the host. Then, add the identifier to the host group to include the host within it. For example, if the custom_tag file in the /opt/cloud/lts directory shows the host's identifier as test1, simply add test1 to the group's custom identifiers.
+ |
+- Add the host group's custom identifier to the custom_tag file in the /opt/cloud/lts directory on the host to include the host within the host group. For example, if the group's custom identifier is test, enter test into the custom_tag file.
- If the group has multiple custom identifiers, simply enter any one of them into the custom_tag file of the /opt/cloud/lts directory on the host.
|
-Adding hosts to a host group
+ | Windows host
|
-Method 1:
-- On the Host Management page, click the Host Groups tab, and click
in the row containing the target host group. - Click Add Host.
- In the displayed slide-out panel, all hosts that are not in the host group and run the selected OS type are displayed. Select the hosts to be added to the host group.
- You can filter hosts by host name or host IP address. You can also click
and enter multiple host IP addresses in the displayed search box to search for matches. - If your desired hosts are not in the list, click Install ICAgent. On the displayed page, install ICAgent on the hosts as prompted. For details, see Installing ICAgent.
+View the host's identifier in the custom_tag file of the C:\opt\cloud\lts directory on the host. Then, add the identifier to the host group to include the host within it. For example, if the custom_tag file in the C:\opt\cloud\lts directory shows the host's identifier as test1, simply add test1 to the group's custom identifiers.
+ |
+- Add the host group's custom identifier to the custom_tag file in the C:\opt\cloud\lts directory on the host to include the host within the host group. For example, if the group's custom identifier is test, enter test into the custom_tag file.
- If the group has multiple custom identifiers, simply enter any one of them into the custom_tag file of the C:\opt\cloud\lts directory on the host.
+ |
+
|
+
+
+
+
+
+
+Modifying a Host GroupYou can change the name of a host group, add hosts to or remove hosts from a host group, or associate a host group with log ingestion configurations. For details, see Table 2.
+
+ Table 2 Operations on host groupsOperation
+ |
+Procedure
+ |
+
+
+Changing a host group name
+ |
+- Go to the Host Groups tab page.
- In the host group list, click the modification button in the Operation column of the target host group.
- On the displayed dialog box, modify the information such as the host group name and custom identifier.
- Click OK.
+ |
+
+Adding hosts to a host group
+ |
+Method 1:
+- In the host group list, click
in the row containing the target host group whose type is IP. - Click Add Host.
- In the displayed slide-out panel, all hosts that are not in the host group and run the selected OS type are displayed. Select the hosts to be added to the host group.
- You can filter hosts by host name or host IP address. You can also click
and enter multiple host IP addresses in the displayed search box to search for matches. - If your desired hosts are not in the list, click Install ICAgent. On the displayed page, install ICAgent on the hosts as prompted. For details, see Installing ICAgent.
- Click OK.
Method 2:
-- On the Host Management page, click the Hosts tab.
- In the host list, select the target hosts and click Add to Host Group.
- In the displayed slide-out panel, select the target host group.
- Click OK.
+- On the Host Management page, click the Hosts tab..
- In the host list, select the target hosts and click Add to Host Group.
- In the displayed slide-out panel, select the target host group.
- Click OK.
|
-Removing a host from a host group
+ | Removing a host from a host group
|
-- On the Host Management page, click the Host Groups tab, and click
in the row containing the target host group. - In the host list, click Remove in the Operation column of the row containing the host to be removed.
- In the displayed dialog box, click OK.
+ | - In the host group list, click
in the row containing the target host group. - In the host list, click Remove in the Operation column of the row containing the host to be removed.
- In the displayed dialog box, click OK.
NOTE: This operation is not supported for hosts in the custom identifier host group.
|
-Uninstalling ICAgent from a host
+ | Uninstalling ICAgent from a host
|
-- On the Host Management page, click the Host Groups tab, and click
in the row containing the target host group. - In the host list, click Uninstall ICAgent in the Operation column of the row containing the target host.
- In the displayed dialog box, click OK to uninstall ICAgent from the host and remove the host from the host group.
NOTE: - This operation is not supported for hosts in the custom identifier host group.
- If the host has also been added to other host groups, it will be removed from those groups as well.
+ - In the host group list, click
in the row containing the target host group. - In the host list, click Uninstall ICAgent in the Operation column of the row containing the target host.
- In the displayed dialog box, click OK to uninstall ICAgent from the host and remove the host from the host group.
NOTE: - This operation is not supported for hosts in the custom identifier host group.
- If the host has also been added to other host groups, it will be removed from those groups as well.
|
|
-Removing hosts from a host group
+ | Removing hosts from a host group
|
-- On the Host Management page, click the Host Groups tab, and click
in the row containing the target host group. - In the host list, select the target hosts and click the Remove button above the list.
- Click OK.
+ | - In the host group list, click
in the row containing the target host group. - In the host list, select the target hosts and click the Remove button above the list.
- Click OK.
|
-Associating a host group with an ingestion configuration
+ | Associating a host group with an ingestion configuration
|
-- On the Host Management page, click the Host Groups tab, and click
in the row containing the target host group. - Click the Associated Ingestion Configuration tab.
- Click Associate.
- In the displayed slide-out panel, select the target ingestion configuration.
- Click OK. The associated ingestion configuration is displayed in the list.
+ | - In the host group list, click
in the row containing the target host group. - Click the Associated Ingestion Configuration tab.
- Click Associate.
- In the displayed slide-out panel, select the target ingestion configuration.
- Click OK. The associated ingestion configuration is displayed in the list.
|
-Disassociating a host group from an ingestion configuration
+ | Disassociating a host group from an ingestion configuration
|
-- On the Associated Ingestion Configuration tab, click Disassociate in the Operation column of the row containing the target ingestion configuration.
- Click OK.
+ | - On the Associated Ingestion Configuration tab, click Disassociate in the Operation column of the row containing the target ingestion configuration.
- Click OK.
|
-Disassociating a host group from multiple ingestion configurations
+ | Disassociating a host group from multiple ingestion configurations
|
-- On the Associated Ingestion Configuration tab, select the target ingestion configurations and click the Disassociate button above the list.
- Click OK.
+ | - On the Associated Ingestion Configuration tab, select the target ingestion configurations and click the Disassociate button above the list.
- Click OK.
+ |
+
+Copying a host group ID
+ |
+Hover your cursor over a host group name to copy the host group ID.
+ |
+
+Exporting host information
+ |
+- On the Hosts page, switch to the Intra-Region Hosts, CCE Cluster, or Extra-Region Hosts tab and select the desired hosts.
- Click Export to export the information of the selected hosts to the local PC.
|
-Deleting Host GroupsDeleting a single host group
- - Log in to the LTS console. In the navigation pane on the left, choose Host Management.
- On the Host Groups tab, click
in the Operation column of the row containing the target host group.Figure 3 Deleting a host group
- - In the displayed dialog box, click OK.
- Deleting host groups in batches
- - On the Host Groups tab, select multiple host groups to be deleted and click Delete above the list.
- In the displayed dialog box, click OK.
+ Deleting Host Groups- Choose Host Management in the navigation pane and click the Host Groups tab.
- Delete a host group:
- Click the deletion icon in the Operation column of the row containing the target host group.
- In the displayed dialog box, click OK.
+ - Delete host groups in batches:
- Select host groups to be deleted and click Delete above the list.
- In the displayed dialog box, click OK.
+
diff --git a/docs/lts/umn/lts_03_0015.html b/docs/lts/umn/lts_03_0015.html
index 0b69504f..6fc234d5 100644
--- a/docs/lts/umn/lts_03_0015.html
+++ b/docs/lts/umn/lts_03_0015.html
@@ -1,15 +1,17 @@
How Do I Obtain an AK/SK Pair?
- Obtain and use the AK/SK of a public account.
- Procedure- Log in to the console, hover your cursor over your username in the upper right corner, and select My Credentials.
- Click the Access Keys tab.
- Click Create Access Key, and enter the login password.
- Click OK. The credentials file is automatically downloaded.
- Obtain the AK/SK pair from the credentials file.
+ An access key ID and secret access key (AK/SK) constitute an access key.
+ - AK: access key ID, which is a unique identifier used in conjunction with a secret access key to sign requests cryptographically.
- SK: secret access key used in conjunction with an AK to sign requests cryptographically. It identifies a request sender and prevents the request from being modified.
+ Obtain and use the AK/SK of a public account.
+ Procedure- Log in to the console, hover your cursor over your username in the upper right corner, and select My Credentials.
- Choose Access Keys.
- Click Create Access Key and enter a description.
- Click OK and download the AK/SK immediately.
- Obtain the AK/SK pair from the credentials file.
Up to two access keys can be created for each user. An access key can be downloaded only right after it is created. Keep it secure after it is generated. If the Create Access Key button is grayed out, delete an access key first before creating one.
diff --git a/docs/lts/umn/lts_04_0002.html b/docs/lts/umn/lts_04_0002.html
deleted file mode 100644
index eac9eb30..00000000
--- a/docs/lts/umn/lts_04_0002.html
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
- Log Analysis
-
-
-
diff --git a/docs/lts/umn/lts_04_0003.html b/docs/lts/umn/lts_04_0003.html
index 3f241359..a8b09cbf 100644
--- a/docs/lts/umn/lts_04_0003.html
+++ b/docs/lts/umn/lts_04_0003.html
@@ -1,26 +1,67 @@
Managing Log Groups
- A log group is a group of log streams. Up to 100 log groups can be created for a single account.
- Creating a Log GroupLog groups can be created in two ways. They are automatically created when other services are connected to LTS, or you can create one manually by following the steps described here.
- - Log in to the LTS console, choose Log Management in the navigation pane on the left, and click Create Log Group in the upper right corner.
Figure 1 Creating a log group
-
- - In the dialog box displayed, enter a log group name. After a log group is created, its name cannot be changed. A log group name:
- Can contain only letters, digits, hyphens (-), underscores (_), and periods (.).
- Cannot start with a period (.) or underscore (_) or end with a period (.).
- Can contain 1 to 64 characters.
- Collected logs are sent to the log streams in the log group. If there are too many logs to collect, you are advised to separate logs into different log groups based on log types, and name log groups in an easily identifiable way.
-
- - Set Log Retention Duration. You can set it to 1 to 30 days. If this parameter is not specified, logs are retained for 7 days by default.
Figure 2 Creating a log group
- - Click OK.
- In the log group list, you can view details of log groups, including log group name, log retention duration (days), creation type, creation time, and number of log streams.
- Click the log group name, the details page of one of its log streams is displayed.
- When multiple log groups are created concurrently, there may be a limit exceeding error.
-
+ A log group is the basic unit for LTS to manage logs. It classifies and consists of log streams, but does not store any log data. Up to 100 log groups can be created for an account.
+ A log group usually corresponds to a project or business in a company. You are advised to sort log streams of various applications or services within a project or business to the same log group. In this way, project staff only need to monitor log streams in the log group corresponding to their project, without being distracted by log streams of other projects.
+ LTS allows you to add tags to log groups to help O&M personnel manage services.
+ PrerequisitesYou have obtained an account and its password for logging in to the LTS console.
+
+ Creating a Log Group- Log in to the management console and choose Management & Deployment > Log Tank Service. The Log Management page is displayed by default.
- Click Create Log Group.
- On the displayed page, set log group parameters by referring to Table 1.
+ Table 1 Log group parametersParameter
+ |
+Description
+ |
+
+
+Log Group Name
+ |
+- Enter 1 to 64 characters, including only letters, digits, hyphens (-), underscores (_), and periods (.). Do not start with a period or underscore or end with a period.
- Collected logs are sent to log streams of the corresponding log groups. If there are too many logs to collect, separate logs into different log groups based on log types, and name log groups in an easily identifiable way.
+ |
+
+Enterprise Project Name
+ |
+Select an enterprise project. You can click View Enterprise Projects to view all enterprise projects.
+Enterprise projects allow you to manage cloud resources and users by project.
+ |
+
+Log Retention Duration
+ |
+Specify the log retention duration for the log group, that is, how many days the logs will be stored in LTS after being reported to LTS.
+By default, logs are retained for 30 days (customizable for 1 to 365 days).
+ |
+
+Tag
+ |
+You can tag log groups as required. Click Add Tags, enter a tag key and value, and enable Apply to Log Stream.
+- To add more tags, repeat this step. A maximum of 20 tags can be added.
- A tag key can contain up to 128 characters, and a tag value can contain up to 255 characters.
- A tag key must be unique.
- If a tag is used by a transfer task, you need to modify the task configuration after deleting the tag.
+ |
+
+Remark
+ |
+Enter remarks. The value contains up to 1,024 characters.
+ |
+
+
+
+
+ - Click OK. The created log group will be displayed in the log group list.
- In the log group list, you can view information such as the log group name, tags, and log streams.
- Click the log group name to access the log stream details page.
- When multiple log groups are created concurrently, there may be a limit exceeding error.
+
+
+ Modifying a Log GroupYou can modify log group settings, such as the group name, log retention duration, or tags as follows:
+ - In the log group list on the Log Management page, locate the target log group and click Modify in the Operation column.
- On the page displayed, modify the group name, log retention duration, and tags on the displayed page.
- Click OK.
- After the modification is successful, move the cursor over the log group name. The new and original log group names are displayed.
Figure 1 Log group name
+
Deleting a Log GroupYou can delete a log group that is no longer needed. Deleting a log group will also delete the log streams and log data in the log group. Deleted log groups cannot be recovered. Exercise caution when performing the deletion.
If you want to delete a log group that is associated with a log transfer task, delete the task first.
- - In the log group list on the Log Management page, locate the target log group and click Delete in the Operation column.
- Enter DELETE and click OK.
Figure 3 Deleting a log group
-
+ - In the log group list on the Log Management page, locate the target log group and click Delete in the Operation column.
- Enter DELETE and click OK.
Figure 2 Deleting a log group
+
- Searching Log Groups/StreamsIn the log group list, click the search box and set the following filter criteria:
- - Log group/stream
- Log group name/ID
- Log stream name/ID
- Figure 4 Searching log groups/streams
+ Searching Log Groups/StreamsIn the log group list, you can set the following filter criteria:
+ - Log group/stream
- Original log group/stream name
- Log group name/ID
- Log stream name/ID
- Log group tag
- Remarks
+ Figure 3 Searching log groups/streams
+
+ Other Operations- To check the details of a log group, including the log group name, ID, and creation time, go to the log group list and click Details in the Operation column of the desired log group.
- To download all displayed information about a log group to the local PC, click
next to the search box.
diff --git a/docs/lts/umn/lts_04_0004.html b/docs/lts/umn/lts_04_0004.html
index 99a0f520..335856bf 100644
--- a/docs/lts/umn/lts_04_0004.html
+++ b/docs/lts/umn/lts_04_0004.html
@@ -1,29 +1,71 @@
Managing Log Streams
- A log stream is the basic unit for reading and writing logs. Sorting logs into different log streams makes it easier to find specific logs when you need them.
+ LTS manages logs by log stream. Collected logs of different types are classified and stored in different log streams for easier log management. If there are a large number of logs, you can create multiple log streams and name them for quick log search. For example, you can sort operation logs and access logs into different log streams, making it easier to find specific logs when you need them. You can add tags to log streams to help O&M personnel manage services.
Up to 100 log streams can be created in a log group. The upper limit cannot be increased. If you cannot create a log stream because the upper limit is reached, you are advised to delete log streams that are no longer needed and try again, or create log streams in a new log group.
PrerequisitesYou have created a log group.
- Creating a Log StreamLog streams can be created in two ways. They are automatically created when other services are connected to LTS, or you can create one manually by following the steps described here.
- - On the LTS console, click
on the left of a log group name. - Click Create Log Stream in the upper left corner of the displayed page, and enter a log stream name. After a log stream is created, its name cannot be changed. A log stream name:
- Can contain only letters, digits, hyphens (-), underscores (_), and periods (.).
- Cannot start with a period (.) or underscore (_) or end with a period (.).
- Can contain 1 to 64 characters.
-Figure 1 Creating a log stream
- Collected logs are sent to the created log stream. If there are too many logs to collect, you are advised to separate logs into different log streams based on log types, and name log streams in an easily identifiable way.
-
- - Click OK.
In the log stream list, you can view details of the list, including the log stream name, creation time, and creation type.
-Figure 2 A created log stream
- Logs cannot be downloaded from log streams on the LTS console. You need to transfer logs to Object Storage Service (OBS) and download them from the OBS console.
+ Creating a Log Stream- Log in to the management console and choose Management & Deployment > Log Tank Service. The Log Management page is displayed by default.
- Click
on the left of the target log group. - Click Create Log Stream. On the displayed page, set log stream parameters by referring to Table 1.
+ Table 1 Log stream parametersParameter
+ |
+Description
+ |
+
+
+Log Group Name
+ |
+The name of the target log group is displayed by default.
+ |
+
+Log Stream Name
+ |
+A log stream name can contain 1 to 64 characters, including only letters, digits, hyphens (-), underscores (_), and periods (.). It cannot start with a period or underscore or end with a period.
+ |
+
+Enterprise Project Name
+ |
+Select the required enterprise project. The default value is default. You can click View Enterprise Projects to view all enterprise projects.
+ |
+
+Log Retention Duration
+ |
+Specify the log retention duration for the log stream, that is, how many days the logs will be stored in LTS after being reported to LTS.
+By default, logs are retained for 30 days (customizable for 1 to 365 days).
+- If you enable Log Retention Duration for the log stream, logs are retained for the duration set for the log stream.
- If you disable Log Retention Duration for the log stream, logs are retained for the duration set for the log group.
+ |
+
+Tag
+ |
+You can tag log streams as required. Click Add Tags and enter a tag key and tag value.
+ NOTE: - To add more tags, repeat this step. A maximum of 20 tags can be added.
- A tag key can contain up to 128 characters, and a tag value can contain up to 255 characters.
- A tag key must be unique.
- If a tag is used by a transfer task, you need to modify the task configuration after deleting the tag.
+ |
+
+Remark
+ |
+Enter remarks. The value contains up to 1,024 characters.
+ |
+
+
+
-
+ Figure 1 Creating a log stream
+ - Click OK. In the log stream list, you can view information such as the log stream name and operations.
+
+ Modifying a Log StreamBy default, a log stream inherits the log retention setting from the log group it belongs to.
+ - In the log stream list, locate the target log stream and click
in the Operation column. - On the page displayed, modify the stream name, log retention duration, and tags.
- If you disable Log Retention Duration, the log stream will inherit the log retention setting of the log group.
- If you enable Log Retention Duration, you can set the log retention duration specifically for the log stream.
- The logs that exceed the retention period will be automatically deleted. You can transfer logs to OBS buckets for long-term storage.
+
+ - Click OK.
- After the modification is successful, move the cursor over the log stream name. The new and original log stream names are displayed.
Figure 2 Log stream name
+
Deleting a Log StreamYou can delete a log stream that is no longer needed. Deleting a log stream will also delete the log data in the log stream. Deleted log streams cannot be recovered. Exercise caution when performing the deletion.
- Before deleting a log stream, check whether any log collection task is configured for it. If there is a log collection task, deleting the log stream may affect log reporting.
- If you want to delete a log stream that is associated with a log transfer task, delete the task first.
- - In the log stream list, locate the target log stream and click
in the Operation column. - Enter DELETE and click OK.
Figure 3 Deleting a log stream
-
+ - In the log stream list, locate the target log stream and click
in the Operation column. - Enter DELETE and click OK.
Figure 3 Deleting a log stream
+
-
diff --git a/docs/lts/umn/lts_04_0011.html b/docs/lts/umn/lts_04_0011.html
index b9a5776c..8c6d5a1e 100644
--- a/docs/lts/umn/lts_04_0011.html
+++ b/docs/lts/umn/lts_04_0011.html
@@ -1,10 +1,9 @@
Overview
- Logs reported from hosts and cloud services are retained in LTS for seven days by default. You can set the retention period to be 1 to 30 days. Retained logs are deleted once the retention period is over. For long-term storage, you can transfer logs to Object Storage Service (OBS).
- Log transfer refers to when logs are replicated to other cloud services. Retained logs are deleted once the retention period is over, but the logs that have been transferred to other services are not affected.
+ Logs reported from hosts and cloud services are retained in LTS. You can set the retention period. Retained logs are deleted once the retention period is over. For long-term retention, you can transfer logs to other cloud services.
+ Log transfer refers to when logs are replicated to other cloud services. LTS deletes retained logs once the retention period is over, but the logs that have been transferred to other services are not affected.
-
diff --git a/docs/lts/umn/lts_04_0012.html b/docs/lts/umn/lts_04_0012.html
index 8fae72d5..ef1545cf 100644
--- a/docs/lts/umn/lts_04_0012.html
+++ b/docs/lts/umn/lts_04_0012.html
@@ -4,13 +4,11 @@
diff --git a/docs/lts/umn/lts_04_0013.html b/docs/lts/umn/lts_04_0013.html
deleted file mode 100644
index 5e6db4ec..00000000
--- a/docs/lts/umn/lts_04_0013.html
+++ /dev/null
@@ -1,61 +0,0 @@
-
-
- ICAgent Statuses
- The following table lists the ICAgent statuses.
-
- Table 1 ICAgent statusesStatus
- |
-Description
- |
-
-
-Running
- |
-ICAgent is running properly.
- |
-
-Uninstalled
- |
-ICAgent is not installed.
- |
-
-Installing
- |
-ICAgent is being installed. This process takes about a minute.
- |
-
-Installation failed
- |
-ICAgent installation failed.
- |
-
-Upgrading
- |
-ICAgent is being upgraded. This process takes about a minute.
- |
-
-Upgrade failed
- |
-ICAgent upgrade failed.
- |
-
-Offline
- |
-ICAgent is abnormal because the Access Key ID/Secret Access Key (AK/SK) pair is incorrect. Obtain the correct AK/SK pair and install ICAgent again.
- |
-
-Faulty
- |
-ICAgent is faulty. Contact technical support.
- |
-
-
-
-
-
-
-
diff --git a/docs/lts/umn/lts_04_0015.html b/docs/lts/umn/lts_04_0015.html
index 44271a1d..c5473061 100644
--- a/docs/lts/umn/lts_04_0015.html
+++ b/docs/lts/umn/lts_04_0015.html
@@ -1,16 +1,16 @@
- Permissions Management
- This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions control for your LTS. With IAM, you can:
- - Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing LTS resources
- Grant only the permissions required for users to perform a specific task.
- Entrust an account or a cloud service to perform professional and efficient O&M on your LTS resources.
- If your account meets your permissions requirements, skip this section.
- This section describes the procedure for granting user permissions. Figure 1 shows the process flow.
- PrerequisitesBefore granting permissions to user groups, learn about "Permissions Management" in the section Service Overview) for LTS and select the permissions as required. For system permissions of other cloud services, see Permissions supported by IAM.
+ Granting LTS Permissions to IAM Users
+ You can use Identity and Access Management (IAM) for fine-grained permissions control for your LTS. With IAM, you can:
+ - Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing LTS resources
- Grant users only the permissions required to perform a given task based on their job responsibilities.
- Entrust an account or a cloud service to perform efficient O&M on your LTS resources.
+ If your account meets your permissions requirements, you can skip this section.
+ Figure 1 shows the process flow of role/policy-based authorization.
+ PrerequisitesBefore granting permissions to user groups, learn about system-defined permissions in Permissions Management for LTS.
- Process FlowFigure 1 Process of granting permissions to a user
- - Log in to the IAM console. Create a user group on the IAM console and grant the LTS FullAccess permission to the user group. For details, see Create a user group and grant it permissions.
If you select the LTS FullAccess permissions, the Tenant Guest policy that the permission depends on is automatically selected. You also need to grant the Tenant Administrator policy for the global service project to the user group.
+ Process FlowFigure 1 Process of granting LTS permissions
+ - Log in to the IAM console. Create a user group on the IAM console and assign the LTS FullAccess permissions to the group. For details, see Creating a User Group and Assigning Permissions.
If you select the LTS FullAccess permissions, the Tenant Guest policy that the permission depends on is automatically selected. You also need to grant the Tenant Administrator policy for the global service project to the user group.
- - Create a user on the IAM console and add the user to the user group created in 1. For details, see Create an IAM user and add it to the created user group.
- Log in to the console by using the created user and verify permissions in the authorized region. For details, see Log in as the IAM user and verify permissions.
+ - Create a user on the IAM console and add the user to the user group created in 1. For details, see Creating a User and Adding the User to a User Group.
- Log in to the LTS console as the created user, switch to the authorized region, and verify your permissions by performing operations on the console. For details, see Logging In as an IAM User.
diff --git a/docs/lts/umn/lts_04_0040.html b/docs/lts/umn/lts_04_0040.html
index 4b6b38bf..fe13a826 100644
--- a/docs/lts/umn/lts_04_0040.html
+++ b/docs/lts/umn/lts_04_0040.html
@@ -8,8 +8,6 @@
- Transferring Logs to OBS
- - Transferring Logs to DMS
-
diff --git a/docs/lts/umn/lts_04_0041.html b/docs/lts/umn/lts_04_0041.html
index e01e1484..d9b423b4 100644
--- a/docs/lts/umn/lts_04_0041.html
+++ b/docs/lts/umn/lts_04_0041.html
@@ -1,139 +1,297 @@
Transferring Logs to OBS
-You can transfer logs to OBS and download log files from the OBS console.
- To transfer logs, you must have the OBS Administrator permissions apart from the LTS permissions.
+ You can transfer logs to OBS and download log files from the OBS console. You can choose scheduled or one-time transfers.
+ - To use this function, you must have the OBS Administrator permissions apart from the LTS permissions.
- LTS transfers only logs generated after the transfer task is configured, not historical logs.
- Prerequisites- Logs have been ingested to LTS.
- You have created an OBS bucket.
+ Prerequisites- Logs have been ingested to LTS. For details, see Log Ingestion.
- You have created an OBS bucket.
- Creating a Log Transfer Task- Log in to the LTS console and choose Log Transfer in the navigation pane on the left.
- Click Configure Log Transfer in the upper right corner.
- On the displayed page, configure the log transfer parameters.
After a transfer task is created, you can modify parameters except the log group name, transfer destination and log stream name.
-
-
-Table 1 Transfer parametersParameter
+Creating a Scheduled Log Transfer Task- Log in to the management console and choose Management & Deployment > Log Tank Service.
- Choose Log Transfer in the navigation pane.
- Click Configure Log Transfer in the upper right corner.
- On the displayed page, configure the log transfer parameters.
+ Table 1 Transfer parametersParameter
|
-Description
+ | Description
|
-Example Value
+ | Example
|
-Enable Transfer
+ | Log Source Account
|
-Enabled by default.
+ | - Current: Logs of the current account will be transferred.
- Other: Logs of the delegator account will be transferred. Ensure that the delegator has created an agency for log transfer delegation. For details, see section "Creating an Agency".
|
-Enabled
+ | Current
|
-Transfer Log to OBS
+ | Transfer Mode
|
-Enable log transfer to OBS.
+ | If you select the current account as the log source account, you can select Scheduled or One-time.
+- Scheduled: Logs are periodically transferred to OBS for long-term storage.
- One-time: Logs are transferred to OBS for long-term storage in a one-time way.
|
-OBS
+ | Scheduled
|
-Transfer Destination
+ | Agency Name
|
-Select a cloud service for log transfer.
+ | This parameter is required when Log Source Account is set to Other. Enter the name of the agency created by the delegator.
|
-OBS
+ | -
|
-Log Group Name
+ | Delegator Account Name
|
-Select a log group.
+ | This parameter is required when Log Source Account is set to Other. Enter the account name of the delegator.
|
-N/A
+ | -
|
-Log Stream Name
+ | Enable Transfer
|
-Select a log stream.
+ | Enabled by default.
|
-N/A
+ | Enabled
|
-OBS Bucket
+ | Transfer Destination
|
-- Select an OBS bucket.
- If no OBS buckets are available, click View OBS Bucket to access the OBS console and create an OBS bucket.
- If encryption has been enabled for the selected OBS bucket, select a key name and select I agree to grant permissions on Key Management Service (KMS) to LTS so LTS can create and use keys to encrypt and decrypt transferred logs.
- - Only Standard OBS buckets are supported in LTS.
+ | Select a cloud service for log transfer.
|
-N/A
+ | OBS
|
-Key Name
+ | Log Group Name
|
-Select a key name for an OBS bucket for which encryption has been enabled. If no keys are available, click Create Key and Authorize to go to the Data Encryption Workshop (DEW) console and create a key.
+ | Select a log group.
|
-N/A
+ | N/A
|
-Custom Log Transfer Path
+ | Enterprise Project Name
|
-- Enabled: Logs will be transferred to a custom path to separate transferred log files of different log streams.
The format is /LogTanks/Region name/Custom path. The default custom path is lts/%Y/%m/%d, where %Y indicates the year, %m indicates the month, and %d indicates the day. A custom path must meet the following requirements: - Must start with /LogTanks/Region name.
- Can contain only letters, digits, and the following special characters: &$@;:,=+?-._/ %. The character % can only be followed only by Y (year), m (month), d (day), H (hour), and M (minute). Any number of characters can be added before and after %Y, %m, %d, %H, and %M, and the sequence of these variables can be changed.
- Can contain 1–128 characters.
+ Select an enterprise project.
+- This parameter is displayed only when the enterprise project function is enabled for the current account.
- If the enterprise project function is enabled for the current account:
- All enterprise projects under the current account are displayed in the drop-down list when Log Source Account is set to Current.
- default is displayed when Log Source Account is set to Other and the enterprise project function is not enabled for the delegator account.
- All enterprise projects under the delegator account are displayed when Log Source Account is set to Other and the enterprise project function is enabled for the delegator account.
+
+ |
+ -
+ |
+
|
+Log Stream Name
+ |
+Select a log stream.
+ NOTE: Log streams that have been configured with OBS transfer settings cannot be configured again.
+
+ |
+-
+ |
+
+OBS Bucket
+ |
+- Select an OBS bucket.
- If no OBS buckets are available, click View OBS Bucket to access the OBS console and create an OBS bucket.
+ - Currently, LTS supports only standard OBS buckets with the single-AZ storage policy.
+ NOTE: If you select an unauthorized OBS bucket, LTS will take 15 minutes to authorize the ACL for the bucket. If your configuration fails, try again 15 minutes later. To prevent log transfer failures, exercise caution when modifying bucket policies.
+
+ |
+-
+ |
+
+Custom Log Transfer Path
+ |
+- Enabled: Logs will be transferred to a custom path to separate transferred log files of different log streams.
The format is /LogTanks/Region name/Custom path. The default custom path is lts/%Y/%m/%d, where %Y indicates the year, %m indicates the month, and %d indicates the day. A custom path must meet the following requirements: - Must start with /LogTanks/Region name.
- Can contain only letters, digits, and the following special characters: &$@;:,=+?-._/ %. The character % can only be followed only by Y (year), m (month), d (day), H (hour), and M (minute). Any number of characters can be added before and after %Y, %m, %d, %H, and %M, and the sequence of these variables can be changed.
- Can contain 1–128 characters.
Example:
-- If you enter LTS-test/%Y/%m/%done/%H/%m, the path is LogTanks/Region name/LTS-test/Y/m/done/H/m/Log file name.
- If you enter LTS-test/%d/%H/%m/%Y, the path is LogTanks/Region name/LTS-test/d/H/m/Y/Log file name.
+- If you enter LTS-test/%Y/%m/%d/%H/%m, the path is LogTanks/Region name/LTS-test/Y/m/d/H/M/Log file name.
- If you enter LTS-test/%d/%H/%m/%Y, the path is LogTanks/Region name/LTS-test/d/H/m/Y/Log file name.
- Disabled: Logs will be transferred to the default path. The default path is LogTanks/Region name/2019/01/01/Log group/Log stream/Log file name.
|
-LTS-test/%Y/%m/%done/%H/%m
+ | LTS-test/%Y/%m/%d/%H/%M
|
-Log Prefix
+ | Log Prefix
|
-The file name prefix of the log files transferred to an OBS bucket
+ | The file name prefix of the log files transferred to an OBS bucket
The prefix must meet the following requirements:
- Can contain 0 to 64 characters.
- Can contain only letters, digits, hyphens (-), underscores (_), and periods (.).
Example: If you enter LTS-log, the log file name will be LTS-log_Log file name.
|
-LTS-log
+ | LTS-log
|
-Format
+ | Format
|
-The storage format of logs. The value can be Raw Log Format or JSON.
-- Examples of the raw log format:
(Logs displayed on the LTS console are in the raw format.) Sep 30 07:30:01 ecs-bd70 CRON[3459]: (root) CMD (/opt/oss/servicemgr/ICAgent/bin/manual/mstart.sh > /dev/null 2>&1)
+ The storage format of logs. The value can be Raw Log Format or JSON.
+- Example of the raw log format:
(Logs displayed on the LTS console are in the raw format.) Sep 30 07:30:01 ecs-bd70 CRON[3459]: (root) CMD (/opt/oss/servicemgr/ICAgent/bin/manual/mstart.sh > /dev/null 2>&1)
- The following is an example of the JSON format:
{"host_name":"ecs-bd70","ip":"192.168.0.54","line_no":249,"message":"Sep 30 14:40:01 ecs-bd70 CRON[4363]: (root) CMD (/opt/oss/servicemgr/ICAgent/bin/manual/mstart.sh > /dev/null 2>&1)\n","path":"/var/log/syslog","time":1569825602303}
|
- Json
+ | Json
|
|
-Log Transfer Interval
+ | Log Transfer Interval
|
-The interval for automatically transferring logs to OBS buckets. The value can be 2, 5, or 30 minutes, or 1, 3, 6, or 12 hours.
+ | The interval for automatically transferring logs to OBS buckets. The value can be 2, 5, or 30 minutes, or 1, 3, 6, or 12 hours.
|
-3 hours
+ | 3 hours
|
-Time Zone
+ | Time Zone
|
-When logs are transferred to OBS buckets, the time in the transfer directory and file name will use the specified UTC time zone.
+ | When logs are transferred to OBS buckets, the time in the transfer directory and file name will use the specified UTC time zone.
|
-(UTC) Coordinated Universal Time
+ | (UTC) Coordinated Universal Time
+ |
+
+Filter by Tag Fields
+ |
+During transfer, logs will be filtered by tag fields collected by ICAgent.
+- Disabled: Logs will not be filtered by tag fields.
- Enabled: Default tag fields include those for hosts (hostIP, hostId, hostName, pathFile, and collectTime) and for Kubernetes (clusterName, clusterId, nameSpace, podName, containerName, and appName). Optional public tag fields are regionName, logStreamName, logGroupName, and projectId.
NOTE: When Filter by Tag Fields is enabled, Format must be JSON.
+
+ - Filter by Tag Fields: When this parameter is enabled, logs will be filtered by tags.
+ |
+Enabled
+ |
+
+Compressed Format
+ |
+Non-compression and gzip/zip compression are supported.
+ |
+gzip
|
- - Click OK. When the log transfer status changes to Normal, the transfer task has been created.
- Click the OBS bucket name in the Transfer Destination column to access the OBS console and view the transferred log files.
Transferred logs can be downloaded from OBS to your local computer for viewing.
-Figure 1 Transferring logs to OBS
+ - Click OK. When the log transfer status changes to Normal, the transfer task has been created.
- Click the OBS bucket name in the Transfer Destination column to switch to the OBS console and view the transferred log files.
Transferred logs can be downloaded from OBS to your local computer for viewing.
+Figure 1 Transferring logs to OBS
Logs stored in OBS are in raw or JSON format.
-
-
+
-Modifying a Log Transfer Task- Log in to the LTS console and choose Log Transfer in the navigation pane on the left.
- Locate the row that contains the target transfer task and click Modify in the Operation column.
- Click OK.
+ Creating a One-off Log Transfer Task- Click Configure Log Transfer in the upper right corner.
- On the displayed page, configure the log transfer parameters.
+ Table 2 Transfer parametersParameter
+ |
+Description
+ |
+Example
+ |
+
+
+Transfer Mode
+ |
+- Scheduled: Logs are periodically transferred to OBS for long-term storage.
- One-time: Logs are transferred to OBS for long-term storage in a one-time way.
+ |
+One-time
+ |
+
+Transfer Destination
+ |
+Select a cloud service for log transfer.
+ |
+OBS
+ |
+
+Log Group Name
+ |
+Select a log group.
+ |
+N/A
+ |
+
+Enterprise Project Name
+ |
+Select an enterprise project.
+- This parameter is displayed only when the enterprise project function is enabled for the current account.
- If the enterprise project function is enabled for the current account:
- All enterprise projects under the current account are displayed in the drop-down list when Log Source Account is set to Current.
- default is displayed when Log Source Account is set to Other and the enterprise project function is not enabled for the delegator account.
- All enterprise projects under the delegator account are displayed when Log Source Account is set to Other and the enterprise project function is enabled for the delegator account.
+
+ |
+-
+ |
+
+Log Stream Name
+ |
+Select a log stream.
+ NOTE: Log streams that have been configured with OBS transfer settings cannot be configured again.
+
+ |
+-
+ |
+
+Filter By
+ |
+Keyword is selected by default. Enter the keyword to be filtered in the text box.
+ |
+-
+ |
+
+Log Time Range
+ |
+There are three types of time range: relative time from now, relative time from last, and specified time. Select a time range as required.
+- From now: queries log data generated in a time range that ends with the current time, such as the previous 1, 5, or 15 minutes. For example, if the current time is 19:20:31 and 1 hour is selected as the relative time from now, the charts on the dashboard display the log data that is generated from 18:20:31 to 19:20:31.
- From last: queries log data generated in a time range that ends with the current time, such as the previous 1 or 15 minutes. For example, if the current time is 19:20:31 and 1 hour is selected as the relative time from last, the charts on the dashboard display the log data that is generated from 18:00:00 to 19:00:00.
- Specified: queries log data that is generated in a specified time range.
+ |
+-
+ |
+
+Total Log Events
+ |
+Total number of log events.
+ |
+-
+ |
+
+Log Files
+ |
+Max log events for each transfer: 20 million. Max transfer files: 200.
+ |
+-
+ |
+
+OBS Bucket
+ |
+
+ |
+-
+ |
+
+Bucket Directory
+ |
+OBS bucket directory.
+ |
+-
+ |
+
+Transfer File Name
+ |
+Custom transfer file name. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed.
+ |
+-
+ |
+
+Format
+ |
+Storage format of logs. The value can be Raw Log Format, JSON, or CSV.
+- Example of the raw log format:
(Logs displayed on the LTS console are in the raw format.) Sep 30 07:30:01 ecs-bd70 CRON[3459]: (root) CMD (/opt/oss/servicemgr/ICAgent/bin/manual/mstart.sh > /dev/null 2>&1)
+
+ - Example of the JSON format:
{"host_name":"ecs-bd70","ip":"192.168.0.54","line_no":249,"message":"Sep 30 14:40:01 ecs-bd70 CRON[4363]: (root) CMD (/opt/oss/servicemgr/ICAgent/bin/manual/mstart.sh > /dev/null 2>&1)\n","path":"/var/log/syslog","time":1569825602303}
+ - CSV: Log content is displayed in a table.
+ |
+Json
+ |
+
+
+
+
+ - Click OK. When the log transfer status changes to Normal, the transfer task has been created.
- Click the OBS bucket name in the Transfer Destination column to switch to the OBS console and view the transferred log files.
- Download the transferred logs from OBS for viewing.
+
+ Modifying a Log Transfer Task- Locate the row that contains the target transfer task and click Modify in the Operation column.
- Click OK.
+
+ Viewing Transfer Details- Locate the target log transfer task and click More > Details in the row of the desired task to view its details.
- On the displayed Transfer Details page, you can view the log transfer details.
Deleting a Log Transfer TaskIf logs do not need to be transferred, you can delete the transfer task.
- After a transfer task is deleted, log transfer will be stopped. Exercise caution when performing the deletion.
- After a transfer task is deleted, the logs that have been transferred remain in OBS.
- When you create a transfer task, OBS will grant read and write permissions to LTS for the selected bucket. If one OBS bucket is used by multiple transfer tasks, perform the following operations to delete the transfer task:
- If only one transfer task is created using this OBS bucket, delete the bucket access permission granted to specific users on the Access Control > Bucket ACLs tab page on the OBS console when you delete the transfer task.
- If multiple transfer tasks are created using this OBS bucket, do not delete the bucket access permission. Otherwise, data transfer will fail.
- - Log in to the LTS console and choose Log Transfer in the navigation pane on the left.
- Locate the row of the target transfer task and choose Delete in the Operation column.
- Click OK.
+ - Locate the row of the target transfer task and choose Delete in the Operation column.
- Click OK.
Viewing Transfer StatusThe status of a transfer task can be Normal, Abnormal, or Disabled.
- - Normal: The log transfer task works properly.
- Abnormal: An error occurred in the log transfer task. The possible causes are as follows:
- The OBS bucket has been deleted. Specify another OBS bucket.
- Access control on the OBS bucket is configured incorrectly. Access the OBS console to correct the settings.
- The key for the encrypted OBS bucket has been deleted or the authorization has been canceled. Ensure that the key is valid.
- - Disabled: The log transfer task is stopped.
+ - Normal: The log transfer task works properly.
- Abnormal: An error occurred in the log transfer task. The possible cause is that the access control on the OBS bucket is configured incorrectly. Access the OBS console to correct the settings.
- Disabled: The log transfer task is stopped.
diff --git a/docs/lts/umn/lts_04_0043.html b/docs/lts/umn/lts_04_0043.html
deleted file mode 100644
index b04bfbd8..00000000
--- a/docs/lts/umn/lts_04_0043.html
+++ /dev/null
@@ -1,138 +0,0 @@
-
-
- Transferring Logs to DMS
- You can use DMS APIs to retrieve logs in real time.
- Prerequisites- Logs have been ingested to LTS.
- Before registering a DMS Kafka instance, configure an inbound rule to allow access from 198.19.128.0/17 over port 9011.
-
- Procedure- Log in to the LTS console and choose Log Transfer in the navigation pane on the left.
- Click Create Log Transfer in the upper right corner.
- On the displayed page, configure the log transfer parameters.
After a transfer task is created, you can modify parameters except the log group name and transfer mode.
-
-
-Table 1 Transfer parametersParameter
- |
-Description
- |
-Example Value
- |
-
-
-Enable Transfer
- |
-Enabled by default.
- |
-Enabled
- |
-
-Transfer Destination
- |
-Select a cloud service for log transfer.
- |
-DMS
- |
-
-Log Group Name
- |
-Select a log group.
- |
-N/A
- |
-
-Log Stream Name
- |
-Select a log stream.
- |
-N/A
- |
-
-Kafka Instance
- |
-Select a Kafka instance. If no instances are available, click View Kafka Instances to access the DMS console and create a Kafka premium instance.
-If a Kafka instance has been registered, you can modify it. For details about how to register a Kafka instance, see Registering a Kafka Instance.
- |
-N/A
- |
-
-Topic
- |
-Select a topic for the Kafka instance. If no topics are available, access the DMS console and create a topic for the Kafka premium instance.
- |
-topic-01
- |
-
-Format
- |
-Only the raw log format is supported. The following is an example:
-(Logs displayed on the LTS console are in the raw format.) Sep 30 07:30:01 ecs-bd70 CRON[3459]: (root) CMD (/opt/oss/servicemgr/ICAgent/bin/manual/mstart.sh > /dev/null 2>&1)
-
- |
-Raw Log Format
- |
-
-Log Transfer Interval
- |
-Logs are transferred to the Kafka instance in real time.
- |
-Real time
- |
-
-Filter by Tag Fields
- |
-During transfer, logs will be filtered by tag fields collected by ICAgent.
-- Disabled: Logs will not be filtered by tag fields.
- Enabled: Default tag fields include those for hosts (hostIP, hostId, hostName, pathFile, and collectTime) and for Kubernetes (clusterName, clusterId, nameSpace, podName, and appName). Optional common tag fields are regionName and projectId.
- |
-Enabled
- |
-
-
-
-
- - Click OK. When the log transfer status changes to Normal, the transfer task has been created. If you transfer logs of another account, the log group and stream belong to the delegator. When you click the name of the delegator's log group or stream on the Log Transfer page, you will be directed to the log group or stream through the agency.
- Click the Kafka premium instance in the Transfer Destination column to access its basic information page.
-
- Registering a Kafka Instance- If you select a Kafka instance that is not registered, access the page for registering the Kafka instance.
- Configure the parameters for registering a Kafka instance.
-
Parameter
- |
-Description
- |
-Example Value
- |
-
-
-Kafka Instance
- |
-DMS instance name.
- |
-Kafka-01
- |
-
-Create DMS Network
- |
-Connect the Kafka instance to LTS so that LTS can send data through this network.
- |
--
- |
-
-Username
- |
-If SASL authentication is enabled for the Kafka instance, enter the username for SASL authentication.
- |
-DMS
- |
-
-Password
- |
-If SASL authentication is enabled for the Kafka instance, enter the password for SASL authentication.
- |
--
- |
-
-
-
-
- - Click OK.
-
-
-
-
diff --git a/docs/lts/umn/lts_04_0052.html b/docs/lts/umn/lts_04_0052.html
new file mode 100644
index 00000000..d5caac89
--- /dev/null
+++ b/docs/lts/umn/lts_04_0052.html
@@ -0,0 +1,589 @@
+
+
+ Configuring Log Content Delimiters
+ You can configure delimiters to split log content into words, so you can search for logs by these words. LTS has preconfigured the following delimiters:
+ , '";=()[]{}@&<>/:\n\t\r
+ If the default delimiters cannot meet your needs, you can set custom delimiters.
+ Precautions- Your custom delimiters are applicable only to the log events generated after the delimiters are configured.
- The delimiter configured on the Delimiters tab page takes effect for all log streams in the current region. For details about how to configure delimiters for a single log stream, see Setting Indexes.
+
+ Procedure- Log in to the management console and choose Management & Deployment > Log Tank Service.
- Choose Configuration Center in the navigation pane and click the Delimiters tab.
- Configure delimiters.
You can configure delimiters in either of the following ways. If you use both ways, the delimiters configured in the two ways will all take effect. - Common Delimiters: Click Edit and enter custom delimiters in the text box.
- ASCII Delimiters: Click Edit > Add ASCII Delimiter, and enter ASCII values by referring to ASCII Table.
+
+ - Preview the parsing result.
Enter log content in the text box and click Preview.
+ - Check whether the parsing result is correct. If it is correct, click Save.
You can click Reset to restore the default delimiters.
+
+
+
+ ASCII Table
+ Table 1 ASCII tableASCII Value
+ |
+Character
+ |
+ASCII Value
+ |
+Character
+ |
+ASCII Value
+ |
+Character
+ |
+ASCII Value
+ |
+Character
+ |
+
+
+0
+ |
+NUL (Null)
+ |
+32
+ |
+Space
+ |
+64
+ |
+@
+ |
+96
+ |
+`
+ |
+
+1
+ |
+SOH (Start of heading)
+ |
+33
+ |
+!
+ |
+65
+ |
+A
+ |
+97
+ |
+a
+ |
+
+2
+ |
+STX (Start of text)
+ |
+34
+ |
+"
+ |
+66
+ |
+B
+ |
+98
+ |
+b
+ |
+
+3
+ |
+ETX (End of text)
+ |
+35
+ |
+#
+ |
+67
+ |
+C
+ |
+99
+ |
+c
+ |
+
+4
+ |
+EOT (End of transmission)
+ |
+36
+ |
+$
+ |
+68
+ |
+D
+ |
+100
+ |
+d
+ |
+
+5
+ |
+ENQ (Enquiry)
+ |
+37
+ |
+%
+ |
+69
+ |
+E
+ |
+101
+ |
+e
+ |
+
+6
+ |
+ACK (Acknowledge)
+ |
+38
+ |
+&
+ |
+70
+ |
+F
+ |
+102
+ |
+f
+ |
+
+7
+ |
+BEL (Bell)
+ |
+39
+ |
+'
+ |
+71
+ |
+G
+ |
+103
+ |
+g
+ |
+
+8
+ |
+BS (Backspace)
+ |
+40
+ |
+(
+ |
+72
+ |
+H
+ |
+104
+ |
+h
+ |
+
+9
+ |
+HT (Horizontal tab)
+ |
+41
+ |
+)
+ |
+73
+ |
+I
+ |
+105
+ |
+i
+ |
+
+10
+ |
+LF (Line feed)
+ |
+42
+ |
+*
+ |
+74
+ |
+J
+ |
+106
+ |
+j
+ |
+
+11
+ |
+VT (Vertical tab)
+ |
+43
+ |
++
+ |
+75
+ |
+K
+ |
+107
+ |
+k
+ |
+
+12
+ |
+FF (Form feed)
+ |
+44
+ |
+,
+ |
+76
+ |
+L
+ |
+108
+ |
+l
+ |
+
+13
+ |
+CR (Carriage return)
+ |
+45
+ |
+-
+ |
+77
+ |
+M
+ |
+109
+ |
+m
+ |
+
+14
+ |
+SO (Shift out)
+ |
+46
+ |
+.
+ |
+78
+ |
+N
+ |
+110
+ |
+n
+ |
+
+15
+ |
+SI (Shift in)
+ |
+47
+ |
+/
+ |
+79
+ |
+O
+ |
+111
+ |
+o
+ |
+
+16
+ |
+DLE (Data link escape)
+ |
+48
+ |
+0
+ |
+80
+ |
+P
+ |
+112
+ |
+p
+ |
+
+17
+ |
+DC1 (Device control 1)
+ |
+49
+ |
+1
+ |
+81
+ |
+Q
+ |
+113
+ |
+q
+ |
+
+18
+ |
+DC2 (Device control 2)
+ |
+50
+ |
+2
+ |
+82
+ |
+R
+ |
+114
+ |
+r
+ |
+
+19
+ |
+DC3 (Device control 3)
+ |
+51
+ |
+3
+ |
+83
+ |
+S
+ |
+115
+ |
+s
+ |
+
+20
+ |
+DC4 (Device control 4)
+ |
+52
+ |
+4
+ |
+84
+ |
+T
+ |
+116
+ |
+t
+ |
+
+21
+ |
+NAK (Negative acknowledge)
+ |
+53
+ |
+5
+ |
+85
+ |
+U
+ |
+117
+ |
+u
+ |
+
+22
+ |
+SYN (Synchronous idle)
+ |
+54
+ |
+6
+ |
+86
+ |
+V
+ |
+118
+ |
+v
+ |
+
+23
+ |
+ETB (End of transmission block)
+ |
+55
+ |
+7
+ |
+87
+ |
+W
+ |
+119
+ |
+w
+ |
+
+24
+ |
+CAN (Cancel)
+ |
+56
+ |
+8
+ |
+88
+ |
+X
+ |
+120
+ |
+x
+ |
+
+25
+ |
+EM (End of medium)
+ |
+57
+ |
+9
+ |
+89
+ |
+Y
+ |
+121
+ |
+y
+ |
+
+26
+ |
+SUB (Substitute)
+ |
+58
+ |
+:
+ |
+90
+ |
+Z
+ |
+122
+ |
+z
+ |
+
+27
+ |
+ESC (Escape)
+ |
+59
+ |
+;
+ |
+91
+ |
+[
+ |
+123
+ |
+{
+ |
+
+28
+ |
+FS (File separator)
+ |
+60
+ |
+<
+ |
+92
+ |
+\
+ |
+124
+ |
+|
+ |
+
+29
+ |
+GS (Group separator)
+ |
+61
+ |
+=
+ |
+93
+ |
+]
+ |
+125
+ |
+}
+ |
+
+30
+ |
+RS (Record separator)
+ |
+62
+ |
+>
+ |
+94
+ |
+^
+ |
+126
+ |
+~
+ |
+
+31
+ |
+US (Unit separator)
+ |
+63
+ |
+?
+ |
+95
+ |
+_
+ |
+127
+ |
+DEL (Delete)
+ |
+
+
+
+
+
+
+
+
diff --git a/docs/lts/umn/lts_04_0057.html b/docs/lts/umn/lts_04_0057.html
new file mode 100644
index 00000000..f61200ca
--- /dev/null
+++ b/docs/lts/umn/lts_04_0057.html
@@ -0,0 +1,16 @@
+
+
+ Log Alarms
+
+
+
diff --git a/docs/lts/umn/lts_04_0058.html b/docs/lts/umn/lts_04_0058.html
index a36b20e3..518fc36a 100644
--- a/docs/lts/umn/lts_04_0058.html
+++ b/docs/lts/umn/lts_04_0058.html
@@ -4,17 +4,15 @@
diff --git a/docs/lts/umn/lts_04_0060.html b/docs/lts/umn/lts_04_0060.html
new file mode 100644
index 00000000..b531e0a9
--- /dev/null
+++ b/docs/lts/umn/lts_04_0060.html
@@ -0,0 +1,21 @@
+
+
+ Viewing Alarms in LTS
+ LTS allows you to configure keyword alarm rules to periodically query log data. When an alarm rule is met, an alarm will be reported. You can view the alarms on the LTS console.
+ PrerequisitesYou have created an alarm rule.
+
+ Procedure- Log in to the management console and choose Management & Deployment > Log Tank Service.
- Choose Alarms in the navigation pane.
- Click the Alarms tab. The alarms generated in 30 minutes from now and their trend charts are displayed by default.
- Set criteria to search for your target alarms.
- In the search box above the alarm list, select a log group, log stream, and alarm severity.
- Set a time range. By default, 30 minutes is specified (relative time from now).
There are three types of time range: relative time from now, relative time from last, and specified time. Select a time range as required. - From now: queries log data generated in a time range that ends with the current time, such as the previous 1, 5, or 15 minutes. For example, if the current time is 19:20:31 and 1 hour is selected as the relative time from now, the charts on the dashboard display the log data that is generated from 18:20:31 to 19:20:31.
- From last: queries log data generated in a time range that ends with the current time, such as the previous 1 or 15 minutes. For example, if the current time is 19:20:31 and 1 hour is selected as the relative time from last, the charts on the dashboard display the log data that is generated from 18:00:00 to 19:00:00.
- Specified: queries log data that is generated in a specified time range.
+
+
+
+ - Click
after you set the search criteria. The details and trend of the alarms that match the criteria will be displayed. - You can point to the Details column of an alarm on the Active Alarms tab to view the complete alarm details. Alternatively, click the name in the Alarm Name column of an alarm. Details about the alarm are displayed in the right panel that pops up.
After the reported fault is rectified, you can click the deletion button in the row that contains the corresponding alarm on the Active Alarms tab to clear the alarm. The cleared alarm will then be displayed on the Historical Alarms tab.
+If you have configured search criteria to filter alarms, you need to manually refresh the alarm list. To enable automatic refresh, click in the upper right corner and select Refresh Every 30s, Refresh Every 1m, or Refresh Every 5m from the drop-down list box. You can still manually refresh the alarm list when automatic refresh is enabled by selecting Refresh Now from the drop-down list box.
+
+
+
+
+
diff --git a/docs/lts/umn/lts_04_0062.html b/docs/lts/umn/lts_04_0062.html
new file mode 100644
index 00000000..ccef5906
--- /dev/null
+++ b/docs/lts/umn/lts_04_0062.html
@@ -0,0 +1,136 @@
+
+
+ Configuring Log Alarm Rules
+ You can set alarm rules based on keywords in log streams to monitor service status in real time. Currently, up to 200 keyword alarms can be created for each account.
+
+ Creating a Keyword Alarm RuleLTS allows you to collect statistics on log keywords in log streams and set alarm rules to monitor them. By checking the number of keyword occurrences in a specified period, you can have a real-time view of the service running.
+ - Log in to the management console and choose Management & Deployment > Log Tank Service.
- Choose Alarms in the navigation pane.
- Click the Alarm Rules tab.
- Click Create. The Create Alarm Rule right panel is displayed.
- Configure alarm rule parameters.
+ Table 1 Keyword alarm rule parametersCategory
+ |
+Parameter
+ |
+Description
+ |
+
+
+Basic Info
+ |
+Rule Name
+ |
+Name of the alarm rule. Enter 1 to 64 characters and do not start or end with a hyphen (-) or underscore (_). Only letters, digits, hyphens, and underscores are allowed.
+ NOTE: After an alarm rule is created, the rule name can be modified. After the modification, move the cursor over the rule name to view the new and original rule names. The original rule name cannot be changed.
+
+ |
+
+Description
+ |
+Brief description of the rule. Enter up to 64 characters.
+ |
+
+Statistical Analysis
+ |
+Statistics
+ |
+By keyword: applicable when keywords are used to search for and configure log alarms.
+ |
+
+Query Condition
+ |
+Log Group Name: Select a log group.
+ |
+
+Log Stream Name: Select a log stream. NOTE: If a log group contains more than one log stream, you can select multiple log streams when creating a keyword alarm rule.
+
+
+ |
+
+Query Time Range: Specify the query period of the statement. It is one period earlier than the current time. For example, if Query Time Range is set to one hour and the current time is 9:00, the period of the query statement is 8:00–9:00.
+- The value ranges from 1 to 60 in the unit of minutes.
- The value ranges from 1 to 24 in the unit of hours.
+ |
+
+Keywords: Enter keywords that you want LTS to monitor in logs. Exact and fuzzy matches are supported. A keyword is case-sensitive and contains up to 1,024 characters.
+ |
+
+Check Rule
+ |
+Configure a condition that will trigger the alarm.
+Matching Log Events: When the number of log events that contain the configured keywords reaches the specified value, an alarm is triggered. Four comparison operators are supported: greater than (>), greater than or equal to (>=), less than (<), and less than or equal to (<=).
+The number of queries refers to the Query Frequency set in Advanced Settings and the number of times the condition must be met to trigger the alarm. The number of queries must be greater than or equal to the number of times the condition must be met.
+ NOTE: - The alarm severity can be critical (default), major, minor, or info.
- Number of queries: 1–10
+
+ |
+
+Advanced Settings
+ |
+Query Frequency
+ |
+The options for this parameter are:
+- Hourly: The query is performed at the top of each hour.
- Daily: The query is run at a specific time every day.
- Weekly: The query is run at a specific time on a specific day every week.
- Custom interval: You can specify the interval from 1 minute to 60 minutes or from 1 hour to 24 hours. For example, if the current time is 9:00 and the Custom interval is set to 5 minutes, the first query is at 9:00, the second query is at 9:05, the third query is at 9:10, and so on.
NOTE: When the query time range is set to a value larger than 1 hour, the query frequency must be set to every 5 minutes or a lower frequency.
+
+ - CRON: CRON expressions support schedules down to the minute and use 24-hour format. Examples:
- 0/10 * * * *: The query starts from 00:00 and is performed every 10 minutes. That is, queries start at 00:00, 00:10, 00:20, 00:30, 00:40, 00:50, 01:00, and so on. For example, if the current time is 16:37, the next query is at 16:50.
- 0 0/5 * * *: The query starts from 00:00 and is performed every 5 hours at 00:00, 05:00, 10:00, 15:00, 20:00, and so on. For example, if the current time is 16:37, the next query is at 20:00.
- 0 14 * * *: The query is performed at 14:00 every day.
- 0 0 10 * *: The query is performed at 00:00 on the 10th day of every month.
+
+ |
+
+Advanced Settings
+ |
+Restores
+ |
+Configure a policy for sending an alarm clearance notification.
+If alarm clearance notification is enabled and the trigger condition has not been met for the specified number of statistical periods, an alarm clearance notification is sent.
+Number of last queries: 1–10
+ |
+
+Advanced Settings
+ |
+Notify When
+ |
+- Alarm triggered: Specify whether to send a notification when an alarm is triggered. If this option is enabled, a notification will be sent when the trigger condition is met.
- Alarm cleared: Specify whether to send a notification when an alarm is cleared. If this option is enabled, a notification will be sent when the recovery policy is met.
+ |
+
+Advanced Settings
+ |
+Frequency
+ |
+You can select Once, Every 5 minutes, Every 10 minutes, Every 15 minutes, Every 30 minutes, Every hour, Every 3 hours, or Every 6 hours to send alarms.
+Once indicates that a notification is sent once an alarm is generated. Every 10 minutes indicates that the minimum interval between two notifications is 10 minutes, preventing alarm storms.
+ |
+
+Advanced Settings
+ |
+Alarm Action Rules
+ |
+Select a desired rule from the drop-down list.
+If no rule is available, click Create Alarm Action Rule on the right.
+ |
+
+Advanced Settings
+ |
+Language
+ |
+Specify the language (Chinese (simplified) or English) in which alarms are sent.
+ |
+
+
+
+
+ - Click OK.
After an alarm rule is created, its status is Enabled by default. After the alarm rule is disabled, the alarm status is Disabled. After the alarm rule is disabled temporarily, the alarm status is Temporarily closed to May 30, 2023 16:21:24.000 GMT+08:00. (The time is for reference only.)
+ When the alarm rule is enabled, an alarm will be triggered if the alarm rule is met. When it is disabled, an alarm will not be triggered even if the alarm rule is met.
+
+
+
+ Follow-up Operations on Alarm Rules- You can perform the following operations on a single alarm rule.
Modifying an alarm rule: Click in the Operation column of the row that contains the target alarm rule. On the Modify Alarm Rule page displayed, modify the rule name, query condition , and check rule, and click OK.
+Enabling an alarm rule: Click in the Operation column of the row that contains the target alarm rule. (The enabling button is displayed only after the alarm rule is disabled.)
+Disabling an alarm rule: Click in the Operation column of the row that contains the target alarm rule. (The disabling button is displayed only after the alarm rule is enabled.)
+Temporarily disabling the alarm rule: Click in the Operation column of the row that contains the target alarm rule and set the end time for temporarily disabling the alarm rule.
+Copying an alarm rule: Click in the Operation column of the row that contains the target alarm rule.
+Deleting an alarm rule: Click in the Operation column of the row that contains the target alarm rule, and click OK.
+ - After selecting multiple alarm rules, you can perform the following operations on the alarms: Open, Close, Disable Temporarily, Re-Enable, Enable Clearance, Disable Clearance, Delete, and Export.
- You can move the cursor to the rule name to view both the new and original names after modification. The original rule name cannot be changed.
+
+
+
+
diff --git a/docs/lts/umn/lts_04_0105.html b/docs/lts/umn/lts_04_0105.html
index ccf41256..8d24bc70 100644
--- a/docs/lts/umn/lts_04_0105.html
+++ b/docs/lts/umn/lts_04_0105.html
@@ -1,12 +1,12 @@
- Collecting Logs from Cloud Services
+ Ingesting Cloud Service Logs to LTS
diff --git a/docs/lts/umn/lts_04_0511.html b/docs/lts/umn/lts_04_0511.html
index 654b8d23..b6408d0e 100644
--- a/docs/lts/umn/lts_04_0511.html
+++ b/docs/lts/umn/lts_04_0511.html
@@ -1,160 +1,175 @@
- Collecting Logs from CCE
- LTS can collect logs from Cloud Container Engine (CCE).
- Prerequisites
+ Ingesting CCE Application Logs to LTS
+ CCE provides highly scalable, high-performance, enterprise-class Kubernetes clusters. With CCE, you can easily deploy, manage, and scale containerized applications.
+ After ingesting CCE logs to LTS, you can centrally manage and analyze them and visualize log reports on the LTS console. This helps you better monitor and manage containerized application running, promptly detect container issues, and improve container performance and reliability.
+ Perform the following steps to complete the ingestion configuration:
+ - Step 1: Select a Log Stream
- Step 2: Check Dependencies
- Step 3: (Optional) Select a Host Group
- Step 4: Configure the Collection
- Step: Configure Log Structuring
- Step 5: Configure Indexing
- Step 6: Complete the Ingestion Configuration
+ To collect logs from multiple scenarios, set multiple ingestion configurations in a batch.
+ Prerequisites- ICAgent has been installed in the CCE cluster and a host group with custom identifiers has been created for related nodes. The system will automatically check these configurations and make necessary corrections when CCE logs are ingested to LTS.
- If you use AOM 2.0 for the first time, authorize it by referring to . Then, log in to the AOM 2.0 console, grant AOM 2.0 the permission to access data of cloud services, such as LTS and CCE, by referring to .
- On the Hosts page, select CCE Clusters, select the target cluster in the search box, and click Upgrade ICAgent. For details, see Upgrading ICAgent.
+
+ - You have disabled Output to AOM.
- |
---|
|
---|
|
---|
|
---|