diff --git a/docs/lts/umn/.placeholder b/docs/lts/umn/.placeholder
deleted file mode 100644
index e69de29b..00000000
diff --git a/docs/lts/umn/ALL_META.TXT.json b/docs/lts/umn/ALL_META.TXT.json
new file mode 100644
index 00000000..c668ea15
--- /dev/null
+++ b/docs/lts/umn/ALL_META.TXT.json
@@ -0,0 +1,262 @@
+[
+ {
+ "uri":"lts_01_0001.html",
+ "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",
+ "title":"Service Overview",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_01_0002.html",
+ "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 ",
+ "doc_type":"productdesc",
+ "kw":"Introduction,Service Overview,User Guide",
+ "title":"Introduction",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_01_0003.html",
+ "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",
+ "doc_type":"usermanual",
+ "kw":"Basic Concepts,Service Overview,User Guide",
+ "title":"Basic Concepts",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_01_0004.html",
+ "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",
+ "doc_type":"productdesc",
+ "kw":"Basic Functions,Service Overview,User Guide",
+ "title":"Basic Functions",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_01_0005.html",
+ "product_code":"lts",
+ "code":"5",
+ "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",
+ "doc_type":"productdesc",
+ "kw":"Related Services,Service Overview,User Guide",
+ "title":"Related Services",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_01_0008.html",
+ "product_code":"lts",
+ "code":"6",
+ "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",
+ "title":"Getting Started",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_01_0009.html",
+ "product_code":"lts",
+ "code":"7",
+ "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",
+ "doc_type":"usermanual",
+ "kw":"Configuring the VPC Flow Log Function,Getting Started,User Guide",
+ "title":"Configuring the VPC Flow Log Function",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_01_0010.html",
+ "product_code":"lts",
+ "code":"8",
+ "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",
+ "doc_type":"usermanual",
+ "kw":"Configuring CTS to Upload Traces to LTS,Getting Started,User Guide",
+ "title":"Configuring CTS to Upload Traces to LTS",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0002.html",
+ "product_code":"",
+ "code":"9",
+ "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",
+ "title":"Log Management",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0003.html",
+ "product_code":"",
+ "code":"10",
+ "des":"A log group is a group of log streams which share the same log retention settings. Up to 100 log groups can be created for a single account.Log in to the LTS console, cho",
+ "doc_type":"",
+ "kw":"Managing Log Groups,Log Management,User Guide",
+ "title":"Managing Log Groups",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0004.html",
+ "product_code":"",
+ "code":"11",
+ "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",
+ "doc_type":"",
+ "kw":"Managing Log Streams,Log Management,User Guide",
+ "title":"Managing Log Streams",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0005.html",
+ "product_code":"lts",
+ "code":"12",
+ "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",
+ "doc_type":"usermanual",
+ "kw":"Configuring Log Collection Rules,Log Management,User Guide",
+ "title":"Configuring Log Collection Rules",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0007.html",
+ "product_code":"",
+ "code":"13",
+ "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 View",
+ "title":"Log View",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0008.html",
+ "product_code":"",
+ "code":"14",
+ "des":"You can view the logs reported to the LTS console in real time.You have created log groups and log streams.You have installed ICAgent.You have configured log collection r",
+ "doc_type":"",
+ "kw":"Viewing Real-Time Logs,Log View,User Guide",
+ "title":"Viewing Real-Time Logs",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0009.html",
+ "product_code":"",
+ "code":"15",
+ "des":"Follow the directions below to search logs by keyword and time range:On the LTS console, click Log Management.In the log group list, click the name of a log group.In the ",
+ "doc_type":"",
+ "kw":"Log Search,Log View,User Guide",
+ "title":"Log Search",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0010.html",
+ "product_code":"",
+ "code":"16",
+ "des":"To search for logs using a keyword repeatedly, perform the following operations to configure quick search.Log in to the LTS console and choose Log Management.In the log g",
+ "doc_type":"",
+ "kw":"Quick Search,Log View,User Guide",
+ "title":"Quick Search",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0041.html",
+ "product_code":"",
+ "code":"17",
+ "des":"You can transfer logs to OBS to keep logs for a long time.Local log files are cleared periodically, but the logs transferred to OBS will not be affected.To transfer logs,",
+ "doc_type":"",
+ "kw":"Log Transfer,User Guide",
+ "title":"Log Transfer",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0012.html",
+ "product_code":"lts",
+ "code":"18",
+ "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":"Agent Management",
+ "title":"Agent Management",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_02_0013.html",
+ "product_code":"",
+ "code":"19",
+ "des":"ICAgent is a log collection tool for LTS. If you use LTS to collect logs from a host running Linux OS, you need to install ICAgent on the host.Ensure that the time and ti",
+ "doc_type":"",
+ "kw":"Installing ICAgent (Linux),Agent Management,User Guide",
+ "title":"Installing ICAgent (Linux)",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_02_0014.html",
+ "product_code":"",
+ "code":"20",
+ "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",
+ "doc_type":"",
+ "kw":"Upgrading ICAgent,Agent Management,User Guide",
+ "title":"Upgrading ICAgent",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_02_0015.html",
+ "product_code":"",
+ "code":"21",
+ "des":"If ICAgent is uninstalled from a host, log collection will be affected. Exercise caution when performing this operation.Uninstalling ICAgent does not delete the installat",
+ "doc_type":"",
+ "kw":"Uninstalling ICAgent,Agent Management,User Guide",
+ "title":"Uninstalling ICAgent",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0013.html",
+ "product_code":"lts",
+ "code":"22",
+ "des":"The following table lists the ICAgent statuses.",
+ "doc_type":"usermanual",
+ "kw":"ICAgent Statuses,Agent Management,User Guide",
+ "title":"ICAgent Statuses",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_04_0017.html",
+ "product_code":"",
+ "code":"23",
+ "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":"Appendixes",
+ "title":"Appendixes",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_03_0015.html",
+ "product_code":"lts",
+ "code":"24",
+ "des":"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 en",
+ "doc_type":"usermanual",
+ "kw":"How Do I Obtain an AK/SK Pair?,Appendixes,User Guide",
+ "title":"How Do I Obtain an AK/SK Pair?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_03_0002.html",
+ "product_code":"lts",
+ "code":"25",
+ "des":"When installing ICAgent, you can create an IAM agency, and ICAgent will automatically obtain an AK/SK pair and generate the ICAgent installation command.Log in to the con",
+ "doc_type":"usermanual",
+ "kw":"How Do I Install ICAgent by Creating an Agency?,Appendixes,User Guide",
+ "title":"How Do I Install ICAgent by Creating an Agency?",
+ "githuburl":""
+ },
+ {
+ "uri":"lts_01_0033.html",
+ "product_code":"lts",
+ "code":"26",
+ "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",
+ "title":"Change History",
+ "githuburl":""
+ }
+]
\ No newline at end of file
diff --git a/docs/lts/umn/CLASS.TXT.json b/docs/lts/umn/CLASS.TXT.json
new file mode 100644
index 00000000..6419aa4a
--- /dev/null
+++ b/docs/lts/umn/CLASS.TXT.json
@@ -0,0 +1,236 @@
+[
+ {
+ "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":"Service Overview",
+ "uri":"lts_01_0001.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "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 ",
+ "product_code":"lts",
+ "title":"Introduction",
+ "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",
+ "product_code":"lts",
+ "title":"Basic Concepts",
+ "uri":"lts_01_0003.html",
+ "doc_type":"usermanual",
+ "p_code":"1",
+ "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",
+ "product_code":"lts",
+ "title":"Basic Functions",
+ "uri":"lts_01_0004.html",
+ "doc_type":"usermanual",
+ "p_code":"1",
+ "code":"4"
+ },
+ {
+ "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",
+ "product_code":"lts",
+ "title":"Related Services",
+ "uri":"lts_01_0005.html",
+ "doc_type":"usermanual",
+ "p_code":"1",
+ "code":"5"
+ },
+ {
+ "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":"Getting Started",
+ "uri":"lts_01_0008.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "code":"6"
+ },
+ {
+ "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",
+ "product_code":"lts",
+ "title":"Configuring the VPC Flow Log Function",
+ "uri":"lts_01_0009.html",
+ "doc_type":"usermanual",
+ "p_code":"6",
+ "code":"7"
+ },
+ {
+ "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",
+ "product_code":"lts",
+ "title":"Configuring CTS to Upload Traces to LTS",
+ "uri":"lts_01_0010.html",
+ "doc_type":"usermanual",
+ "p_code":"6",
+ "code":"8"
+ },
+ {
+ "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 Management",
+ "uri":"lts_04_0002.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "code":"9"
+ },
+ {
+ "desc":"A log group is a group of log streams which share the same log retention settings. Up to 100 log groups can be created for a single account.Log in to the LTS console, cho",
+ "product_code":"lts",
+ "title":"Managing Log Groups",
+ "uri":"lts_04_0003.html",
+ "doc_type":"usermanual",
+ "p_code":"9",
+ "code":"10"
+ },
+ {
+ "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",
+ "product_code":"lts",
+ "title":"Managing Log Streams",
+ "uri":"lts_04_0004.html",
+ "doc_type":"usermanual",
+ "p_code":"9",
+ "code":"11"
+ },
+ {
+ "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",
+ "product_code":"lts",
+ "title":"Configuring Log Collection Rules",
+ "uri":"lts_04_0005.html",
+ "doc_type":"usermanual",
+ "p_code":"9",
+ "code":"12"
+ },
+ {
+ "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 View",
+ "uri":"lts_04_0007.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "code":"13"
+ },
+ {
+ "desc":"You can view the logs reported to the LTS console in real time.You have created log groups and log streams.You have installed ICAgent.You have configured log collection r",
+ "product_code":"lts",
+ "title":"Viewing Real-Time Logs",
+ "uri":"lts_04_0008.html",
+ "doc_type":"usermanual",
+ "p_code":"13",
+ "code":"14"
+ },
+ {
+ "desc":"Follow the directions below to search logs by keyword and time range:On the LTS console, click Log Management.In the log group list, click the name of a log group.In the ",
+ "product_code":"lts",
+ "title":"Log Search",
+ "uri":"lts_04_0009.html",
+ "doc_type":"usermanual",
+ "p_code":"13",
+ "code":"15"
+ },
+ {
+ "desc":"To search for logs using a keyword repeatedly, perform the following operations to configure quick search.Log in to the LTS console and choose Log Management.In the log g",
+ "product_code":"lts",
+ "title":"Quick Search",
+ "uri":"lts_04_0010.html",
+ "doc_type":"usermanual",
+ "p_code":"13",
+ "code":"16"
+ },
+ {
+ "desc":"You can transfer logs to OBS to keep logs for a long time.Local log files are cleared periodically, but the logs transferred to OBS will not be affected.To transfer logs,",
+ "product_code":"lts",
+ "title":"Log Transfer",
+ "uri":"lts_04_0041.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "code":"17"
+ },
+ {
+ "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":"Agent Management",
+ "uri":"lts_04_0012.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "code":"18"
+ },
+ {
+ "desc":"ICAgent is a log collection tool for LTS. If you use LTS to collect logs from a host running Linux OS, you need to install ICAgent on the host.Ensure that the time and ti",
+ "product_code":"lts",
+ "title":"Installing ICAgent (Linux)",
+ "uri":"lts_02_0013.html",
+ "doc_type":"usermanual",
+ "p_code":"18",
+ "code":"19"
+ },
+ {
+ "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":"18",
+ "code":"20"
+ },
+ {
+ "desc":"If ICAgent is uninstalled from a host, log collection will be affected. Exercise caution when performing this operation.Uninstalling ICAgent does not delete the installat",
+ "product_code":"lts",
+ "title":"Uninstalling ICAgent",
+ "uri":"lts_02_0015.html",
+ "doc_type":"usermanual",
+ "p_code":"18",
+ "code":"21"
+ },
+ {
+ "desc":"The following table lists the ICAgent statuses.",
+ "product_code":"lts",
+ "title":"ICAgent Statuses",
+ "uri":"lts_04_0013.html",
+ "doc_type":"usermanual",
+ "p_code":"18",
+ "code":"22"
+ },
+ {
+ "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":"Appendixes",
+ "uri":"lts_04_0017.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "code":"23"
+ },
+ {
+ "desc":"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 en",
+ "product_code":"lts",
+ "title":"How Do I Obtain an AK/SK Pair?",
+ "uri":"lts_03_0015.html",
+ "doc_type":"usermanual",
+ "p_code":"23",
+ "code":"24"
+ },
+ {
+ "desc":"When installing ICAgent, you can create an IAM agency, and ICAgent will automatically obtain an AK/SK pair and generate the ICAgent installation command.Log in to the con",
+ "product_code":"lts",
+ "title":"How Do I Install ICAgent by Creating an Agency?",
+ "uri":"lts_03_0002.html",
+ "doc_type":"usermanual",
+ "p_code":"23",
+ "code":"25"
+ },
+ {
+ "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":"Change History",
+ "uri":"lts_01_0033.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "code":"26"
+ }
+]
\ No newline at end of file
diff --git a/docs/lts/umn/PARAMETERS.txt b/docs/lts/umn/PARAMETERS.txt
new file mode 100644
index 00000000..6da8d5f0
--- /dev/null
+++ b/docs/lts/umn/PARAMETERS.txt
@@ -0,0 +1,3 @@
+version=""
+language="en-us"
+type=""
\ No newline at end of file
diff --git a/docs/lts/umn/en-us_image_0000001190616042.png b/docs/lts/umn/en-us_image_0000001190616042.png
new file mode 100644
index 00000000..584cb028
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001190616042.png differ
diff --git a/docs/lts/umn/en-us_image_0000001368010788.png b/docs/lts/umn/en-us_image_0000001368010788.png
new file mode 100644
index 00000000..796e7400
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001368010788.png differ
diff --git a/docs/lts/umn/en-us_image_0000001368172808.png b/docs/lts/umn/en-us_image_0000001368172808.png
new file mode 100644
index 00000000..69c4544a
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001368172808.png differ
diff --git a/docs/lts/umn/en-us_image_0000001419010601.png b/docs/lts/umn/en-us_image_0000001419010601.png
new file mode 100644
index 00000000..3099d744
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001419010601.png differ
diff --git a/docs/lts/umn/en-us_image_0000001419012101.png b/docs/lts/umn/en-us_image_0000001419012101.png
new file mode 100644
index 00000000..528d7b2d
Binary files /dev/null and b/docs/lts/umn/en-us_image_0000001419012101.png differ
diff --git a/docs/lts/umn/en-us_image_0178020286.png b/docs/lts/umn/en-us_image_0178020286.png
new file mode 100644
index 00000000..2df583a1
Binary files /dev/null and b/docs/lts/umn/en-us_image_0178020286.png differ
diff --git a/docs/lts/umn/en-us_image_0224007615.png b/docs/lts/umn/en-us_image_0224007615.png
new file mode 100644
index 00000000..9c2cc1b3
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007615.png differ
diff --git a/docs/lts/umn/en-us_image_0224007618.png b/docs/lts/umn/en-us_image_0224007618.png
new file mode 100644
index 00000000..f3ec3896
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007618.png differ
diff --git a/docs/lts/umn/en-us_image_0224007629.png b/docs/lts/umn/en-us_image_0224007629.png
new file mode 100644
index 00000000..add263ef
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007629.png differ
diff --git a/docs/lts/umn/en-us_image_0224007642.png b/docs/lts/umn/en-us_image_0224007642.png
new file mode 100644
index 00000000..a82a1885
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007642.png differ
diff --git a/docs/lts/umn/en-us_image_0224007643.png b/docs/lts/umn/en-us_image_0224007643.png
new file mode 100644
index 00000000..96735ebf
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007643.png differ
diff --git a/docs/lts/umn/en-us_image_0224007651.png b/docs/lts/umn/en-us_image_0224007651.png
new file mode 100644
index 00000000..17ffb3e6
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007651.png differ
diff --git a/docs/lts/umn/en-us_image_0224007663.png b/docs/lts/umn/en-us_image_0224007663.png
new file mode 100644
index 00000000..b62af39d
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007663.png differ
diff --git a/docs/lts/umn/en-us_image_0224007665.png b/docs/lts/umn/en-us_image_0224007665.png
new file mode 100644
index 00000000..929bab9a
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007665.png differ
diff --git a/docs/lts/umn/en-us_image_0224007675.png b/docs/lts/umn/en-us_image_0224007675.png
new file mode 100644
index 00000000..20b8afa5
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007675.png differ
diff --git a/docs/lts/umn/en-us_image_0224007681.png b/docs/lts/umn/en-us_image_0224007681.png
new file mode 100644
index 00000000..7da509bf
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007681.png differ
diff --git a/docs/lts/umn/en-us_image_0224007683.png b/docs/lts/umn/en-us_image_0224007683.png
new file mode 100644
index 00000000..addc5197
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007683.png differ
diff --git a/docs/lts/umn/en-us_image_0224007684.png b/docs/lts/umn/en-us_image_0224007684.png
new file mode 100644
index 00000000..1e55d0de
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007684.png differ
diff --git a/docs/lts/umn/en-us_image_0224007690.png b/docs/lts/umn/en-us_image_0224007690.png
new file mode 100644
index 00000000..f9d5799a
Binary files /dev/null and b/docs/lts/umn/en-us_image_0224007690.png differ
diff --git a/docs/lts/umn/lts_01_0001.html b/docs/lts/umn/lts_01_0001.html
new file mode 100644
index 00000000..dcccf665
--- /dev/null
+++ b/docs/lts/umn/lts_01_0001.html
@@ -0,0 +1,17 @@
+
+
+Service Overview
+
+
+
diff --git a/docs/lts/umn/lts_01_0002.html b/docs/lts/umn/lts_01_0002.html
new file mode 100644
index 00000000..1ec37418
--- /dev/null
+++ b/docs/lts/umn/lts_01_0002.html
@@ -0,0 +1,12 @@
+
+
+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
+
Basic Concepts
+Log Groups
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.
+
+
Log Streams
Up 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.
+
+
ICAgent
ICAgent 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.
+
+
Basic Functions
+Real-time Log Collection
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.
+
+
Log Query and Real-Time Analysis
You 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 Transfer
Reported 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.
+
+
Related Services
+VPC
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 Cards (NICs) logs are uploaded to LTS for preview, search, and storage.
+
+
OBS
Object Storage Service (OBS) is an object-based massive storage service. Logs can be transferred to OBS buckets for long-term storage.
+
+
IAM
Identity and Access Management (IAM) provides identity authentication and permissions management. LTS calls IAM APIs to obtain administrator permissions for log management.
+
+
CTS
If 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.
+
+
WAF
You 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.
+
+
ELB
You 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 for details on HTTP and HTTPS requests sent to your load balancer and perform log analysis.
+
+
Getting Started
+
+
+
diff --git a/docs/lts/umn/lts_01_0009.html b/docs/lts/umn/lts_01_0009.html
new file mode 100644
index 00000000..2266d75e
--- /dev/null
+++ b/docs/lts/umn/lts_01_0009.html
@@ -0,0 +1,271 @@
+
+
+Configuring the VPC Flow Log Function
+Scenarios
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 network attacks, and determine whether security groups and firewall rules need to be modified.
+
To obtain traffic details of VPC Network Interface Cards (NICs), you can enable Log Tank Service (LTS) and view logs about the NICs on the LTS console.
+
This section describes how to create a VPC flow log to report logs to LTS.
+
+
Constraints
- A VPC is available.
- Currently, only C3, CC3, and P2 ECSs are supported.
+
+
Operation Process
Figure 1 Flowchart
+
Operations in Figure 1 are performed on different consoles:
+
- LTS console: Creating a log group and creating a log topic.
- VPC console: Creating a VPC flow log and viewing the flow log.
+
+
Creating a Log Group
- 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 > 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 or end with a period.
+ |
+lts-group-wule
+ |
+
+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 Topic
To create a log topic in the log group, perform the following operations:
+
- 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 > Log Tank Service.
- In the log group list, click the name of the target log group.
Figure 4 Log topic list
+ - On the displayed page, click Create Log Topic.
Figure 5 Creating a log topic
+ - On the displayed page, enter a name.
+
Table 2 Parameter descriptionParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+Log Topic Name
+ |
+Specifies the log topic name. The name must be unique in a log group. 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 or end with a period.
+ |
+LogTopic1
+ |
+
+
+
+
- Click OK.
+
+
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 type of resources whose traffic is to be logged. Currently, Resource Type can only be NIC.
+ |
+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 topic 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 Log
The 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 enter a keyword on the log topic details page on the LTS console to search for flow log records.
+
+
+
Configuring CTS to Upload Traces to LTS
+Scenarios
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.
+
+
Operation process
Figure 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 CTS
You 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 Tracker
You can perform the following operations to enable the trace analysis function, thus reporting CTS traces to LTS.
+
- On the Tracker page, click Configure in the Operation column.
The Configure Tracker page is displayed.
+ - On the displayed page, enable Trace Analysis.
Figure 3 Configuring a tracker
+
During CTS trace reporting, the system automatically creates a log group and a log topic on the LTS console.
+
- Click OK.
+
+
Viewing Logs in Real Time
You 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 the name of the target log group.
- In the log topic list, locate the target log topic and click View in the Operation column.
Figure 4 Viewing logs in real time
+Logs are reported to LTS every 10 minutes. In the log display area, you may wait for at most 10 minutes to view the logs.
+In addition, you can customize log display by clicking
Clear,
Pause, or
Close in the upper right corner.
Figure 5 Log display area
+
+
+
+
Change History
+
+
Released On
+ |
+Description
+ |
+
|---|
+
+2022-09-02
+ |
+The modification is as follows:
+- Modified description of restrictions in section "Managing Log Groups."
- Modified description of restrictions in section "Managing Log Streams."
- Modified description of restrictions in section "Quick Search."
+ |
+
+2021-01-25
+ |
+The modification is as follows:
+Updated descriptions of initial installation in section "Installing ICAgent".
+ |
+
+2020-09-03
+ |
+The modification is as follows:
+Adjusted the document structure and content based on console changes.
+ |
+
+2019-11-26
+ |
+The modification is as follows:
+Added supported ECS types in section "Configuring the VPC Flow Log Function".
+ |
+
+2019-08-07
+ |
+The modifications are as follows:
+- Added descriptions of how to disable or modify log subscriptions in section "Log Subscription".
- Added descriptions of access keys in section "Log Subscription".
+ |
+
+2019-05-23
+ |
+The modification is as follows:
+Added descriptions of how to enable and disable the search function in section "Searching for Logs by Keyword".
+ |
+
+2019-05-09
+ |
+The modification is as follows:
+Accepted in OTC-4.0/Agile-06.2019
+ |
+
+2019-04-30
+ |
+The modifications are as follows:
+- Each user can create up to 100 log groups.
- Up to 100 log streams can be created in a log group.
- Optimized descriptions in section "Searching for Logs by Keyword".
+ |
+
+2019-04-12
+ |
+The modifications are as follows:
+Updated descriptions in section "Searching for Logs by Keyword".
+- Optimized the examples of fuzzy search.
- Optimized the format of key-value pairs. The keys include host_name:, ip:, path:, and time:.
+ |
+
+2019-02-22
+ |
+The modification is as follows:
+Updated descriptions and screenshots in section "Configuring the VPC Flow Log Function".
+ |
+
+2019-02-15
+ |
+This issue is the first official release.
+ |
+
+
+
+
+
Installing ICAgent (Linux)
+ICAgent is a log collection tool for LTS. If you use LTS to collect logs from a host running Linux OS, you need to install ICAgent on the host.
+
Prerequisites
Ensure 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.
+
+
+
Installation Methods
There 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
+ |
+When ICAgent has already been installed on one host but needs to be installed on multiple hosts, you can use this method.
+ |
+
+
+
+
+
+
Initial Installation
- Log in to the LTS console and choose Agent Management in the navigation pane on the left.
- Click Install ICAgent.
+ - Select an 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 Agent Management page of the LTS console.
- If the installation fails, uninstall ICAgent and reinstall it. If reinstallation fails, contact technical support.
+
+
+
+
Inherited Installation
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.
- Ensure that user root can run SSH or SCP commands on the host where ICAgent has been installed to remotely communicate with the 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 Agent Management page of the LTS console.
- If the installation fails, uninstall ICAgent and reinstall it. If reinstallation fails, contact technical support.
+
+
+
+
Batch Inherited Installation
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.
+
+
+
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:
+
192.168.2.109 Password of the host where ICAgent is to be installed
+
192.168.0.139 Password of the host where ICAgent is to be installed
+
- 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 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.
+ - Choose Agent Management in the LTS navigation pane to view the ICAgent status. For details, see ICAgent Status.
+
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.
+
Procedure
- Log in to the LTS console and choose Agent Management in the navigation pane on the left.
- Select one or more hosts where ICAgent is to be upgraded, and click Upgrade ICAgent.
- In the Upgrade ICAgent dialog box, click Yes.
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 status 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 ICAgent
+If ICAgent is uninstalled from a host, log collection will be affected. Exercise caution when performing this operation.
+
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 Agent Management in the navigation pane on the left.
- Select one or more hosts where ICAgent is to be uninstalled and click Uninstall ICAgent.
- In the Uninstall ICAgent dialog box, click Yes.
The uninstallation begins. This process takes about a minute.
+When the ICAgent status changes from Uninstalling to Uninstalled, the ICAgent uninstallation has completed.
+ 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 ICAgent
You can uninstall ICAgent on one host remotely from another host.
+
- On a host that has ICAgent installed, run the following command. x.x.x.x indicates the IP address of the host you wish 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 for the remote host.
- If the Expect tool has been installed on the host you are running the command from, ICAgent will be uninstalled from the remote host after the command is executed. If the Expect tool has not been installed, you will need to enter the password of user root for the remote host 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
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 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)
+
- 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/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 Agent Management in the LTS navigation pane to view the ICAgent status of the host.
+
+
How Do I Install ICAgent by Creating an Agency?
+When installing ICAgent, you can create an IAM agency, and ICAgent will automatically obtain an AK/SK pair and generate the ICAgent installation command.
+
Procedure
- Log in to the console and choose Service List > Management & Deployment > Identity and Access Management.
- Choose Agencies in the navigation pane on the left.
- Click Create Agency in the upper right corner and set parameters as follows:
+
Table 1 Agency parametersParameter
+ |
+Description
+ |
+
|---|
+
+Agency Name
+ |
+Set the agency name. For example, lts_ecm_trust.
+ |
+
+Agency Type
+ |
+Select Cloud service.
+ |
+
+Cloud Service
+ |
+Select Elastic Cloud Server (ECS) and Bare Metal Server (BMS).
+ |
+
+Validity Period
+ |
+Select Unlimited.
+ |
+
+Description
+ |
+(Optional) Provide details about the agency.
+ |
+
+Permissions
+ |
+- In the Permissions area, click Assign Permissions.
- Search for LTS Admin and APM Administrator and select them.
- Click OK on the Assign Permissions page.
+ |
+
+
+
+
- Click OK on the Create Agency page.
+
+
Making an Agency Effective
- Choose Service List > Computing > Elastic Cloud Server.
- Click the ECS where ICAgent is installed. The ECS details page is displayed.
- Select the created agency and confirm the configuration to make the agency effective.
- (Optional) If you want to set an agency when you are purchasing an ECS, do as follows: Click Buy ECS on the ECS console. In the Configure Advanced Settings step, set Advanced Options to Configure now and select an agency from the Agency drop-down list. Set the other parameters and click Next.
+
+
How Do I Obtain an AK/SK Pair?
+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.
+
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.
+
+
+
Log Management
+
+
+
diff --git a/docs/lts/umn/lts_04_0003.html b/docs/lts/umn/lts_04_0003.html
new file mode 100644
index 00000000..dac79d90
--- /dev/null
+++ b/docs/lts/umn/lts_04_0003.html
@@ -0,0 +1,25 @@
+
+
+Managing Log Groups
+A log group is a group of log streams which share the same log retention settings. Up to 100 log groups can be created for a single account.
+
Creating a Log Group
- 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.
+ - 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 (_), and cannot 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.
+
+ - Log retention duration is 7 days by default and cannot be modified.
+
+ - Click OK.
- In the log group list on the Log Management page, you can view details of the log group, including log group name, log retention duration, creation time, and creation type.
+
+
Deleting a Log Group
You 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 Yes.
+
+
+
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.
+
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.
+
Prerequisites
You have created a log group.
+
+
Creating a Log Stream
- On the LTS console, click the name of the created log group.
- Click Create Log Stream in the upper left corner, 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 (_), and cannot end with a period (.).
- Can contain 1 to 64 characters.
+
+ 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.
On the log stream page, you can view details of the log stream, including log stream name, creation time, and creation type.
+
+ 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.
+
+
+
+
Deleting a Log Stream
You 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 Delete in the Operation column.
- Enter DELETE and click Yes.
+
+
+
Configuring Log Collection Rules
+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 on the LTS console in real time.
+
Prerequisites
- You have created a log group.
- You have created a log stream.
- You have installed ICAgent.
+
+
Procedure
- Log in to the LTS console, choose Log Management in the navigation pane on the left, and click the name of a log group.
- Click the name of a log stream. Logs will be collected to this log stream.
- Click Collection Configuration in the navigation pane. The collection configuration details page is displayed.
- Click Add Path.
- In the Add Host step, select the host whose logs you want to collect and click Next.
- In the Configure Collection Path step, add the path of logs you want to collect.
- Logs can be collected recursively. A double asterisk (**) can represent up to 5 directory levels in a path.
For example, /var/logs/**/a.log will match the following logs:
+/var/logs/1/a.log
+/var/logs/1/2/a.log
+/var/logs/1/2/3/a.log
+/var/logs/1/2/3/4/a.log
+/var/logs/1/2/3/4/5/a.log
+ - /1/2/3/4/5/ indicates the 5 levels of directories under the /var/logs directory. All the a.log files found in all these levels of directories will be collected.
- Only one double asterisk (**) can be contained in a collection path. For example, /var/logs/**/a.log is acceptable but /opt/test/**/log/** is not.
- A collection path cannot begin with a double asterisk (**), such as /**/test to avoid collecting system files.
+
+ - You can use an asterisk (*) as a wildcard for fuzzy match. The wildcard (*) can represent one or more characters of a directory or file name.
+
- If the collection path is set to a directory (such as /var/logs/), only .log, .trace, and .out files in the directory are collected.
If the collection path is set to a file name, the corresponding file is collected. Only text files can be collected.
+
+ - Ensure that sensitive information is not collected.
- System logs are not collected by LTS by default. If you need to collect system logs, configure a corresponding collection path.
- LTS cannot collect logs of PostgreSQL (database) instances. It only collects logs of ECS (host) instances.
- A collection path can be configured only once. It means that a path of a host cannot be added for different log streams. Otherwise, log collection may be abnormal.
- If a collection path of a host has been configured in Application Operations Management (AOM), do not configure the path in LTS. If a path is configured in both AOM and LTS, only the path that is configured later takes effect.
+
+ - Click Next: Configure Collection.
+
Table 1 Log collection settingsParameter
+ |
+Description
+ |
+
|---|
+
+Log Format
+ |
+- Single-line: Each log line is displayed as a single log event.
- Multi-line: Multiple lines of exception log events can be displayed as a single log event. This is helpful when you check logs to locate problems.
+ |
+
+Log Time
+ |
+System time: log collection time by default. It is displayed at the beginning of each log event.
+ NOTE: Log printing time is the time when logs are printed. Log collection time is the time when logs are collected and sent by ICAgent to LTS.
+ ICAgent collects and sends logs to LTS with an interval of 1 second.
+
+ |
+
+Time wildcard: You can set a time wildcard so that ICAgent will look for the log printing time as the beginning of a log event.
+- If the time format in a log event is 2019-01-01 23:59:59, the time wildcard should be set to YYYY-MM-DD hh:mm:ss.
- If the time format in a log event is 19-1-1 23:59:59, the time wildcard should be set to YY-M-D hh:mm:ss.
+ NOTE: If a log event does not contain year information, ICAgent regards it as printed in the current year.
+
+Example:
+YY - year (19)
+YYYY - year (2019)
+M - month (1)
+MM - month (01)
+D - day (1)
+DD - day (01)
+hh - hours (23)
+mm - minutes (59)
+ss - seconds (59)
+hpm - hours (03PM)
+h:mmpm - hours:minutes (03:04PM)
+h:mm:sspm - hours:minutes:seconds (03:04:05PM)
+hh:mm:ss ZZZZ (16:05:06 +0100)
+hh:mm:ss ZZZ (16:05:06 CET)
+hh:mm:ss ZZ (16:05:06 +01:00)
+ |
+
+Log Segmentation
+ |
+This parameter needs to be specified if the Log Format is set to Multi-line. By generation time indicates that a time wildcard is used to detect log boundaries, whereas By regular expression indicates that a regular expression is used.
+ |
+
+Regular Expression
+ |
+You can set a regular expression to look for a specific pattern to indicate the beginning of a log event. This parameter needs to be specified when you select Multi-line for Log Format and By regular expression for Log Segmentation.
+ |
+
+
+
+
The time wildcard and regular expression will look for the specified pattern right from the beginning of each log line. If no match is found, the system time, which may be different from the time in the log event, is used. For example, if the time wildcard is set to YYYY-MM-DD hh:mm:ss but the time in the log event is [2019-01-01 23:59:59], they cannot be matched. In general cases, you are advised to select Single-line for Log Format and System time for Log Time.
+
+ - Click OK. LTS will collect logs based on your specified collection rules.
The configurations of the log collection path can still be changed after the path is added.
+
+
+
Log View
+
+
+
diff --git a/docs/lts/umn/lts_04_0008.html b/docs/lts/umn/lts_04_0008.html
new file mode 100644
index 00000000..99869529
--- /dev/null
+++ b/docs/lts/umn/lts_04_0008.html
@@ -0,0 +1,22 @@
+
+
+Viewing Real-Time Logs
+You can view the logs reported to the LTS console in real time.
+
Prerequisites
- You have created log groups and log streams.
- You have installed ICAgent.
- You have configured log collection rules.
+
+
Procedure
- Log in to the LTS console and choose Log Management.
- In the log group list, click the name of a log group.
- In the log stream list, click the name of a log stream.
- On the log stream details page, click the Real-Time Logs tab to view 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.
+
Stay on the Real-Time Logs tab to keep updating them in real time. If you leave the Real-Time Logs tab page, logs will stop being loaded in real time. The next time you access the tab, the logs that were shown before you left the tab will not be displayed.
+
+
+
Log Search
+Follow the directions below to search logs by keyword and time range:
+
- On the LTS console, click Log Management.
- In the log group list, click the name of a log group.
- In the log stream list, click the name of a log stream.
Alternatively, click Search in the Operation column of the row containing the target log stream.
+ - In the upper right corner, select a time range.
- On the displayed page, enter a keyword in the search box.
- Click
to start searching.Logs that contain the keyword are displayed.
+
+
Search Syntax and Examples
Search syntax:
+
+
Table 1 Search syntaxFilter
+ |
+Description
+ |
+
|---|
+
+Exact search by keyword
+ |
+LTS searches for logs containing the exact keyword (case-sensitive) that you specify. A keyword is the word between two adjacent delimiters.
+You can add an asterisk (*) after a keyword, for example, error*, if you are not familiar with delimiters.
+ |
+
+Exact search by phrase
+ |
+LTS searches for logs containing the exact phrase (case-sensitive) that you specify.
+ |
+
+&&
+ |
+Intersection of search results.
+ |
+
+||
+ |
+Union of search results.
+ |
+
+AND
+ |
+Intersection of search results.
+ |
+
+NOT
+ |
+Logs that contain the keyword after NOT are excluded.
+ |
+
+*
+ |
+Fuzzy search. The asterisk (*) can only be after a keyword to replace an unspecified number of characters.
+ |
+
+?
+ |
+Fuzzy search. The question mark (?) can be put in the middle or at the end of a keyword to replace a character.
+ |
+
+
+
+
+
Operators (such as &&, ||, AND, NOT, *, ?, and :) contained in raw logs cannot be used to search for logs.
+
+
Search rules:
+
+
- Searching using multiple key-value pairs is supported. The format is key1:value1 key2:value2.
For example, if you enter casInstanceID:in* hostIP:x.x.x.x kkfa, the following is displayed:
+{
+ "casApplicationName": "app",
+ "casEnvironmentName": "env",
+ "hostName": "ecs-zc-xxxx",
+ "collectTime": "15838xxxxx",
+ "hostIP": "x.x.x.x",
+ "logContent": "4312341341341314 kkfa dfa\\n", (Keyword)
+ "appName": "testhshroma",
+ "casInstanceID": "ins-111",
+ "hostId": "b32dcfc0-615b-4de6-a796-dfccaxxxxxx",
+ "casComponentID": "com-111"
+}
+
+
Search examples:
+
- Search for logs containing start: Enter start.
- Search for logs containing start to refresh: Enter start to refresh.
- Search for logs containing both start and unexpected: Enter start && unexpected or start AND unexpected.
- Search for logs containing start or unexpected: Enter start || unexpected.
+
- Search for the logs containing keyword start but not unexpected: Enter start NOT unexpected.
- error*: logs that contain error.
- er?or: logs that start with er, is followed by any single character, and end with or.
- query1 AND query2 NOT query3: logs that contain both query1 and query2 but not query3.
+
- Keywords are case-sensitive.
- The asterisk (*) and question mark (?) do not match special characters such as hyphens (-) and spaces.
+
+
+
Quick Search
+To search for logs using a keyword repeatedly, perform the following operations to configure quick search.
+
Procedure
- Log in to the LTS console and choose Log Management.
- In the log group list, click the name of a log group.
- In the log stream list, click the name of a log stream.
Alternatively, click Search in the Operation column of the row containing the target log stream.
+ - On the log stream details page, click Add Quick Search and configure the Name and Keyword parameters.
- Set Name. A quick search name:
- Can contain only letters, digits, hyphens (-), underscores (_), and periods (.).
- Cannot start with a period (.) or underscore (_), and cannot end with a period (.).
- Can contain 1 to 64 characters.
+ - Set Keyword to a keyword that will be frequently used, for example, error*.
+
- Click OK.
Added query search filters are displayed next to Add Quick Search. Click the name of a quick search filter to view the search results.
+
+
+
Viewing Context of a Log
You can check the log events generated before and after a log event for quick fault locating.
+
- Log in to the LTS console and choose Log Management.
- In the log group list, click the name of a log group.
- In the log stream list, click the name of a log stream.
Alternatively, click Search in the Operation column of the row containing the target log stream.
+ - On the Original Logs tab page, click View Context in the row of a log event.
The context of the log is displayed.
+
+
+
+
Agent Management
+
+
+
diff --git a/docs/lts/umn/lts_04_0013.html b/docs/lts/umn/lts_04_0013.html
new file mode 100644
index 00000000..4392b734
--- /dev/null
+++ b/docs/lts/umn/lts_04_0013.html
@@ -0,0 +1,61 @@
+
+
+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
+ |
+Check for network faults and rectify such faults.
+ |
+
+Faulty
+ |
+ICAgent is faulty. Contact technical support.
+ |
+
+
+
+
+
Appendixes
+
+
+
diff --git a/docs/lts/umn/lts_04_0041.html b/docs/lts/umn/lts_04_0041.html
new file mode 100644
index 00000000..ad1a30a3
--- /dev/null
+++ b/docs/lts/umn/lts_04_0041.html
@@ -0,0 +1,107 @@
+
+
+
+ Log Transfer
+
+ You can transfer logs to OBS to keep logs for a long time.
+
Local log files are cleared periodically, but the logs transferred to OBS will not be affected.
+
To transfer logs, you must have the OBS Administrator permissions apart from the LTS permissions.
+
+
Prerequisites
- Logs have been ingested to LTS.
- You have purchased 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 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 log stream name.
+
+
+Table 1 Transfer parametersParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+Log Group Name
+ |
+Select a log group.
+ |
+N/A
+ |
+
+Log Stream Name
+ |
+Select a log stream.
+ |
+N/A
+ |
+
+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.
+ - Only Standard OBS buckets are supported in LTS.
+ |
+N/A
+ |
+
+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. A custom path must meet the following requirements: - Must start with /LogTanks/Region name.
- Can contain 1–64 characters.
+ - 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
+ |
+
+Log File Prefix
+ |
+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
+ |
+
+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 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
+ |
+
+Transfer Log to OBS
+ |
+Enable log transfer to OBS.
+ |
+Enabled
+ |
+
+Transfer Period
+ |
+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
+ |
+
+
+
+
- Click OK. When the log transfer status changes to Normal, the transfer task has been created.
- Click the OBS bucket name in the OBS Bucket 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.
+
+
+
+
Viewing Transfer Status
The 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.
+
+
Deleting a Log Transfer Task
If 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.
+
+
- 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 More > Delete in the Operation column.
- Click OK.
+
+
. Ensure they have space before and after. */.ullinks,ul.simple{list-style-type:none}.attention,.danger,.ddexpand,.dlexpand,.example,.fastpath,.important,.liexpand,.linklist,.note,.notice,.olchildlink,.relconcepts,.relinfo,.relref,.reltasks,.remember,.restriction,.section,.sliexpand,.stepexpand,.substepexpand,.tip,.ulchildlink,.warning{margin-top:1em;margin-bottom:1em}.linklistwithchild,.sublinklist{margin-top:1em;margin-right:1.5em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-right:20px}/*! Set heading sizes, getting smaller for deeper nesting */.topictitle1{font-size:1.34em;margin-top:0;margin-bottom:.1em}.topictitle2,.topictitle3,.topictitle4,.topictitle5,.topictitle6,.sectiontitle{font-size:1.17em}.topictitle2{margin-top:1pc;margin-bottom:.45em}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-weight:700}.topictitle4{margin-top:.83em;font-weight:700}.topictitle5{font-weight:700}.topictitle6{font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:0;color:#000;font-weight:700}/*! All note formats have the same default presentation */.attentiontitle,.bold,.cautiontitle,.dangertitle,.dlterm,.fastpathtitle,.firstcol,.importanttitle,.notelisttitle,.notetitle,.noticetitle,.parmname,.remembertitle,.restrictiontitle,.tiptitle,.uicontrol,.warningtitle{font-weight:700}.caution{font-weight:700;margin-bottom:1em}/*! Simple lists do not get a bullet *//*! Used on the first column of a table, when rowheader="firstcol" is used *//*! Various basic phrase styles */.boldItalic{font-weight:700;font-style:italic}.shortcut,.underlined{text-decoration:underline}/*! 2008-10-27 keyword采用跟随上下文的样式
+*//*! Default of bold for definition list terms *//*! Use CSS to expand lists with @compact="no" */.dltermexpand{font-weight:700;margin-top:1em}[compact="yes"]>li{margin-top:0}[compact="no"]>li{margin-top:.53em}/*! Align images based on @align on topic/image */div.imageleft,.text-align-left{text-align:left}div.imagecenter,.text-align-center{text-align:center}div.imageright,.text-align-right{text-align:right}div.imagejustify,.text-align-justify{text-align:justify}.cellrowborder{border-right:0;border-top:0;border-left:1px solid;border-bottom:1px solid}.row-nocellborder{border-left:hidden;border-right:0;border-top:0;border-bottom:1px solid}.cell-norowborder{border-top:0;border-bottom:hidden;border-right:0;border-left:1px solid}.nocellnorowborder{border:0;border-left:hidden;border-bottom:hidden}pre.codeblock,pre.screen{padding:5px;border:outset;background-color:#ccc;margin-top:2px;margin-bottom:2px;white-space:pre}
\ No newline at end of file
diff --git a/docs/lts/umn/public_sys-resources/danger_3.0-en-us.png b/docs/lts/umn/public_sys-resources/danger_3.0-en-us.png
new file mode 100644
index 00000000..47a9c723
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/danger_3.0-en-us.png differ
diff --git a/docs/lts/umn/public_sys-resources/delta.gif b/docs/lts/umn/public_sys-resources/delta.gif
new file mode 100644
index 00000000..0d1b1f67
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/delta.gif differ
diff --git a/docs/lts/umn/public_sys-resources/deltaend.gif b/docs/lts/umn/public_sys-resources/deltaend.gif
new file mode 100644
index 00000000..cc7da0fc
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/deltaend.gif differ
diff --git a/docs/lts/umn/public_sys-resources/icon-arrowdn.gif b/docs/lts/umn/public_sys-resources/icon-arrowdn.gif
new file mode 100644
index 00000000..84eec9be
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/icon-arrowdn.gif differ
diff --git a/docs/lts/umn/public_sys-resources/icon-arrowrt.gif b/docs/lts/umn/public_sys-resources/icon-arrowrt.gif
new file mode 100644
index 00000000..39583d16
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/icon-arrowrt.gif differ
diff --git a/docs/lts/umn/public_sys-resources/icon-caution.gif b/docs/lts/umn/public_sys-resources/icon-caution.gif
new file mode 100644
index 00000000..079c79b2
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/icon-caution.gif differ
diff --git a/docs/lts/umn/public_sys-resources/icon-danger.gif b/docs/lts/umn/public_sys-resources/icon-danger.gif
new file mode 100644
index 00000000..079c79b2
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/icon-danger.gif differ
diff --git a/docs/lts/umn/public_sys-resources/icon-huawei.gif b/docs/lts/umn/public_sys-resources/icon-huawei.gif
new file mode 100644
index 00000000..a31d60f8
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/icon-huawei.gif differ
diff --git a/docs/lts/umn/public_sys-resources/icon-note.gif b/docs/lts/umn/public_sys-resources/icon-note.gif
new file mode 100644
index 00000000..31be2b03
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/icon-note.gif differ
diff --git a/docs/lts/umn/public_sys-resources/icon-notice.gif b/docs/lts/umn/public_sys-resources/icon-notice.gif
new file mode 100644
index 00000000..40907065
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/icon-notice.gif differ
diff --git a/docs/lts/umn/public_sys-resources/icon-tip.gif b/docs/lts/umn/public_sys-resources/icon-tip.gif
new file mode 100644
index 00000000..c47bae05
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/icon-tip.gif differ
diff --git a/docs/lts/umn/public_sys-resources/icon-warning.gif b/docs/lts/umn/public_sys-resources/icon-warning.gif
new file mode 100644
index 00000000..079c79b2
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/icon-warning.gif differ
diff --git a/docs/lts/umn/public_sys-resources/note_3.0-en-us.png b/docs/lts/umn/public_sys-resources/note_3.0-en-us.png
new file mode 100644
index 00000000..57a0e1f5
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/note_3.0-en-us.png differ
diff --git a/docs/lts/umn/public_sys-resources/notice_3.0-en-us.png b/docs/lts/umn/public_sys-resources/notice_3.0-en-us.png
new file mode 100644
index 00000000..fa4b6499
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/notice_3.0-en-us.png differ
diff --git a/docs/lts/umn/public_sys-resources/popup.js b/docs/lts/umn/public_sys-resources/popup.js
new file mode 100644
index 00000000..a550862e
--- /dev/null
+++ b/docs/lts/umn/public_sys-resources/popup.js
@@ -0,0 +1 @@
+var i=0;var dhtmlgoodies_tooltipFlag=false;var dhtmlgoodies_tooltip="";var dhtmlgoodies_tooltipShadow="";var dhtmlgoodies_shadowSize=3;var dhtmlgoodies_tooltipMaxWidth=500;var dhtmlgoodies_tooltipMinWidth=100;var dhtmlgoodies_iframe=false;var timeId;var clickFlag=false;var tooltip_is_msie=(navigator.userAgent.indexOf("MSIE")>=0&&navigator.userAgent.indexOf("opera")==-1&&document.all)?true:false;var xPos;var yPos;window.document.onmousemove=function(a){a=a||window.event;if(a.pageX){xPos=a.pageX;yPos=a.pageY}else{if(document.body!==null&&typeof document.body!=="undefined"){xPos=a.clientX+document.body.scrollLeft-document.body.clientLeft;yPos=a.clientY+document.body.scrollTop-document.body.clientTop}}};function showTooltip(e){if(document.body===null||typeof document.body==="undefined"){return}if(i==0){return}clickFlag=true;var f=Json.parse("jsonData."+e);var a=Math.max(document.body.clientWidth,document.documentElement.clientWidth)-20;if(!dhtmlgoodies_tooltipFlag){dhtmlgoodies_tooltip=document.createElement("DIV");dhtmlgoodies_tooltip.id="dhtmlgoodies_tooltip";dhtmlgoodies_tooltipShadow=document.createElement("DIV");dhtmlgoodies_tooltipShadow.id="dhtmlgoodies_tooltipShadow";document.body.appendChild(dhtmlgoodies_tooltip);document.body.appendChild(dhtmlgoodies_tooltipShadow);if(tooltip_is_msie){dhtmlgoodies_iframe=document.createElement("IFRAME");dhtmlgoodies_iframe.frameborder="5";dhtmlgoodies_iframe.style.backgroundColor="#FFFFFF";dhtmlgoodies_iframe.src="#";dhtmlgoodies_iframe.style.zIndex=100;dhtmlgoodies_iframe.style.position="absolute";document.body.appendChild(dhtmlgoodies_iframe)}}dhtmlgoodies_tooltip.style.display="block";dhtmlgoodies_tooltipShadow.style.display="block";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="block"}var b=Math.max(document.body.scrollTop,document.documentElement.scrollTop);if(navigator.userAgent.toLowerCase().indexOf("safari")>=0){b=0}var c=xPos+10;dhtmlgoodies_tooltip.style.width=null;dhtmlgoodies_tooltip.innerHTML=f;dhtmlgoodies_tooltip.style.left=c+"px";if(tooltip_is_msie){dhtmlgoodies_tooltip.style.top=yPos+20+b+"px"}else{dhtmlgoodies_tooltip.style.top=yPos+20+"px"}dhtmlgoodies_tooltipShadow.style.left=c+dhtmlgoodies_shadowSize+"px";if(tooltip_is_msie){dhtmlgoodies_tooltipShadow.style.top=yPos+20+b+dhtmlgoodies_shadowSize+"px"}else{dhtmlgoodies_tooltipShadow.style.top=yPos+20+dhtmlgoodies_shadowSize+"px"}if(dhtmlgoodies_tooltip.offsetWidth>dhtmlgoodies_tooltipMaxWidth){dhtmlgoodies_tooltip.style.width=dhtmlgoodies_tooltipMaxWidth+"px"}var d=dhtmlgoodies_tooltip.offsetWidth;if(da){dhtmlgoodies_tooltip.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a))+"px";dhtmlgoodies_tooltipShadow.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a)+dhtmlgoodies_shadowSize)+"px"}if(tooltip_is_msie){dhtmlgoodies_iframe.style.left=dhtmlgoodies_tooltip.style.left;dhtmlgoodies_iframe.style.top=dhtmlgoodies_tooltip.style.top;dhtmlgoodies_iframe.style.width=dhtmlgoodies_tooltip.offsetWidth+"px";dhtmlgoodies_iframe.style.height=dhtmlgoodies_tooltip.offsetHeight+"px"}}function hideTooltip(){i=0;clickFlag=false;if((dhtmlgoodies_tooltip!==null&&typeof dhtmlgoodies_tooltip!=="undefined")&&+(dhtmlgoodies_tooltip.style!==null&&typeof dhtmlgoodies_tooltip.style!=="undefined")){dhtmlgoodies_tooltip.style.display="none";dhtmlgoodies_tooltipShadow.style.display="none";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="none"}}if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}function showText(a){i=1;timeId=setTimeout(function(){showTooltip(a)},500)}function showText2(a){if(!clickFlag){i=1;showTooltip(a);i=0;if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}}function anchorScroll(b){var d=document.getElementsByName(b);if(d!=null&&d.length>0){var c=d[0];var a=c.getBoundingClientRect().left+(document.body.scrollLeft||(document.documentElement&&document.documentElement.scrollLeft));var e=c.getBoundingClientRect().top+(document.body.scrollTop||(document.documentElement&&document.documentElement.scrollTop));window.scrollTo(a,e-30)}};
\ No newline at end of file
diff --git a/docs/lts/umn/public_sys-resources/warning_3.0-en-us.png b/docs/lts/umn/public_sys-resources/warning_3.0-en-us.png
new file mode 100644
index 00000000..def5c356
Binary files /dev/null and b/docs/lts/umn/public_sys-resources/warning_3.0-en-us.png differ