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

Torch Log Service

Copy page
Download PDF
Data collection
Import SLS collection configuration
Copy page
Download PDF
Import SLS collection configuration
In scenarios such as cross-service data migration, you can use the TLS import collection configuration feature to batch import log collection configurations from other cloud providers. This topic describes how to import SLS collection configurations.​
Background information​
In scenarios like application migration and cross-service data migration, you need to batch migrate existing log data to TLS and batch migrate collection configurations in applications. In doing so, you can quickly apply the collection configurations in TLS and improve migration efficiency. Currently, TLS supports importing log collection configurations from Alibaba Cloud SLS. The imported collection configurations include collection rules such as the Logstore for log writing; host groups are not bound; and host group resource configurations and index configurations are not included.​
Notice​
  • If the name of the imported collection configuration duplicates an existing one, TLS will update the existing collection configuration based on the imported configuration.​
  • When importing collection configurations, TLS will automatically create a log topic with default settings. After the import is complete, you can refer to the original SLS Logstore’s shard configuration and modify the topic configuration as needed.​
Prerequisites​
  • A data collection configuration has been created in Alibaba Cloud Log Service (SLS).​
  • Alibaba Cloud access key has been obtained. To ensure data security, we recommend using a RAM user with read permission for the collection configuration. For details on authorization policies, see SLS RAM Authorization policy example.​
  • A project has been created in Volcanoengine TLS. For more details, see Log project.​
  • Before using this feature for the first time, you need to authorize access to cloud resources by granting TLS permission to access and write to resources. If authorization has not yet been granted, TLS will guide you through the process when you create an import task in the console. We recommend using the Volcanoengine primary account for authorization. For more information, refer to cross-service access authorization.​
Create data collection configuration import task​
  1. Select the region where torch log service is located from the top navigation bar.​
  1. On the left navigation bar, select Common functions > Log collection.​
  1. On the LogCollector Log Collection tab, click Alibaba Cloud Collection Configuration.​
  1. Fill in the following task settings and click Submit.​
  • ​
    Configuration​
    Description​
    Import source​
    It is fixed to Alibaba Cloud SLS configuration.​
    Log project​
    Select the project to import the collection configuration.​
    Task name​
    Name of the collection configuration import task.​
    Source domain name​
    Service endpoint of Alibaba Cloud Log Service SLS. See Service endpoint for viewing method.​
    Access key​
    Access key of your Alibaba Cloud account or RAM user. For viewing instructions, see Access Key.​
    To ensure data and information security, we recommend using RAM user keys with the required permissions. For authorization policy, see SLS RAM Authorization policy example.​
    Project​
    Project in Alibaba Cloud Log Service SLS, used to specify which project’s collection configurations to import.​
    Import item​
    Select the SLS collection configuration from Volcanoengine TLS to be imported.​
    ​
After creating the import task, you can view basic information about the import task on the collection configuration import list page. The import task list page displays the name, ID, import status, import source, import quantity, import progress, and creation time for each import task. You can check the import status to determine the running state of the import task. If an import fails, you can contact technical support through ticket for assistance.​
SLS RAM Authorization policy example​
If you use a RAM user to import SLS collection configuration and read SLS configuration information, you must grant the RAM user permissions for the project and related collection configuration. The recommended authorization policy is as follows:​
​
{​
"Version": "1",​
"Statement": [​
{​
"Effect": "Allow",​
"Action": [​
"log:GetConfig",​
"log:ListProject"​
],​
"Resource": [​
"acs:log:*:*:project/*/logtailconfig/*",​
"acs:log:*:*:project/*"​
]​
}​
]​
}​
​
Next steps​
  • The imported collection configuration is not bound to any host group by default. You need to manually update the host group for the collection configuration and bind it to the specified host group for the configuration to take effect.​
  • The automatically created log topic does not have an index set. You can set an index for the log topic based on the original SLS Logstore index configuration.​
​
Last updated: 2026.01.08 16:51:06