Limited availability Clone an existing alert definition, for a specific service type. Run the List alert definitions operation to see all of your available definitions. These points apply to cloning:

• You need to set a new label for the clone.

• You can clone your custom user alert definitions and preset Akamai system alert definition. Cloning a system alert definition generates a user alert definition.

• Leave out optional fields from the request to keep existing settings from the clone source. If you include a field that allows you to apply multiple values, you need to include any existing values to keep them. Run the Get an alert definition operation to see the current settings for your source. If you leave an existing value out, it's removed from the clone.

• You can't change the scope for a cloned alert definition:

  • If the clone source scope is region, you can modify the region array to add or remove new regions. Leave this array out to create a new alert definition in the same regions.

  • If the clone source scope is entity, you can add new entity_ids to include additional entities. To remove current entities, leave their entity_id out.

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-clone dbaas 457 \
--label Read-Write Channel (clone)
--description New alert definition cloned from Read-Write Channel
--regions us-iad

Learn more