Skip to main content
Alerting & Response/Alert Rules
POSTAlertingSince 1.0SynchronousAuth Required

CloneAlertRule

Clone an existing alert rule with a new name and identifier

Execution Availability

Try It Out

Submit a mock request using the current auth context and example-driven inputs.

Path Parameters

Query Parameters

Request Inputs

Path Parameters

  • ruleIdStringRequired

    UUID of the rule to clone

Query Parameters

  • tenantIdString

    Tenant identifier for the clone operation Tenant identifier for the clone operation

Responses

200 OK

On success, this API returns the following response structure.

  • idString

    UUID of the newly created clone

    Example: rule-new456

  • originalIdString

    UUID of the original rule that was cloned

    Example: rule-abc123

  • nameString

    Name of the cloned rule (auto-suffixed)

    Example: High CPU Usage (copy)

Endpoint

POST/api/v1/alerting/rules/{ruleId}/clone

/api/v1/alerting/rules/{ruleId}/clone

Operation ID

CloneAlertRule

Permalink

Request Example

curl -X POST '{host}/api/v1/alerting/rules/{ruleId}/clone' -H 'Authorization: Bearer {token}' -H 'Content-Type: application/json' -d '{}'

Response Example

200
{
  "id": "rule-new456",
  "originalId": "rule-abc123",
  "name": "High CPU Usage (copy)"
}

Change History

This API has no change history records yet.

View all change history