Simple Log Service:Manage a logstore

Console

1. Log on to the Simple Log Service console. In the Projects section, click the project that you want to manage.

2. On the Log Storage > Logstores tab, click the + icon.

   

3. On the Create Logstore page, configure the parameters and click OK.

   1. Logstore Type: The default value is Standard.

   2. Billing Mode:

      • Pay-by-feature (cannot be changed): You are billed for each resource that you use, such as storage, indexing, and read/write operations. A monthly free quota is provided to help you control costs in small-scale use cases.

      • Pay-by-ingested-data: You pay only for the raw data that you write. Storage and mainstream features are free for 30 days. This billing mode has a simpler and more cost-effective structure.

      The pay-by-ingested-data mode is ideal when your data retention period is close to 30 days and you require indexing comparable to a full-text index.

   3. Logstore Name: The name must be unique within the project. It serves as the unique identifier for the logstore and cannot be changed after the logstore is created.

   4. Data Retention Period: The default value is 30 days.

   5. Keep the default values for the other parameters. For a full list of parameters, see the following table.

   Full list of logstore parameters

   Parameter	Description
   Logstore Type	SLS logstores support two specifications: Standard and Query. Choose one based on your scenario to save costs. The Standard specification includes the complete one-stop data analytics features of SLS. It is suitable for scenarios such as real-time monitoring, interactive analysis, and building complete observability systems. The index traffic unit price for the Query specification is 29% of the Standard specification. This lets you enable indexes for more fields for the same cost. The Query specification supports only keyword search and does not support statistical analysis.
   Billing Mode	Pay-by-feature: This is the original billing mode of SLS. You are billed for the resources that you use, such as storage and indexes, and features, such as data transformation and data shipping. You are charged on a pay-as-you-go basis. Pay-by-ingested-data: This is a simplified billing mode of SLS. You are charged mainly for the amount of raw data that you write to SLS. After data is written to SLS, store the data and use features such as data transformation and data shipping for free for 30 days. This billing mode is simple, predictable, and controllable. It helps you make full use of SLS to mine more data value.
   Logstore Name	The logstore name must be unique within a project and cannot be changed after creation.
   WebTracking	Enables the collection of user access data from web browsers and mobile apps (iOS/Android). This feature is disabled by default.
   Data Retention Period	The number of days to retain log data before it is automatically deleted. Valid values: 1 to 3650. A value of 3650 indicates permanent storage.
   Intelligent Tiered Storage	Automatically moves data to lower-cost storage tiers based on its age using the lifecycle management feature. Hot storage: Hot storage is a scalable and high-availability data storage solution for frequently accessed data. It supports real-time data access and provides high-performance log query and analysis functions. It is suitable for business scenarios that require frequent data queries and analysis. IA storage class The IA storage class (formerly cold storage) is a storage class that can reduce your long-term storage costs while ensuring that log query, analysis, visualization, alerting, shipping, and transformation capabilities are not affected. It is suitable for business scenarios that require infrequent queries and analysis, such as issue tracing. Archive Storage Archive Storage provides a lower-cost, queryable, and analyzable long-term data storage solution based on the existing Hot and IA storage classes. It is suitable for business scenarios that require long-term storage of audit data.
   Shards	Each shard supports a write throughput of 5 MB/s and a read throughput of 10 MB/s. If the data traffic exceeds the service capabilities of a shard, split the shard. If the data traffic does not reach the maximum read and write capabilities of a shard, merge shards to save costs.
   Automatic Sharding	If the write volume to a shard exceeds its read/write capacity for more than 5 minutes, enable this feature to automatically increase the number of shards based on the data volume.
   Maximum Shards	After you enable automatic sharding, a maximum of 256 shards can be automatically created.
   Log Public IP	After logs are received, the public IP address of the client and the time when the logs arrive at the server are automatically added.

API

CreateLogStore

Console

In the Basic Information section, click Modify, change the data retention period, and then click Save.

Simple Log Service does not support deleting specific log entries. You can delete logs based on time by modifying the log retention period. Alternatively, you can delete all logs by stopping billing or deleting the Logstore.

API

UpdateLogStore operation, set the value of ttl to adjust the log retention period.

Console

1. In the Basic Information section, click Modify and enable Intelligent Tiered Storage.

2. Configure the Storage Policy. The total retention period across all three storage tiers must match the Data Retention Period.

   • Hot storage: at least 7 days.

   • The minimum storage duration for the IA storage class is 30 days.

   • Archive storage: at least 60 days.

3. Click Save. For more information, see Intelligent tiered storage.

API

In the UpdateLogStore operation, set the values of ttl, hot_ttl, and infrequentAccessTTL to dynamically adjust the retention policy for tiered storage.

Console

In the Basic Information section, click Modify, enable WebTracking, and then click Save.

API

UpdateLogStore operation, set the enable_tracking parameter to true to enable the web tracking feature.

Console

In the Basic Properties section, click Modify, enable the Log Public IP switch, and then click Save.

API

In the UpdateLogStore operation, use the appendMeta parameter to enable public IP address logging.

Console

In the Basic Information section, click Modify, enable Automatic Sharding, set the Maximum Shards, and then click Save.

SLS lets you split and merge a specific shard.

API

SplitShard.

MergeShards.

Console

1. Perform cleanup before deletion.

   1. Before you delete a logstore, delete all its associated Logtail configurations.

   2. If data shipping is enabled for the logstore, stop writing new data to the logstore and make sure that all existing data in the logstore is shipped before you delete the logstore.

2. Deletion procedure.

   1. On the Log Storage > Logstores tab, hover over the target logstore and choose Delete.

   2. In the Warning dialog box, click Confirm Deletion.

3. After deletion.

   1. Storage fees are incurred on the day you delete the logstore. No fees are generated from the following day onward.

   2. After you delete a logstore, the export tasks, data transformation jobs, and Scheduled SQL tasks that use the logstore as a data source and the import tasks that use the logstore as a destination are also deleted.

API

Delete Logstore