A Logstore in Simple Log Service is a unit that is used to collect, store, and query logs.
A Logstore in Simple Log Service is used to collect, store, and query logs. A Logstore can belong to only one project. You can create multiple Logstores in a project.
Simple Log Service provides two types of Logstores: Standard Logstores and Query Logstores.
Standard Logstores support the following billing modes:
Pay-by-ingested-data
Pay-by-feature
Query Logstores support only the pay-by-feature billing mode.
Standard Logstore: This type of Logstore supports the log analysis feature and is suitable for scenarios such as real-time monitoring and interactive analysis. You can use this type of Logstore to build a comprehensive observability system.
Query Logstore: The index traffic fee of a Query Logstore is lower than that of a Standard Logstore. Query Logstores do not support SQL analysis. Query Logstores are suitable for scenarios in which the volume of data is large, the log retention period is long, or log analysis is not required. Log retention periods of weeks or months are considered long.
For more information, see Logstore.
Each Logstore belongs to a project. You can create multiple Logstores in a project. You can create multiple Logstores in a specific project based on your business requirements. In most cases, you can create a Logstore for each log type of an application. For example, if you want to collect the operation logs, application logs, and access logs of App A, you can create a project named app-a, and then create three Logstores named operation_log, application_log, and access_log in the project to store the logs.
You must specify a Logstore when you write, query, analyze, transform, consume, or ship logs.
Simple Log Service uses the Logstore as a collection unit to collect logs.
Simple Log Service uses the Logstore as a storage unit to store, transform, consume, and ship logs.
Simple Log Service creates indexes for the Logstore to query and analyze logs.