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 ServiceUser GuideData collectionCloud product log collectionVolcano Ark application lab log collectionCollect Volcano Ark Application Lab logs
Copy page
Download PDFVolcano Ark application lab log collection
Collect Volcano Ark Application Lab logs
Copy pageDownload PDFCollect Volcano Ark Application Lab logs
This document introduces the features and collection methods related to Volcano Ark Application Lab logs.
Feature overview
The Volcano Ark large model service platform Application Lab provides platform services for quickly building applications based on large models, targeting enterprise developers and ecosystem partners with varying development capabilities, offering zero-code, low-code, and high-code modes.
Ark high-code applications are based on veFaaS function services and other cloud products, providing a convenient online deployment process and a production-grade runtime environment. After enabling the Trace log service, the system automatically collects the input and output of requests and the time consumed at each stage, recording them in TLS for subsequent operations and troubleshooting.
The relevant configuration is as follows:
Configuration | Description |
Configuration | Description |
Log type | High-code application logs. |
Log storage location | In Ark high-code applications, after enabling log analysis, TLS automatically creates a Trace instance, the corresponding project, and log topic. For details on managing log resources, please refer to Manage Volcano Ark Application Lab log resources.
|
Log storage period | The default is 30 days. |
Log shard |
|
Index settings | Index is automatically configured. |
Log fields |
Collecting Ark high-code application logs
For usage restrictions, enabling log analysis operations, and more details, please refer to High-code Application Creation and Deployment Guide.
Ark high-code application log fields
Trace log fields
Field | Description |
Field | Description |
Name | Span name. |
TracelD | Trace ID. |
SpanID | Span ID. |
TraceState | Trace extended state information. |
ParentSpanID | ID of the parent Span. |
Kind | Type of the Span. |
Start | Start timestamp of the current Span. |
End | End timestamp of the current Span. |
Duration | Duration of the current Span, used to measure the time consumed by this invocation. |
Attributes | A set of key-value pair labels attached to the Span, used to record additional context information. |
Events | List of events that occur during the Span lifecycle. |
Links | Relationships with other Traces/Spans. |
StatusCode | The final status code of the Span. |
StatusDescription | Textual description of the StatusCode. |
Resource | Set of resource-level common attributes. |
ServiceName | Service name. |
Host | Host information where the Span is executed. |
OTLPName | Name of the OpenTelemetry-related component that generates logs/Traces, such as the SDK or Exporter name used. |
OTLPVersion | Version number corresponding to OTLPName, used to distinguish data reported by different versions of the SDK/Exporter. |
Dependency log fields
Field | Description |
Field | Description |
Version | Version number of the dependency statistics or structure. |
ServiceName | Service name to which the current record belongs. |
Kind | Dependency type/direction. |
ParentServiceName | The other service name that has a dependency relationship with ServiceName. |
CallCount | Number of calls between ServiceName and ParentServiceName during the statistical period. |
OperationName | Specific operation/interface name. |
__task_id__ | ID of the scheduled SQL analysis task. |
__process_id__ | Instance ID that executes this scheduling calculation in the scheduled SQL analysis task. |
__process_start_time__ | Start time of the SQL time window for the scheduled SQL analysis task. |
__process_end_time__ | End time of the SQL time window for the scheduled SQL analysis task. |
__process_time__ | Scheduling time of the instance, that is, by default, the backend service starts generating running instances. |
__schedule_time__ | Execution time of the instance, that is, the actual start time of the instance for the scheduled SQL analysis task. |
Last updated: 2026.02.12 18:03:21
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
