Update an alert definition

Beta Update an existing alert definition. You need read_only access to the OAuth scope for the selected serviceType. Only include the objects in the request that you want to update. Leave any object out of the request to leave it set as is.

📘

This operation is beta. Call it using the v4beta path in its URL.

User alert definitions

When updating an alert definition you've created, you can change the status to enabled or disabled. You can also modify the label, description, severity, scope and its applicable entity_ids or regions, rule_criteria, trigger_conditions, and channel_ids objects. If updating the rule_criteria, channel_ids, entity_ids, or regions parameters, these points apply:

• If you want to keep an existing item, you need to include it in the list.

• If you want to remove an existing item, leave it out of the list.

• To add a new item, include it in the list.

• You can't pass an empty list to remove all items. This doesn't apply to the entity_ids, regions, or dimension_filters (in rule_criteria) list objects, because they are optional, while all other list objects are required.

• If you change the scope of an existing definition, you need to include the appropriate list item for the new type: entity_ids for a scope of type entity, regions for a scope of type region, and no additional items for a scope of type account.

System alert definitions

These are the default alert definitions offered by Akamai. You can only edit the scopes object and its applicable parameters -- entity_ids for a scope type of entity, or regionsfor ascopetype ofregion`. All of the points above regarding editing a list apply here, too.

​​​​​

monitor:read_write

<https://techdocs.akamai.com/linode-api/reference/get-started#oauth>

linode-cli alerts definition-update dbaas 457 \
--status disabled \
--label Read-Write Channel (old)

<https://techdocs.akamai.com/cloud-computing/docs/getting-started-with-the-linode-cli>