Skip to main content
POST
Get datasource detail

Restrictions

Usage

  • Requires manage access to the datasource (see manage_team_id); members who can only query it get AccessDenied. Use /monit/datasource/list for the datasources you can query.
  • The response is sensitive: payload holds connection settings, and credentials of non-diagnostic types are returned as stored. Diagnostic passwords and Kafka private keys are returned only when they are ${env:NAME} references; tencent_cls secret_key is returned as an empty string unless it is a ${env:NAME} reference.
  • An unknown ID, or one in another account, returns ResourceNotFound.

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

Request with a single numeric ID.

id
integer<uint64>
required

Numeric ID of the target resource; the exact meaning depends on the API being called (e.g. datasource ID, ruleset ID).

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
object

A monitoring datasource.