Control types for @turbot/azure-monitor
- Azure > Monitor > Action Group > Active
- Azure > Monitor > Action Group > Approved
- Azure > Monitor > Action Group > CMDB
- Azure > Monitor > Action Group > Configured
- Azure > Monitor > Action Group > Discovery
- Azure > Monitor > Alerts > Active
- Azure > Monitor > Alerts > Approved
- Azure > Monitor > Alerts > CMDB
- Azure > Monitor > Alerts > Configured
- Azure > Monitor > Alerts > Discovery
- Azure > Monitor > Log Profile > Active
- Azure > Monitor > Log Profile > Approved
- Azure > Monitor > Log Profile > CMDB
- Azure > Monitor > Log Profile > Discovery
- Azure > Monitor > Stack
Azure > Monitor > Action Group > Active
Take an action when an Azure Monitor action group is not active based on theAzure > Monitor > Action Group > Active > * policies
.
The Active control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated compliance
environment, it's common to end up with a wide range of alarms that are difficult
and time consuming to clear. The Active control brings automated, well-defined
control to this process.
The Active control checks the status of all defined Active policies for the
resource (Azure > Monitor > Action Group > Active > *
),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note: In contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.
See Active for more information.
tmod:@turbot/azure-monitor#/control/types/actionGroupActive
Azure > Monitor > Action Group > Approved
Take an action when an Azure Monitor action group is not approved based on Azure > Monitor > Action Group > Approved > * policies
.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
For any enforcement actions that specify if new
, e.g., Enforce: Delete unapproved if new
, this control will only take the enforcement actions for resources created within the last 60 minutes.
See Approved for more information.
tmod:@turbot/azure-monitor#/control/types/actionGroupApproved
Azure > Monitor > Action Group > CMDB
Record and synchronize details for the Azure Monitor action group into the CMDB.
The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.
tmod:@turbot/azure-monitor#/control/types/actionGroupCmdb
Azure > Monitor > Action Group > Configured
Maintain Azure > Monitor > Action Group configuration.
Note: If the resource is managed by another stack, then the Skip/Check/Enforce values here are ignored
and inherit from the stack that owns it.
tmod:@turbot/azure-monitor#/control/types/actionGroupConfigured
Azure > Monitor > Action Group > Discovery
Discover all Azure Monitor action group resources and add them to the CMDB.
The 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 control.
tmod:@turbot/azure-monitor#/control/types/actionGroupDiscovery
Azure > Monitor > Alerts > Active
Take an action when an Azure Monitor alerts is not active based on theAzure > Monitor > Alerts > Active > * policies
.
The Active control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated compliance
environment, it's common to end up with a wide range of alarms that are difficult
and time consuming to clear. The Active control brings automated, well-defined
control to this process.
The Active control checks the status of all defined Active policies for the
resource (Azure > Monitor > Alerts > Active > *
),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note: In contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.
See Active for more information.
tmod:@turbot/azure-monitor#/control/types/alertsActive
Azure > Monitor > Alerts > Approved
Take an action when an Azure Monitor alerts is not approved based on Azure > Monitor > Alerts > Approved > * policies
.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
For any enforcement actions that specify if new
, e.g., Enforce: Delete unapproved if new
, this control will only take the enforcement actions for resources created within the last 60 minutes.
See Approved for more information.
tmod:@turbot/azure-monitor#/control/types/alertsApproved
Azure > Monitor > Alerts > CMDB
Record and synchronize details for the Azure Monitor alerts into the CMDB.
The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.
tmod:@turbot/azure-monitor#/control/types/alertsCmdb
Azure > Monitor > Alerts > Configured
Maintain monitor alerts configuration
tmod:@turbot/azure-monitor#/control/types/alertsConfigured
Azure > Monitor > Alerts > Discovery
Discover all Azure Monitor alerts resources and add them to the CMDB.
The 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 control.
tmod:@turbot/azure-monitor#/control/types/alertsDiscovery
Azure > Monitor > Log Profile > Active
Take an action when an Azure Monitor log profile is not active based on theAzure > Monitor > Log Profile > Active > * policies
.
The Active control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated compliance
environment, it's common to end up with a wide range of alarms that are difficult
and time consuming to clear. The Active control brings automated, well-defined
control to this process.
The Active control checks the status of all defined Active policies for the
resource (Azure > Monitor > Log Profile > Active > *
),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note: In contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.
See Active for more information.
tmod:@turbot/azure-monitor#/control/types/logProfileActive
Azure > Monitor > Log Profile > Approved
Take an action when an Azure Monitor log profile is not approved based on Azure > Monitor > Log Profile > Approved > * policies
.
The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.
For any enforcement actions that specify if new
, e.g., Enforce: Delete unapproved if new
, this control will only take the enforcement actions for resources created within the last 60 minutes.
See Approved for more information.
tmod:@turbot/azure-monitor#/control/types/logProfileApproved
Azure > Monitor > Log Profile > CMDB
Record and synchronize details for the Azure Monitor log profile into the CMDB.
The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.
Note: If CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.
tmod:@turbot/azure-monitor#/control/types/logProfileCmdb
Azure > Monitor > Log Profile > Discovery
Discover all Azure Monitor log profile resources and add them to the CMDB.
The 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 control.
tmod:@turbot/azure-monitor#/control/types/logProfileDiscovery
Azure > Monitor > Stack
Configure a custom stack on Azure, per the custom Stack > Source
.
A Guardrails Stack
is a set of resources configured by Guardrails, as specified
via Terraform source. Stacks are responsible for the creation and deletion
of multiple resources. Once created, stack resources are responsible for
configuring themselves from the stack source via their Configured
control.
tmod:@turbot/azure-monitor#/control/types/monitorStack