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.

When updating an alert definition you've created, you can change the status to enabled or disabled. You can also modify the label, description, and severity. You can't update a scope, but you can update its applicable entity_ids or regions, as well as its rule_criteria, trigger_conditions, and channel_ids objects. If updating the rule_criteria, channel_ids, entity_ids, or regions fields, 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.

Permissions and scopes

To call this operation, you need permissions, based on the model you're using:

• OAuth scopes. Your user needs these scopes assigned. Learn more.

  • Scopes: monitor:read_write

CLI

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

Learn more