MonitorScheduledQueryRulesAlertV2 is the Schema for the MonitorScheduledQueryRulesAlertV2s API. Manages an AlertingAction Scheduled Query Rules Version 2 resource within Azure Monitor
Type
CRD
Group
insights.azure.upbound.io
Version
apiVersion: insights.azure.upbound.io/v1beta1
kind: MonitorScheduledQueryRulesAlertV2
MonitorScheduledQueryRulesAlertV2Spec defines the desired state of MonitorScheduledQueryRulesAlertV2
No description provided.
An action block as defined below.
List of Action Group resource IDs to invoke when the alert fires.
A criteria block as defined below.
A failing_periods block as defined below.
An identity block as defined below.
A list of User Assigned Managed Identity IDs to be assigned to this Scheduled Query Rule.
Reference to a ResourceGroup in azure to populate resourceGroupName.
Policies for referencing.
Selector for a ResourceGroup in azure to populate resourceGroupName.
Policies for selection.
Specifies the list of resource IDs that this scheduled query rule is scoped to. Changing this forces a new resource to be created. Currently, the API supports exactly 1 resource ID in the scopes list.
References to ApplicationInsights in insights to populate scopes.
Policies for referencing.
Selector for a list of ApplicationInsights in insights to populate scopes.
Policies for selection.
List of resource type of the target resource(s) on which the alert is created/updated. For example if the scope is a resource group and targetResourceTypes is Microsoft.Compute/virtualMachines, then a different alert will be fired for each virtual machine in the resource group which meet the alert criteria.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
An action block as defined below.
List of Action Group resource IDs to invoke when the alert fires.
A criteria block as defined below.
A failing_periods block as defined below.
An identity block as defined below.
A list of User Assigned Managed Identity IDs to be assigned to this Scheduled Query Rule.
Specifies the list of resource IDs that this scheduled query rule is scoped to. Changing this forces a new resource to be created. Currently, the API supports exactly 1 resource ID in the scopes list.
References to ApplicationInsights in insights to populate scopes.
Policies for referencing.
Selector for a list of ApplicationInsights in insights to populate scopes.
Policies for selection.
List of resource type of the target resource(s) on which the alert is created/updated. For example if the scope is a resource group and targetResourceTypes is Microsoft.Compute/virtualMachines, then a different alert will be fired for each virtual machine in the resource group which meet the alert criteria.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
MonitorScheduledQueryRulesAlertV2Status defines the observed state of MonitorScheduledQueryRulesAlertV2.
No description provided.
An action block as defined below.
List of Action Group resource IDs to invoke when the alert fires.
A criteria block as defined below.
A failing_periods block as defined below.
An identity block as defined below.
A list of User Assigned Managed Identity IDs to be assigned to this Scheduled Query Rule.
Specifies the list of resource IDs that this scheduled query rule is scoped to. Changing this forces a new resource to be created. Currently, the API supports exactly 1 resource ID in the scopes list.
List of resource type of the target resource(s) on which the alert is created/updated. For example if the scope is a resource group and targetResourceTypes is Microsoft.Compute/virtualMachines, then a different alert will be fired for each virtual machine in the resource group which meet the alert criteria.
Conditions of the resource.
msqraexample
apiVersion: insights.azure.upbound.io/v1beta1
kind: MonitorScheduledQueryRulesAlertV2
metadata:
annotations:
meta.upbound.io/example-id: insights/v1beta1/monitorscheduledqueryrulesalertv2
labels:
testing.upbound.io/example-name: example
name: msqraexample
spec:
forProvider:
autoMitigationEnabled: true
criteria:
- dimension:
- name: client_CountryOrRegion
operator: Exclude
values:
- "123"
failingPeriods:
- minimumFailingPeriodsToTriggerAlert: 1
numberOfEvaluationPeriods: 1
metricMeasureColumn: CountByCountry
operator: LessThan
query: |
requests
| summarize CountByCountry=count() by client_CountryOrRegion
resourceIdColumn: client_CountryOrRegion
threshold: 17.5
timeAggregationMethod: Maximum
description: example sqr
displayName: example-sqr
enabled: true
evaluationFrequency: PT10M
location: West Europe
queryTimeRangeOverride: PT1H
resourceGroupNameSelector:
matchLabels:
testing.upbound.io/example-name: example
scopesRefs:
- name: msqraexample
severity: 4
skipQueryValidation: true
tags:
key: value
key2: value2
windowDuration: PT10M
workspaceAlertsStorageEnabled: false