Manage Alert Escalation Policy

Describes the clientId or mspId of the tenant

Policy unique identifier

Users, User Groups, and Rosters to receive the escalations.

Roster is a list of users part of the schedule doing particular duty.

Escalation rules are actions taken when an alert is not acknowledged within the desired time.OpsRamp supports manual and automatic escalation types.

Enum:

MANUALAUTOMATIC

Escalation action to take - Escalate as Notification implies to send periodic notifications to users until the alert is acknowledged. - Escalate as Incident implies to automatically create an incident from the alert and assign to the desired user/team.

Enum:

NOTIFICATIONINCIDENT

Information about the escalation actions.

The time interval to escalate an alert after generation. Escalate after the alert has elapsed the set time.

A threshold limit on the number of notifications a user receives. Example: notifyLimitCount: 5

For every change in the alert state, user receives notifications.

- For escalationType: MANUAL- Users to contact directly. User ID (or) name. - For escalationType: AUTOMATIC- Recipients who receives notifications.

This string helps to differentiate between partner and client escalation policies. allClients: true indicates the policy is a partner level policy.

This string indicates that machine-learning is enabled to automatically escalate an incident to appropriate teams. - Machine-learning enabled incident attributes: Example: Assignee Group, Priority - "Assignee Group" is the Incident attribute and "incident.assigneeGroup" is the respective output column in a CSV file. - learnedFieldsToOutputColumnsMap"Assignee Group": "incident.assigneeGroup","Priority": "incident.priority"

The time interval when a user receives repeated notifications. This example indicates that a user receives repeated notifications every 15 minutes: repeatFrequency: 15.

Describes the clientId or mspId of the tenant

Policy unique identifier

Describes the clientId or mspId of the tenant

Policy unique identifier