Delete the Azure Alerts Management Smart Detector Alert Rule.


Azure > Alerts Management > Smart Detector Alert Rule

Azure > Alerts Management > Smart Detector Alert Rule > Delete

Process events for Azure Alerts Management service Smart Detector Alert Rule resources.

The router receives events from the event handler and creates, updates, or deletes Smart Detector Alert Rule resources in the CMDB.


Azure > Resource Group

Azure > Alerts Management > Smart Detector Alert Rule > Router

Update the tags for Azure Alerts Management smart detector alert rule.


Azure > Alerts Management > Smart Detector Alert Rule > Set Tags

Take an action when an Azure Alerts Management smart detector alert rule is not active based on the&#92;n`Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Active &gt; * policies`.&#92;n&#92;nThe Active control determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated compliance&#92;nenvironment, it&#39;s common to end up with a wide range of alarms that are difficult&#92;nand time consuming to clear. The Active control brings automated, well-defined&#92;ncontrol to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

Azure > Alerts Management > Smart Detector Alert Rule > Active > Age

Azure > Alerts Management > Smart Detector Alert Rule > Active > Last Modified

Azure > Alerts Management > Smart Detector Alert Rule > Active > Status

Azure > Alerts Management > Smart Detector Alert Rule > Active

This control serves as a hierarchical parent for more specific Allowed controls, such as region-based controls and custom rule-based controls.&#92;n

Azure > Alerts Management > Smart Detector Alert Rule > Allowed

Take an action when an Azure Alerts Management smart detector alert rule is not allowed based on custom rules.&#92;n&#92;nThe `Allowed &gt; Custom` control checks if the smart detector alert rule is allowed based on the `Allowed &gt; Custom &gt; *` policies. If the smart detector alert rule is not allowed, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete if not allowed and resource is new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n

Azure > Alerts Management > Smart Detector Alert Rule > Allowed > Custom > Rules

Azure > Alerts Management > Smart Detector Alert Rule > Allowed > Custom

Record and synchronize details for the Azure Alerts Management smart detector alert rule into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is&#92;nresponsible for populating and updating all the attributes for that&#92;nresource type in the Guardrails CMDB.&#92;n&#92;n**Note:** If CMDB is set to Skip for a resource, then it will not be added&#92;nto the CMDB, and no controls that target it will run.&#92;n

Azure > Alerts Management > Smart Detector Alert Rule > CMDB

Discover all Azure Alerts Management smart detector alert rule resources and add them to the CMDB.&#92;n&#92;nThe [Discovery](https://turbot.com/guardrails/docs/concepts/guardrails/discovery) control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control.&#92;n

Azure > Alerts Management > Smart Detector Alert Rule > Regions

Azure > Alerts Management > Smart Detector Alert Rule > Discovery

Take an action when an Azure Alerts Management smart detector alert rule tags is not updated based on the `Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Tags &gt; *` policies.&#92;n&#92;nIf the resource is not updated with the tags defined in `Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Tags &gt; Template`, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

Azure > Alerts Management > Smart Detector Alert Rule > Tags > Template

Azure > Alerts Management > Smart Detector Alert Rule > Tags

alertsManagement

alertsManagementAka

smartDetectorAlertRule

smartDetectorAlertRuleAka

azure-alertsmanagement

A list of Azure regions in which Azure Alerts Management resources are allowed for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n&#92;nThis policy is the default value for all Azure Alerts Management resources&#39; Allowed &gt; Regions policies.&#92;n

Azure > Alerts Management

Azure > Subscription

Azure > Alerts Management > Allowed Regions [Default]

A list of Azure regions in which Azure Alerts Management resources are approved for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n&#92;nThis policy is the default value for all Azure Alerts Management resources&#39; Approved &gt; Regions policies.&#92;n

Azure > Alerts Management > Approved Regions [Default]

The Event Grid event pattern used by the Azure Alerts Management module to specify&#92;nwhich events to forward to the Guardrails Event Handlers [Event Grid].&#92;n&#92;nThis policy automatically generates operation filters based on which&#92;nresource types have CMDB enabled. Only enabled resource types will&#92;nhave their events forwarded to Guardrails.&#92;n

Azure > Turbot > Event Handlers [Event Grid] > Custom Event Patterns

Azure > Turbot > Event Handlers [Event Grid] > Custom Event Patterns > @turbot/azure-alertsmanagement

Azure > Alerts Management > Enabled

Azure > Alerts Management > Permissions > Levels

Configure whether permissions policies are in effect for Azure Alerts Management&#92;nThis setting does not affect Subscription level permissions (Azure/Admin, Azure/Owner, etc)&#92;n

Azure > Alerts Management > Permissions

Azure > Alerts Management > Permissions > Levels > Modifiers

Define the permissions levels that can be used to grant access to Storage an&#92;nAzure Subscription.  Permissions levels defined will appear in the UI to assign&#92;naccess to Guardrails users.&#92;n

A map of Azure API to Guardrails Permission Level used to customize Guardrails&#39;&#92;nstandard permissions. You can add, remove or redefine the mapping of&#92;nAzure API operations to Guardrails permissions levels here.&#92;n&#92;n```&#92;nexample:&#92;n  - &quot;Microsoft.Alerts Management/Alerts Management/delete&quot;: operator&#92;n  - &quot;Microsoft.Alerts Management/Alerts Management/write&quot;: admin&#92;n  - &quot;Microsoft.Alerts Management/Alerts Management/read&quot;: readonly&#92;n```&#92;n

A list of Azure regions in which Azure Alerts Management resources are supported for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n&#92;nThis policy is the default value for all Azure Alerts Management resources&#39; Regions policies.&#92;n

Azure > Alerts Management > Regions

A template used to generate the keys and values for Azure Alerts Management resources.&#92;n&#92;nBy default, all Alerts Management resource Tags &gt; Template policies will use this value.&#92;n

Azure > Alerts Management > Tags Template [Default]

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermissions for Azure Alerts Management that is used as input to the control that manages&#92;nthe IAM stack.&#92;n

Azure > Turbot > Permissions > Compiled > Service Permissions

Azure > Turbot > Permissions > Compiled > Service Permissions > @turbot/azure-alertsmanagement

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermission levels for Azure Alerts Management that is used as input to the&#92;nstack that manages the Guardrails IAM permissions objects.&#92;n

Azure > Turbot > Permissions > Compiled > Levels

Azure > Turbot > Permissions > Compiled > Levels > @turbot/azure-alertsmanagement

Determine the action to take when an Azure Alerts Management smart detector alert rule, based on the `Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Active &gt; *` policies.&#92;n&#92;nThe control determines whether the resource is in active use, and if not,&#92;nhas the ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The age after which the Azure Alerts Management smart detector alert rule&#92;nis no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The number of days since the Azure Alerts Management smart detector alert rule was last modified before it is considered&#92;ninactive.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n

The policy allows you to&#92;ncheck which status determines if the Azure Alerts Management smart detector alert rule is active.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

This policy serves as a hierarchical parent for more specific Allowed policies, such as region-based policies and custom rule-based policies.&#92;n

Determine the action to take when an Azure Alerts Management smart detector alert rule is not allowed based on custom rules.&#92;n&#92;nThe `Allowed &gt; Custom` control checks if the smart detector alert rule is allowed based on the `Allowed &gt; Custom &gt; *` policies. If the smart detector alert rule is not allowed, the control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete if not allowed and resource is new`, the control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n

Determine whether the Azure Alerts Management smart detector alert rule is allowed to exist based on custom rules.&#92;n&#92;nThis policy will be evaluated by the `Allowed &gt; Custom` control. If an Azure Alerts Management smart detector alert rule is not allowed, it will be subject to the action specified in the `Allowed &gt; Custom` policy.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Allowed`, `Not allowed` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Allowed` or `Not allowed`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

string

Configure whether to record and synchronize details for the AZURE Alerts Management smart detector alert rule into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.&#92;nAll policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to **&quot;Enforce: Enabled&quot;**.&#92;n&#92;nIf set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.&#92;n&#92;nTo cleanup resources and stop tracking changes, set this policy to **&quot;Enforce: Disabled&quot;**.&#92;n

A list of AZURE regions in which AZURE Alerts Management smart detector alert rules are supported for use.&#92;n&#92;nAny smart detector alert rules in a region not listed here will not be recorded in CMDB.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n

Determine the action to take when Azure Alerts Management smart detector alert rule tags are not updated based on the `Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Tags &gt; *` policies.&#92;n&#92;nThe control ensures Azure Alerts Management smart detector alert rule tags include tags defined in `Azure &gt; Alerts Management &gt; Smart Detector Alert Rule &gt; Tags &gt; Template`.&#92;n&#92;nTags not defined in Smart Detector Alert Rule Tags Template will not be modified or deleted. Setting a tag value to `undefined` will result in the tag being deleted.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

The template is used to generate the keys and values for Azure Alerts Management smart detector alert rule.&#92;n&#92;nTags not defined in Smart Detector Alert Rule Tags Template will not be modified or deleted. Setting a tag value to `undefined` will result in the tag being deleted.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

The Alerts Management service in Azure provides a centralized view and management experience for all Azure alerts. It enables users to create, manage, and analyze alert rules, including Smart Detector Alert Rules that use machine learning to detect application issues.&#92;n

Azure

Azure Smart Detector Alert Rules use machine learning algorithms to automatically detect application issues. They monitor Application Insights telemetry data and generate smart detection alerts when potential performance problems or failure anomalies are detected.&#92;n

Mod: azure-alertsmanagement

Recommended Version

Resource Types

Controls

IAM Roles

Policies