Skip to main content
POST
List SLS logstores

Restrictions

Usage

  • The datasource identified by id must be of type sls; other types fail with InvalidParameter.
  • The caller needs query access to the datasource (see readonly_team_ids on the datasource); otherwise the call fails with 403 AccessDenied.
  • Supply project to select the SLS project whose logstores to list; use offset and size to paginate. The response is a plain array of logstore names.
  • The request is relayed to the Monitors edge cluster of the datasource, which calls Alibaba Cloud with the stored credentials; it times out after 30 seconds. Fails with InvalidParameter when no edge instance of that cluster is online, and with HTTP 503 ServiceUnavailable when the edge version does not support metadata discovery.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Parameters for listing SLS logstores.

id
integer<uint64>
required

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[]

List of SLS logstore names.