Updates the attributes of a Logstore.

Usage notes

  • Host consists of a project name and a Log Service endpoint. You must specify a project in Host.
  • You can call the UpdateLogStore operation to change only the time-to-live (TTL) attributes.

Debugging

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

PUT /logstores/{logstore} HTTP/1.1

Request parameters

ParameterTypePositionRequiredExampleDescription
projectStringHostYesali-test-project

The name of the project.

logstoreStringPathYestest-logstore

The name of the Logstore.

ObjectBodyYes

The body of the request.

logstoreNameStringBodyYestest-logstore

The name of the Logstore.

shardCountIntegerBodyYes2

The number of shards.

Note You cannot call the UpdateLogStore operation to change the number of shards. You can call the SplitShard or MergeShards operation to change the number of shards.
ttlIntegerBodyYes30

The retention period of log data. Unit: days. Valid values: 1 to 3650. If you set this parameter to 3650, data is permanently stored.

encrypt_confEncryptConfBodyNo

The data structure of the encryption configuration.

autoSplitBooleanBodyNotrue

Specifies whether to enable automatic sharding. Valid values:

  • true
  • false
enable_trackingBooleanBodyNofalse

Specifies whether to enable the web tracking feature. Default value: false. Valid values:

  • true
  • false
appendMetaBooleanBodyNofalse

Specifies whether to record public IP addresses. Default value: false. Valid values:

  • true
  • false
maxSplitShardIntegerBodyNo64

The maximum number of shards into which existing shards can be automatically split. Valid values: 1 to 256.

Note If you set autoSplit to true, you must specify maxSplitShard.
telemetryTypeStringBodyNoNone

The type of the observable data. Valid values:

  • None (default): logs.
  • Metrics: metrics.
hot_ttlIntegerBodyNo60

The retention period of log data in the hot storage tier of the Logstore. Unit: days. Valid values: 7 to 3000.

Hot data that is stored for longer than the period specified by hot_ttl is converted to cold data. For more information, see Enable hot and cold-tiered storage for a Logstore.

modeStringBodyNostandard

The type of the Logstore. Log Service provides two types of Logstores: Standard Logstores and Query Logstores. Valid values:

  • standard: 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 also use this type of Logstore to build a comprehensive observability system.
  • query: Query Logstore. This type of Logstore supports high-performance queries. The index traffic fee of a Query Logstore is approximately half that of a Standard Logstore. Query Logstores do not support SQL analysis. Query Logstores are suitable for scenarios in which the amount of data is large, the log retention period is long, or log analysis is not required. If logs are stored for weeks or months, the log retention period is considered long.

Response parameters

ParameterTypeExampleDescription
ServerStringnginx

The name of the server.

Content-TypeStringapplication/json

The content type of the response body.

Content-LengthString0

The content length of the response body.

ConnectionStringclose

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.

x-log-requestidString5B0A6B60BB6EE39764D458B5

The request ID.

Examples

Sample requests

PUT /logstores/test-logstore HTTP/1.1
Host:ali-test-project.cn-hangzhou.log.aliyuncs.com
Content-Type:application/json

{
  "logstoreName" : "test-logstore",
  "shardCount" : 2,
  "ttl" : 30,
  "encrypt_conf" : {
    "encrypt_type" : "default",
    "user_cmk_info" : { }
  },
  "autoSplit" : true,
  "enable_tracking" : false,
  "appendMeta" : false,
  "maxSplitShard" : 64,
  "telemetryType" : "None",
  "hot_ttl" : 60,
  "mode" : "standard"
}

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

Description

404

ProjectNotExist

Project does not exist.

The specified project does not exist.

404

LogStoreNotExist

Logstore does not exist.

The specified Logstore does not exist.

500

InternalServerError

Specified Server Error Message.

An internal server error has occurred.

For more information, see Common error codes.