Skip to main content
POST
List SLS logstores

Restrictions

Usage

  • The datasource identified by id must be of type sls.
  • Supply project to select the SLS project whose logstores to list.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Parameters for listing SLS logstores.

id
integer<uint64>

ID of an SLS-type datasource. Obtainable via POST /monit/datasource/list.

project
string

SLS project name. Obtainable via POST /monit/datasource/sls/projects.

offset
integer

Pagination offset.

size
integer

Page size. Defaults to 200 server-side when 0.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
string[]
required

List of SLS logstore names.