All Products
Document Center

Simple Log Service:DeleteLogStore

Last Updated:Oct 26, 2023

Deletes a Logstore. All shards and indexes of the Logstore are deleted.

Usage notes

  • Host consists of a project name and a Log Service endpoint. You must specify a project in Host.
  • An AccessKey pair is created and obtained. For more information, see AccessKey pair.

    The AccessKey pair of an Alibaba Cloud account has permissions on all API operations. Using these credentials to perform operations in Log Service is a high-risk operation. We recommend that you use a RAM user to call API operations or perform routine O&M. To create a RAM user, log on to the RAM console. Make sure that the RAM user has the management permissions on Log Service resources. For more information, see Create a RAM user and authorize the RAM user to access Log Service.

  • The information that is required to query logs is obtained. The information includes the name of the project to which the logs belong and the region of the project. For more information, see Manage a project.
  • Before you can delete a Logstore, you must delete all Logtail configurations that are associated with the Logstore. For more information, see Delete a Logtail configuration.
  • If you delete all Logstores, you are still charged for data storage on the day that you delete the Logstores, but no charges are incurred from the following day. As a result, from the third day after you delete all Logstores, you no longer receive a Log Service bill.
  • After you delete a Logstore, all logs in the Logstore are deleted and cannot be restored. Proceed with caution.

Authentication resources

The following table describes the authorization information that is required for this operation. You can add the information to the Action element of a RAM policy statement to grant a RAM user or a RAM role the permissions to call this operation.





OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request headers

This operation uses only common request headers. For more information, see Common request headers.

Request syntax

DELETE /logstores/{logstore} HTTP/1.1

Request parameters


The name of the project.


The name of the Logstore.

Response parameters


The name of the server.


The type of the response body.


The length of the response body.


Indicates whether the connection is persistent. Valid values:

  • close: The connection is non-persistent. A new TCP connection is established for each HTTP request.
  • keep-alive: The connection is persistent. After a TCP connection is established, the connection remains open, and no more time or bandwidth is consumed to establish new connections.
DateStringSun, 27 May 2018 08:25:04 GMT

The time when the response was returned.


The request ID.


Sample requests

DELETE /logstores/logstoreName HTTP/1.1

Common request parameters

Sample success responses

JSON format

HTTP/1.1 200 OK

Error codes

For a list of error codes, see Service error codes.

HTTP status code

Error code

Error message




Project does not exist.

The specified project does not exist.



Logstore does not exist.

The specified Logstore does not exist.



invalid request method: /logstores/logstoreName

The value of logstoreName is invalid.



Specified Server Error Message.

An internal server error has occurred.

For more information, see Common error codes.