errors.alert-rules.list

List a project’s alert rules and their latest firings

GET /errors/api/projects/{id}/alert-rulesIAM errors:ListAlertRulesRead

Request syntax

GET /errors/api/projects/{id}/alert-rules

Path parameters

  • idRequired

    string

    Constraints: uuid

Response

200 with { rules, firings }: `rules` oldest first (id, projectId, name, enabled, trigger, filters, actions, throttleMinutes, createdAt, updatedAt); `firings` the project’s latest 50 (id, ruleId, ruleName, subject, summary, firedAt, result). 404 when the project does not exist, 403 without errors:ListAlertRules on it.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow errors:ListAlertRules on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud errors alert-rules list id

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_errors_alert-rules_list.