Create a SessionStore - Simple Log Service - Alibaba Cloud Documentation Center

Prerequisites

The preparations and service authorization are complete, and you have determined whether to use the direct write mode or the reference mode. For more information about the differences between the two modes, see SessionStore overview.

Procedure

Log on to the Simple Log Service console and open the destination project.
In the left-side navigation pane, select SessionStore. Use the creation entry in the resource panel, or click Create SessionStore on the list page.
In the Create SessionStore panel, configure the basic information and the data ingestion settings.
Make sure that the service authorization check is passed.
Configure the properties and advanced properties of the SessionStore. For the first verification, you can retain the default values.
Click Create and wait until the page returns a clear result.
After the SessionStore is created, open it from the list or the resource panel and check the overview information.

Important

The data format, ingestion mode, and referenced data source cannot be modified after creation. Do not create a SessionStore with an arbitrary format and plan to switch the format on the modification page later.

Basic information and data ingestion

Parameter	Description	Default value or requirement
SessionStore Name	Identifies the resource in the current project	Required. The input box allows up to 63 characters. Use a name that is not in use. The server also checks whether the name is valid.
Raw Data Format	Determines how the data is interpreted	Default value: OpenTelemetry Trace. You can also select OpenTelemetry Log Ebpf or OpenTelemetry Log AI Gateway.
Raw Data Source	Specifies whether to write new data directly or reference existing logs	Default value: Write Directly to SessionStore.
Source Project	The project to which the referenced data belongs	Required only when you select Associate Existing Logstore. The source project must belong to the same account and reside in the same region as the destination project.
Source Logstore	The standard Logstore that actually generates the raw data	Required only for the reference mode. Make sure that the actual data format matches the selected format.
Service Authorization	Allows Simple Log Service to read raw data and generate results	The default role check must be passed.

Note: You do not need to select a source Logstore in direct write mode. The reference mode does not modify the collection configurations, indexes, or retention period of the source Logstore on your behalf.

Data retention policy

Intelligent tiered storage disabled

By default, data is retained for 30 days in hot storage. You can select Specified Days or Permanent Storage.

Specified Days indicates that data that exceeds the retention period expires based on the retention policy. Permanent Storage indicates that data does not automatically expire after a limited number of days. It does not mean that no storage fees are incurred.

Important

The current console uses 3650 as a special value for permanent storage, and you are prompted to confirm when you enter this value. Do not interpret this value as automatic deletion after 10 years. If you need a limited retention period, select the actual number of days.

Intelligent tiered storage enabled

Suitable for data that is frequently queried in the near term and occasionally traced back in the long term. Based on your business requirements, you can transition data from hot storage to IA storage, from hot storage to Archive storage, or from hot storage to IA storage and then to Archive storage.

The current console has the following configuration requirements.

Transition method	Configuration requirement
Hot storage → IA storage → Deletion upon expiration	Hot storage: at least 7 days. IA storage: at least 1 day.
Hot storage → Archive storage → Deletion upon expiration	Hot storage: at least 30 days. Archive storage: at least 60 days.
Hot storage → IA storage → Archive storage → Deletion upon expiration	Hot storage: at least 7 days. IA storage: at least 30 days. Archive storage: at least 60 days.

For permanent storage, the final storage tier is retained based on the page configuration, and the deletion upon expiration is no longer calculated based on a limited total number of days.

Note: Switching between Specified Days and Permanent Storage resets the tiered storage configuration. Check the settings of each tier again. IA storage and Archive storage are suitable for different access frequencies. Before you make a selection, learn about the related query performance and billing rules. Do not assume that all tiers have the same performance.

In reference mode, the preceding settings adjust only the retention policy of the results that are processed by the SessionStore, and do not modify the retention period of the raw logs in the source Logstore.

Advanced properties

Parameter	Purpose	Default value
Shards	Specifies the initial number of shards	2. The form allows an integer from 1 to 64. After creation, you cannot directly modify this value on the resource modification page.
Automatic Sharding	Enables automatic sharding based on service capabilities	Enabled.
Maximum Shards	The upper limit when automatic sharding is enabled	64. The form allows an integer from 1 to 64.
WebTracking	Enables web tracking as required by the collection solution	Disabled. You do not need to enable this feature to create the SessionStore for a regular initial ingestion.

The input ranges of the form do not represent account resource quotas or throughput guarantees. Plan the capacity based on the actual traffic and service quotas.

Creation results and exception handling

Result	Recommended action
Created	Open the overview page to check the configurations, and then ingest data.
A parameter or permission error is explicitly reported	Keep the form, fix the issue based on the error message, and then try again.
The system prompts that the resource creation result is not confirmed	Check the list to see whether a resource with the same name already exists, and contact the administrator if necessary. Do not create the resource repeatedly.
The resource is created, but the field configuration fails	Keep the current panel and click Retry Field Configuration or Reload Configuration as prompted. For more information, see the custom fields section.

If a failure occurs, record the error code, the message, and the request ID that is available on the page. Do not provide your cookies, AccessKey pairs, or complete sensitive logs to others.