Beta Update an existing alert definition. Include the appropriate service_type and alert_id as path parameters. You need read_only access to the scope for the selected service_type. 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
v4betapath in its URL.Currently, only the Managed Databases (
dbaas) service type is supported.
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, entity_ids, rule_criteria, trigger_conditions, and channel_ids objects. If updating the entity_ids, rule_criteria, or channel_ids list objects, 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_idsordimension_filters(inrule_criteria) list objects, because they are optional, while all other list objects are required.
System alert definitions
These are the default alert definitions offered by Akamai. You can only edit the entity_ids list object for these alerts. All of the points above regarding editing a list object 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>