Update datasource
Update an existing data source. Supply id plus the fields to change.
Restrictions
Usage
- Every call is recorded in the account audit log. Don’t put secrets in request fields.
Credential fields
Theinfo / create / update responses include the payload configuration exactly as stored — password, basic_auth_password, api_key, service_token, access_key_secret, tls_key, tls_key_pwd and similar fields are returned as-is, not masked. Treat these responses as sensitive: avoid logging them or forwarding them to third parties.Authorizations
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
Request body for creating or updating a datasource. id is required only for update. address is required for all types except Elasticsearch with deployment=cloud.
Datasource type identifier. Allowed: prometheus, loki, mysql, oracle, postgres, clickhouse, elasticsearch, sls, victorialogs.
Datasource display name. This is the name referenced as ds_name in query and diagnose APIs.
Type-specific configuration block. Must include the key matching type_ident.
Monitors edge cluster name responsible for evaluating rules using this datasource.
Datasource ID. Required for update; omit for create.
Optional description.
Connection address. For Prometheus/Loki/VictoriaLogs: HTTP URL. For MySQL/Oracle/Postgres/ClickHouse: host:port. For SLS: endpoint without http/https prefix. Not required for Elasticsearch cloud deployment.
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.