All Products
Search
Document Center

Simple Log Service:Resource management overview

Last Updated:Mar 11, 2025

Simple Log Service enables resource management of projects and logstores through the Simple Log Service console, API operations, SDKs, and command-line interface (CLI).

Prerequisites

  1. You have an Alibaba Cloud account.

  2. Simple Log Service is activated.

    Note

    Upon activation of Simple Log Service, a service-linked role named AliyunServiceRoleForSLSAudit is automatically created.

  3. To manage Simple Log Service using the API, SDK, or CLI, create an AccessKey pair.

  4. To manage it as a RAM user, create a RAM user and grant permissions.

Resource management

image

A project is the primary resource container in Simple Log Service, containing logstores, metricstores, and eventstores. It provides an endpoint to access the resources in the project. Resource management allows you to adjust quotas at the project level to control costs and prevent waste. At the store level, you can adjust the number of shards for performance, organize resources using groups and tags, and improve long-distance log transmission.

  1. Create and manage Simple Log Service projects.

    1. Initially, create a project in the desired region based on your business needs.

    2. A project supports dynamic allocation of multiple metrics. You can adjust resource quotas according to your actual needs to ensure resource availability. Also, consider whether to modify the resource quota based on resource throttling and solutions.

  2. Create storage resources.

  3. Simple Log Service uses shards to manage the read and write capabilities of logstores, eventstores, and metricstores. Adjust the number of shards to control the maximum read and write capabilities of Simple Log Service.

  4. For long-distance log transmission, such as writing logs from outside China to the Chinese mainland, enable transfer acceleration.

  5. Simple Log Service offers resource groups to isolate access privileges in various scenarios and implement permission management within resource groups.

Comparison of logstore, metricstore, and eventstore

Store

Data type

Scenarios

Related links

Logstore

General logs

Used to store application or system-generated logs, such as error logs and access logs.

Logstore

Manage a logstore

Metricstore

Time series data that follows the Prometheus data model, such as metric naming conventions, label mechanisms, and data retention policies.

Used to store performance metrics that are commonly used in storage systems or applications, such as CPU utilization and memory usage.

Metricstore

Manage a metricstore

Eventstore

Event data that follows the CloudEvents protocol.

Used to store system or application-generated data about specific activities or actions, such as user clicks and transactions.

Eventstore

Manage an eventstore