หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา
- 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
- Collecting Logs from Multiple Channels to LTS
- 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
Show all
Copied.
Cross-Account Ingestion
After you configure cross-account ingestion, if account A deletes the agency from IAM, LTS cannot detect the deletion and the cross-account ingestion still takes effect. If the cross-account ingestion configuration is no longer used, notify account B to delete it.
Prerequisites
An agency relationship has been created.
Restrictions
- Log stream mapping cannot be performed for log cleaning logs.
- Before data synchronization is complete, data in the target and source log streams may be different. Check back later in one hour.
Procedure
If you choose Cross-Account Ingestion as the log ingestion type, perform the following operations to configure the ingestion:
- Log in to the LTS console.
- In the navigation pane on the left, choose Log Ingestion and click Cross-Account Ingestion.
- Select an agency.
Set parameters by referring to Table 1 and click Next: Log Stream Mapping.
Table 1 Agency parameters Parameter
Description
Agency Name
Enter the name of an agency created by the delegator in IAM. A delegator account can create an agency to delegate resource management permissions to another account.
Delegator Account Name
Enter the name of the delegator account to verify the delegation.
- Map log streams.
On the Log Stream Mapping page, there are two ways to configure ingestion rules: automatic and manual configuration.
- Automatic configuration
- Click Auto Configure.
- On the displayed page, set the required parameters and click OK.
Table 2 Parameters of automatic ingestion rule configuration Parameter
Description
Rule Name Prefix
Enter the rule name prefix. In automatic configuration, this prefix is used to generate multiple ingestion rules.
Can contain only letters, digits, underscores (_), hyphens (-), and periods (.). The prefix cannot start with a period or underscore, or end with a period. If you do not specify a prefix, the default rule name prefix rule will be used.
Select the log groups or log streams that you want to ingest from the delegator account.
Up to 20 log groups or log streams can be selected.
NOTE:By default, the names of the target log groups and target log streams of the delegated account are the same as those of the source log groups and source log streams of the delegator account. You can also manually change the names of the target log groups and target log streams.
- Click Preview.
NOTE:
- There are two types of preview results:
- A new target log stream will be created: A target log group or log stream will be created in the delegated account.
- An existing target log stream will be ingested: The target log group or log stream already exists in the delegated account.
- Preview error messages are as follows:
- Source log stream xxx has been configured as the target log stream.
- Target log stream xxx has been configured as the source log stream.
- Target log stream xxx already exists in another log group.
- Target log stream xxx exists in different target log groups.
- Duplicate rule names.
- The source log stream xxx is already mapped.
- The number of log groups or log streams exceeds the upper limit.
If any of the preceding error messages is displayed, delete the corresponding ingestion rule of the log stream.
- There are two types of preview results:
- After the preview is complete, click Submit.
- Click Auto Configure.
- Manual configuration
- On the Log Stream Mapping page, click Add Rule.
Table 3 Parameter
Description
Rule Name
The default value is rule_xxx. You can also specify a name as needed.
Can contain only letters, digits, underscores (_), hyphens (-), and periods (.). The name cannot start with a period or underscore, or end with a period.
Delegator Account
Source Log Group
Log group of the delegator account. Select an existing log group.
Source Log Stream
Log stream of the delegator account. Select an existing log stream.
Delegated Account
Target Log Group
Log group of the delegator account. You can select an existing log group or enter a name to create one.
Target Log Stream
Log stream of the delegated account. You can select an existing log stream or enter a name to create one.
- Click Preview.
NOTE:
- There are two types of preview results:
- A new target log stream will be created: A target log group or log stream will be created in the delegated account.
- An existing target log stream will be ingested: The target log group or log stream already exists in the delegated account.
- There are five types of preview errors:
- Source log stream xxx has been configured as the target log stream.
- Target log stream xxx has been configured as the source log stream.
- Target log stream xxx already exists in another log group.
- Target log stream xxx exists in different target log groups.
- Duplicate rule names.
- The source log stream xxx is already mapped.
- The number of log groups or log streams exceeds the upper limit.
If any of the preceding error messages is displayed, delete the corresponding ingestion rule of the log stream.
- There are two types of preview results:
- After the preview is complete, click Submit and wait until the log ingestion task is created.
- On the Log Stream Mapping page, click Add Rule.
- Automatic configuration
- Finish the configuration.
NOTE:
After the configuration is complete, data will be synchronized within one hour. Please check back later.
- If multiple log streams are ingested, you can click Back to Ingestion Configurations to view the log ingestion list.
- If a single log stream is ingested, click Back to Ingestion Configurations to view the log ingestion list. Click View Log Stream to view details about the ingested log stream.
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