Torch Log Service
Torch Log Service
Torch Log Service
Document
Product News
Product Overview
Product Billing
User Guide
TLS Agent
AgentLoop
Resource management
Host group
Data collection
LogCollector collection
Introduction to LogCollector
Installation and upgrade
Collect host logs
Collect container logs
LogCollector plugins
Manage LogCollector
general reference
Data import
Cloud product log collection
TOS log collection
DBW log collection
VPN Log collection
VKE log collection
CLB log collection
CloudTrail log collection
CFW log collection
NTA log collection
ALB log collection
APMPlus log collection
veFaaS log collection
VPC log collection
veImageX log collection
TrafficRoute DNS log collection
DDoS log collection
WAF log collection
DCDN log collection
Multi-cloud security platform log collection
APIG log collection
Machine learning task log collection
CR log collection
Volcano Ark application lab log collection
FileNAS log collection
LLM Application Firewall Service log collection
vePFS log collection
Cloud security center log collection
EFS log collection
Data storage
Query and analysis
Configure log indexes
Query log
Analyze logs
Query and analyze logs using third-party tools
Associate external data source for log query
SQL function
SQL syntax
Visualization
Query and analysis charts
Summaries of query and analysis charts
Create dashboard
Use dashboard
Add dashboard filters and variables
Use other systems to analyze logs
Log application
Log applications for product observability
Log applications for large models observability
Coding Agent log app
ModelProvider log app
No-coding Agent log app
Log applications for basic service monitoring
Data processing
Data transformation
Syntax and functions
Global operation function
expression function
Data processing best practices
general reference
Data write processor
Data consumer processor
Data consumption and shipping
Ship logs to TOS
Ship logs to Kafka
Ship logs to Splunk
Alarm
Alarm policy
Alarm notification content
Alarm notification content template
alarm notification channel
Tracing service
Monitor Log Service
API reference
Project management API
Topic management API
Shard management API
Index management API
Log management API
Host group management API
Collection configuration management API
Data import API
Data processor API
Data transformation API
Data backflow API
SQL analysis API
Alarm management API
Consumer group management API
Kafka protocol consumption API
Tag management API
Trace storage API
Account management API
SDK reference
Go SDK
Java SDK
Python SDK
iOS SDK
C++ SDK
CLI reference
Best practices
Data collection
Query and analysis
permission management
Consumption and delivery
Visualization
Alarm
FAQs
Billing and cost FAQ
Data collection FAQ
Data storage FAQ
Index configuration FAQ
Query and analysis FAQ
Scheduled SQL tasks FAQ
Alarm FAQ
- Documentation
Torch Log ServiceFAQsData collection FAQHow to troubleshoot log collection exceptions (host machine)
Copy page
Download PDFData collection FAQ
How to troubleshoot log collection exceptions (host machine)
Copy pageDownload PDFHow to troubleshoot log collection exceptions (host machine)
After using LogCollector to collect logs, if logs are not successfully collected, you can refer to the steps in this article for troubleshooting.
1. Check whether logs are being printed in real time
The LogCollector collection configuration created through the console is incremental by default, which means only logs generated after the configuration takes effect are collected.
- If the log file is not updated after creating the collection configuration, LogCollector will not collect that file.
- If the log file is updated after creating the collection configuration, proceed to the next step for further inspection.
2. Check whether the host group heartbeat is normal
- If the target server's heartbeat is abnormal, please refer to How to troubleshoot host group heartbeat status Exception (host machine) for troubleshooting.
- If the target server's heartbeat is normal, proceed to the next step for further inspection.
3. Check whether the collection configuration is correct
Confirm in the TLS console that the LogCollector collection configuration has been created and is correct.
- If the collection configuration has not been created, create the collection configuration first. For specific operations, please refer to Collect host machine logs.
- If the collection configuration has already been created, confirm that the configuration is correct. For example:
- The collection path in the configuration matches the log file path on the current server.
- The log file matches the collection configuration correctly.
- By default, a log file can only match one collection configuration. If logs in the file need to be collected multiple times, please refer to Collect multiple log files or standard output simultaneously.
- If there are no issues, proceed to the next step for further inspection.
4. Check whether the collection configuration is bound to the host group
In the host group details page, check whether the collection configuration has been bound to the host group. For details, see View host group.
- If the host group is not bound, please refer to Change the host group for the collection configuration to complete the configuration.
- If the host group is already bound, proceed to the next step for further inspection.
5. Check error messages
Check whether there are error messages in the LogCollector logs. The LogCollector client records key information as well as all WARNING and ERROR logs. You can view the logs in the LogCollector installation directory. The log file paths are as follows:
LogCollector version | Installation scenario | File path |
LogCollector version | Installation scenario | File path |
LogCollector v2.2.0 and later versions | Host scenario | /usr/local/logcollector/logs |
| Container scenario | /usr/local/container/logcollector/logs |
Logcollector versions before v2.2.0 | Host scenario | /usr/local/filebeat-7.12.0/logs |
| Container scenario | /usr/local/container/filebeat-7.12.0/logs |
Notice
After completing the above checks, if the issue persists, please submit a ticket and provide the key information found during troubleshooting in the ticket.
Last updated: 2026.06.25 16:39:46
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
