Overview
Log ingestion is crucial for LTS, as it collects various log data generated during the execution of applications or services, including system statuses, errors, and user operation records. LTS stores the data in a specific location for subsequent analysis and application, which is critical to system O&M, troubleshooting, and service analysis.
LTS enables real-time log ingestion via various methods. Logs can be collected using ICAgent, ingested from cloud services, or reported to LTS via custom software or APIs. Subsequently, you can perform operations on these logs using the LTS console, such as searching and analyzing logs, visualizing log statistics in charts or dashboards, and setting alarm reporting and log transfer.
Before configuring log ingestion, ensure that ICAgent collection is enabled by referring to Setting LTS Log Collection Quota and Usage Alarms.
- This function is enabled by default. If you do not need to collect logs, disable this function to reduce resource usage.
- After this function is disabled, ICAgent will stop collecting logs, and the log collection function on the AOM console will also be disabled.
Data Sources
Table 1 lists the sources of logs that can be reported to LTS.
Type |
Source |
Ingestion Method |
---|---|---|
Application |
Program output |
|
Access logs |
||
OS |
Linux |
|
Windows |
||
Docker files |
||
Docker output |
||
Database |
MySQL |
|
SQL Server |
||
PostgreSQL |
||
GaussDB |
||
GeminiDB |
||
Standard protocol |
HTTP polling |
|
Syslog |
||
Kafka |
||
Third party |
Logstash |
|
Flume |
||
Beats |
||
Cloud service |
Logs of Huawei Cloud services, such as ECS and CCE |
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