Torch Log Service
Feature | Description |
Feature | Description |
Dual editions | Provides both automation and manual interaction versions, both sharing the same tool / workflow / raw runtime semantics.
|
Wide business coverage | Covering domains such as project, log topic, index, query and analysis, alert, host group, collection rule, ETL, and consumer group. |
Comprehensive security assurance | Provides --dry-run, structured envelope, trace artifacts, and file delivery, making pre-checks, validation, and recovery more straightforward. |
Flexible credential access | Provides local profile, explicit region/endpoint, environment variables, and one-time --secrets-file injection. |
Layered usage |
|
Feature | Description |
Feature | Description |
Log project (Project) | Create, query, modify, and delete projects. |
Log topic (Topic) | Create, query, modify, and delete topics, and manage the log lifecycle. |
Index & query | Create and manage indexes, provide log query capabilities, export SQL analysis, and download raw logs. |
Metric topic | Create metric topics and support monitoring metric queries based on PromQL. |
Alarm and notification | Configure alarm policies and notification channels to ensure that business exceptions are notified within seconds. |
Dashboard | Create and manage visual dashboards for real-time insights into data changes. |
Consumer and shipper | Manage consumer groups and configure log shipping to external storage (such as TOS, Kafka, and more). |
Data transformation | Log cleansing, enrichment, distribution, and formatting. |
Host group and collector | Manage TLS host groups, configure and distribute LogCollector collection rules. |
Permission management | Supports accessing TLS via multiple authentication methods.
|
Category | Requirements |
Category | Requirements |
Operating system and architecture |
|
Installation dependencies |
|
Credentials and configuration |
Notice Dynamically obtain Volcengine credentials and other authentication information through environment variables to avoid data security risks from hardcoding the AccessKey. This can be done through profile, environment variables, --secrets-file, and other approaches. |
Large result output | For automation or sandbox environments, it is recommended to prepare a writable directory in advance and explicitly use --output-mode file --output-dir for large queries. |
Scenarios | | Trace analysis |
Scenarios | | Trace analysis |
Scenario 1 | How to integrate a new project into TLS and complete query and analysis. |
|
Scenario 2 | How to export problematic log data and view visual analysis results. |
|
Scenario 3 | How to troubleshoot when log configuration is complete but logs cannot be collected. |
|