Create ruleset
Create a new ruleset in the rule repository.
Restrictions
| Aspect | Value |
|---|---|
| Rate limits | 1,000 requests/minute; 50 requests/second per account |
| Permissions | Rule Repository Manage (monit) |
Usage
open_flag:0= private (creator only),1= account-shared,2= public.payloadis a required JSON string containing the alert rule definitions.- 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 a ruleset. All fields are validated by Validate() on the server.
Datasource type identifier this ruleset applies to, e.g. prometheus.
Description or title of the ruleset.
JSON string containing the alert rule definitions.
Sharing scope. 0 = private (creator only), 1 = account-shared, 2 = public. Defaults to 0 if omitted.
0, 1, 2 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.