- About LogicMonitor
- AIOps
- Alerts
- Certification
- Cloud Monitoring
- Collectors
- Dashboards and Widgets
- Devices
- Getting Started
- LM Service Insight
- LogicModules
- Mobile
- Monitoring
- Reports
- Rest API Developers Guide
- REST API Overview
- REST API v1
- REST API v1 Examples
- REST API v1 Status Codes
- Managing Ops Notes with the REST API
- Managing Alert Rules with the REST API
- Managing Alerts with the REST API
- Managing API Tokens with the REST API
- Accessing Audit Logs with the REST API
- Managing Collectors with the REST API
- Managing Collector Groups with the REST API
- Managing Dashboards and Widgets with the REST API
- Managing Dashboard Groups with the REST API
- Getting Data with the REST API
- Managing Datasources with the REST API
- Managing Datasource Instances with the REST API
- Managing Devices with the REST API
- Managing Device Groups with the REST API
- Get devices for a particular device group
- Get all alerts for a Device Group
- AWS Device Groups
- Delete Device Group Properties
- Update Device Group Properties
- Get Device Group Properties
- Add Device Group Properties
- Get all SDTs for a Device Group
- Delete a Device Group
- Get Device Groups
- Update a Device Group
- Add a Device Group
- About the Device Group Resource
- Managing Escalation Chains with the REST API
- Managing Reports with the REST API
- Managing Report Groups with the REST API
- Managing Roles with the REST API
- Managing SDTs with the REST API
- Managing Websites with the REST API
- Managing Website Groups with the REST API
- Getting Websites Test Locations with the REST API
- Managing Thresholds with the REST API
- Managing Users with the REST API
- REST API v2
- LogicMonitor SDKs
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Settings
- Terminology and Syntax
- Websites
Update an Escalation Chain
You can use LogicMonitor’s REST API to update the Escalation Chains in your account.
As with all of our API calls, authentication is required
HTTP Method:
PUT
*Note that consistent with REST standards, any properties not specified in a PUT request will revert back to their default values
URI:
/setting/alert/chains/{id}
Where id should be replaced with the id of the escalation chain you’d like to update. You can get escalation chain ids via a GET request to the escalation chains resource.
Request Parameters:
Property |
Description |
Required? |
Type |
Example |
| name | The name of the Escalation Chain | Yes | String | “name”:”MyEscalationChain” |
| description | The description associated with the Escalation Chain | No. Defaults to no description | String | “description”:”routes to the on call engineer” |
| enableThrottling | Whether or not throttling (rate limiting) is enabled for this Escalation Chain. If true, throttlingPeriod and throttlingAlerts indicate how alerts will be throttled. | No. Defaults to false | Boolean | “enableThrottling”:false |
| throttlingPeriod | The throttling (rate limit) period if enableThrottling is true, in minutes | Only if enableThrottling=true | Integer | “throttlingPeriod”:30 |
| throttlingAlerts | If enableThrottling is true, throttingAlerts indicates the maximum number of alerts that can be routed in the throttlingPeriod. | Only if enableThrottling=true | Integer | “throttlingAlerts”:40 |
| destinations | The destinations associated with the Escalation Chain. For non-time based escalation chains, the destination object consists of a stages object and type=single, and each stage includes a type (admin | arbitrary | group), a method (for type=admin values can be email | sms, for type=arbitrary value must be email, does not apply for type=group), and addr (the username for type=admin, recipient group for type=group and email for type=arbitrary). For time based escalation chains, the destination object consists of one or more objects, each with type=timebased, a period (includes fields startMinutes (0-1440), endMinutes(0-1440) and weekDays(should be an array with days, where options are 1-7, e.g. [1, 2, 3, 4, 5, 6, 7])), and a stages object (see above re non-time based chains for info about stages object). Note that prior to v89/90, the stages object must be enclosed in double brackets, as shown in the example. | Yes | JSON Object | “destinations”:[{“type”:”single”,”stages”:[[{“type”:”admin”,”method”:”sms”,”addr”:”Bob”},{“type”:”group”,”addr”:”OnCallGroup”},{“type”:”arbitrary”,”method”:”email”,”addr”:”[email protected]”}]]}] |
| ccDestinations | CC recipients – these recipients will receive all notifications sent to every stage. Each ccDestination (recipient) will include a type (always is ARBITRARY), method (always is email), and addr (email address) | No. Defaults to no CC recipients | JSON Object | “ccDestinations”:[{“type”:”arbitrary”,”method”:”email”,”addr”:”[email protected]”}] |
In this Article: