Skip to main content
API Explorer|API Explorer
Alerting & Response/Alert Rules
PUTAlertingSince 1.0SynchronousAuth Required

ConfigureAlertEscalationRule

Configure a logging-based escalation rule for an alert rule

Execution Availability

Try It Out

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

Path Parameters

Request Inputs

Path Parameters

  • ruleIdStringRequired

    Alert rule identifier to configure escalation for

Body Fields

  • enabledBooleanRequired

    Whether to enable the escalation rule

    Example: true

  • keywordsListRequired

    Keyword patterns with severity levels

    Example: (nested array)

    • patternString

      Log keyword pattern to match

      Example: OutOfMemory

    • severityString

      Severity to assign when pattern matches

      Example: critical

  • windowSecondsIntegerRequired

    Evaluation time window in seconds

    Example: 300

  • minMatchCountIntegerRequired

    Minimum matches to trigger escalation

    Example: 3

  • scheduleIdStringRequired

    Primary on-call schedule identifier

    Example: sched-001

Responses

200 OK

On success, this API returns an empty JSON object {}.

Endpoint

PUT/api/v1/alerting/rules/{ruleId}/logging-escalation

/api/v1/alerting/rules/{ruleId}/logging-escalation

Operation ID

ConfigureAlertEscalationRule

Permalink

Request Example

curl -X PUT '{host}/api/v1/alerting/rules/{ruleId}/logging-escalation' -H 'Authorization: Bearer {token}' -H 'Content-Type: application/json' -d '{"enabled":true,"keywords":"(nested array)","windowSeconds":300,"minMatchCount":3,"scheduleId":"sched-001","escalateScheduleId":"sched-002","escalateAfterMinutes":30,"notifyContext":true}'

Response Example

200
{}

Change History

This API has no change history records yet.

View all change history