Create datasource
Create a new monitoring data source. The payload must include the type-specific configuration block.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Datasources Manage (monit) |
Usage
type_identmust be one of:prometheus,loki,mysql,oracle,postgres,clickhouse,elasticsearch,sls,victorialogs.edge_cluster_namespecifies which Monitors edge cluster evaluates rules using this datasource.- For
elasticsearch, setpayload.elasticsearch.deploymenttocloudorself-managed. - Every call is recorded in the account audit log. Don’t put secrets in request fields.
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.
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.