You need to enable JavaScript to run this app.
Torch Log Service

Torch Log Service

Copy page
Download PDF
iOS SDK( v2.x)
iOS SDK Overview (v2.x)
Copy page
Download PDF
iOS SDK Overview (v2.x)
Volcano Engine TLS iOS SDK v2.x wraps the logging collection interface of TLS, providing an asynchronous log upload producer for Apple platforms (VolcengineTLSProducer) with high-throughput async log writing capability for iOS and native macOS applications.​
Description​
For the release notes and version information of the Volcano Engine TLS iOS SDK, see GitHub. We recommend using the latest SDK version for enhanced product features and more stable service.​
iOS SDK v2.x only handles log upload and does not offer interfaces for query, consumption, alert, or data transformation. It supports Swift and Objective-C.​
Sample projects​
TLS iOS SDK provides sample projects for your reference. For details, see the Github sample repository.​
​
GitHub source code​
Notice​
Async log upload Producer for Volcengine TLS on Apple platforms​
  • Provides Swift and Objective-C interfaces but is not compatible with v1.x class names and methods​
  • Supports iOS, iPadOS, and native macOS, offering batch processing, compression, retry, backpressure, and optional WAL​
​
Reference​
​
Reference​
Notice​
VolcengineTLSProducer offers high-throughput asynchronous log writing for iOS and native macOS applications It completes local reception on the calling thread and then aggregates, compresses, and sends logs in the background​
Environment requirements, installation steps, and version selection for the VolcengineTLSProducer SDK.​
Upload logs using Producer v2 without adding Swift source files to the business target The SDK still includes Swift internally for sharing implementation with Swift Producer, but it is not a compatibility layer for the old v1.x client​
Successfully returning from add alone does not confirm completion. Verification should cover local reception, batch callback, and server-side query.​
ProducerConfiguration is a mutable value type. Parameters are validated during initialization, and Producer.open validates and saves the configuration again at that time. After opening successfully, modifying the original configuration does not affect the running Producer.​
Compatibility of product platforms, toolchains, and access methods​
Data persistence helps restore unconfirmed data after an exception exit, device restart, or extended offline periods. Provides at-least-once delivery assurance, but does not support exactly-once.​
When troubleshooting, first determine where the failure occurs: open, local add, asynchronous batch callback, server-side query, or close. The meaning of success varies at each stage.​
Performance results are closely related to device, system, log size, persistence method, and network conditions. Related data is used to estimate resource consumption. Results are for selection and configuration reference and do not represent throughput limits or service guarantees.​
​
Last updated: 2026.10.27 17:51:00