หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา
- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Granting LTS Permissions to IAM Users
- Log Management
-
Log Ingestion
- Overview
-
Using ICAgent to Collect Logs
- Overview
- Installing ICAgent (Intra-Region Hosts)
- Installing ICAgent (Extra-Region Hosts)
- Managing ICAgent
- Managing Host Groups
- Ingesting BMS Text Logs to LTS
- Ingesting CCE Application Logs to LTS
- Ingesting ECS Text Logs to LTS
- Ingesting ServiceStage Containerized Application Logs to LTS
- Ingesting ServiceStage Cloud Host Logs to LTS
- Ingesting Self-Built Kubernetes Application Logs to LTS
- Setting ICAgent Structuring Parsing Rules
-
Ingesting Cloud Service Logs to LTS
- Overview
- Ingesting AOM Logs to LTS
- Ingesting APIG Logs to LTS
- Ingesting CBH Logs to LTS
- Ingesting CFW Logs to LTS
- Ingesting CTS Logs to LTS
- Ingesting DDS Logs to LTS
- Ingesting DMS for Kafka Logs to LTS
- Ingesting DRS Logs to LTS
- Ingesting GaussDB(DWS) Logs to LTS
- Ingesting ELB Logs to LTS
- Ingesting Enterprise Router Logs to LTS
- Ingesting FunctionGraph Logs to LTS
- Ingesting GaussDB Logs to LTS
- Ingesting GES Logs to LTS
- Ingesting GaussDB(for MySQL) Logs to LTS
- Ingesting GeminiDB Logs to LTS
- Ingesting GeminiDB Mongo Logs to LTS
- Ingesting GeminiDB Cassandra Logs to LTS
- Ingesting IoTDA Logs to LTS
- Ingesting ModelArts Logs to LTS
- Ingesting MRS Logs to LTS
- Ingesting RDS for MySQL Logs to LTS
- Ingesting RDS for PostgreSQL Logs to LTS
- Ingesting RDS for SQL Server Logs to LTS
- Ingesting ROMA Connect Logs to LTS
- Ingesting SMN Logs to LTS
- Ingesting SecMaster Logs to LTS
- Ingesting VPC Logs to LTS
- Ingesting WAF Logs to LTS
- Using APIs to Ingest Logs to LTS
- Ingesting Logs to LTS Across IAM Accounts
- Using Kafka to Report Logs to LTS
- Using Flume to Report Logs to LTS
- Log Search and Analysis
-
Log Visualization
- Overview
- Visualizing Logs in Statistical Charts
-
Visualizing Logs in Dashboards
- Creating a Dashboard
- Adding a Dashboard Filter
-
Dashboard Templates
- APIG Dashboard Templates
- CCE Dashboard Templates
- CDN Dashboard Templates
- CFW Dashboard Templates
- CSE Dashboard Templates
- DCS Dashboard Template
- DDS Dashboard Template
- DMS Dashboard Template
- DSL Dashboard Template
- ER Dashboard Template
- METRIC Dashboard Template
- Nginx Dashboard Templates
- VPC Dashboard Template
- WAF Dashboard Templates
- Log Alarms
- Log Transfer
- Log Processing
- Configuration Center
- Querying Real-Time LTS Traces
-
Best Practices
- Overview
-
Log Ingestion
- Collecting Logs from Third-Party Cloud Vendors, Internet Data Centers, and Other Huawei Cloud Regions to LTS
- Collecting Kubernetes Logs from Third-Party Clouds, IDCs, and Other Huawei Cloud Regions to LTS
- Collecting Syslog Aggregation Server Logs to LTS
- Importing Logs of Self-built ELK to LTS
- Using Flume to Report Logs to LTS
- Collecting Zabbix Data Through ECS Log Ingestion
- Log Search and Analysis
- Log Transfer
- Billing
- Developer Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- API Calling Examples
- Examples
-
APIs
- Host Group Management
- Log Group Management
- Log Stream Management
- Log Management
- Log Ingestion
- Log Transfer
- Log Collection Beyond Free Quota
- Cloud Log Structuring
- Container Log Ingestion from AOM to LTS
- Alarm Topics
- Message Template Management
- SQL Alarm Rules
- Keyword Alarm Rules
- Alarm List
- Tag Management
- Dashboard Management
- Log Charts
- Quick Search
- Multi-Account Log Aggregation
- Permissions Policies and Supported Actions
- Appendix
- SDK Reference
-
FAQs
- Overview
- Consultation
- Log Management
-
Host Management
- What Do I Do If ICAgent Installation Fails in Windows and the Message "SERVICE STOP" Is Displayed?
- What Do I Do If ICAgent Upgrade Fails on the LTS Console?
- What Do I Do If I Could Not Query New Logs on LTS?
- What Do I Do If ICAgent Restarts Repeatedly After Being Installed?
- What Do I Do If ICAgent Is Displayed as Offline on the LTS Console After Installation?
- What Do I Do If I Do Not See a Host with ICAgent Installed on the LTS Console?
- How Do I Create a VPC Endpoint on the VPCEP Console?
- How Do I Obtain an AK/SK Pair?
- How Do I Install ICAgent by Creating an Agency?
-
Log Ingestion
- What Do I Do If LTS Cannot Collect Logs After I Configure Host Log Ingestion?
- 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?
- What Do I Do If the CPU Usage Is High When ICAgent Is Collecting Logs?
- What Kinds of Logs and Files Does LTS Collect?
- How Do I Disable the Function of Collecting CCE Standard Output Logs to AOM on the LTS Console?
- What Log Rotation Scheme Should I Use for ICAgent to Collect Logs?
- Does LTS Use the Log4j Plug-in to Report Logs?
- How Long Does It Take to Generate Logs After Configuring Log Ingestion?
- What Do I Do If LTS Cannot Collect Logs After I Configure Log Ingestion with ICAgent?
- Log Search and Analysis
- Log Transfer
-
More Documents
- User Guide (ME-Abu Dhabi Region)
- API Reference (ME-Abu Dhabi Region)
- User Guide(Paris Regions)
- API Reference(Paris Regions)
- User Guide (Kuala Lumpur Region)
- API Reference (Kuala Lumpur Region)
- User Guide (Ankara Region)
-
API Reference (Ankara Region)
- Before You Start
- Calling APIs
- API Calling Examples
- APIs
- Permissions and Supported Actions
- Appendix
- Change History
- Videos
- General Reference
Copied.
Managing Log Streams
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.
A maximum of 100 log streams can be created in a log group. If you cannot create a log stream, delete unnecessary log streams before creating new ones, or create log streams in another log group.
Prerequisites
You have created a log group.
Creating a Log Stream
- Log in to the LTS console. 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.
If your organization has configured tag policies for LTS, add tags to log groups, log streams, log ingestion rules, and host groups based on the tag policies. If a tag does not comply with the tag policies, the log group, log stream, ingestion rule, and host group creation may fail. Contact your administrator to learn more about tag policies. For details about tag policies, see Overview of a Tag Policy. For details about tag management, see Managing Tags.
Table 1 Log stream parameters Parameter
Description
Log Group Name
The name of the target log group is displayed by default.
Log Stream 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.
Enterprise Project Name
Select the required enterprise project. The default value is default. You can click View Enterprise Projects to view all enterprise projects.
NOTE:- An enterprise project can be used only after it is enabled. For details, see Enabling the Enterprise Project Function.
- Then, resources of this enterprise project can be removed. For details, see Removing Resources from an Enterprise Project.
Log Storage
If this function is disabled, Log Retention (Days) cannot be enabled.
- If enabled, logs will be stored in the search engine and all log functions are available.
- If disabled, logs will not be stored to LTS. This saves on index traffic and storage costs, but disables log search, analysis, alarm, consumption, and processing. You will only be allowed to use metric generation and log transfer functions.
Log Retention (Days)
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 (Days) for the log stream, logs are retained for the duration set for the log stream.
- If you disable Log Retention (Days) 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.
- To delete a tag, click Delete in the Operation column of the tag.
- 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.
Anonymous Write
Anonymous write is disabled by default. Only logs reported by Android, iOS, applets, and browsers can be written anonymously. To use this function, submit a service ticket to add your account to the whitelist.
If anonymous write is enabled for a log stream, no valid authentication is required, which may lead to the generation of dirty data.
Remark
Enter remarks. The value contains up to 1,024 characters.
- Click OK. In the log stream list, you can view information such as the log stream name and operations.
- You can view the log stream billing status. For details, see Price Calculator.
- The function of reporting SDRs by log stream is in Friendly User Test (FUT). You can submit a service ticket to enable it.
Modifying a Log Stream
By 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 Modify in the Operation column.
- On the page displayed, modify the stream name, log retention duration, and tags.
- If you disable Log Retention (Days), the log stream will inherit the log retention setting of the log group.
- If you enable Log Retention (Days), 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.
- Currently, logs of whitelisted users can be retained for 1,095 days. If necessary, submit a service ticket.
- Click OK.
- After the modification is successful, move the cursor over the log stream name. The new and original log stream names are displayed.
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. This may lead to exceptions in related tasks. In addition, deleted log streams cannot be restored. Exercise caution when performing this operation.
- 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 OK.
Figure 1 Deleting a log stream
Other Operations
- Adding a log stream to favorites
Click More > Edit in the Operation column of a log stream. On the displayed dialog box, enable My Favorites and/or My Favorites(Local Cache). The stream is then displayed in the My Favorites/My Favorites(Local Cache) list.
- Viewing details
Click More > Details in the Operation column of a log stream to view its details, including its name, ID, and creation time.
- Collection diagnosis: If you have enabled ICAgent diagnosis by referring to Setting ICAgent Collection, you can click More > ICAgent Collect Diagnosis in the Operation column of the target log stream to check its ICAgent's exceptions, overall status, and collection monitoring.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot