Monitor is the Schema for the Monitors API. Provides a Datadog monitor resource. This can be used to create and manage Datadog monitors.
Type
CRD
Group
datadog.upbound.io
Version
v1alpha1
apiVersion: datadog.upbound.io/v1alpha1
kind: Monitor
MonitorSpec defines the desired state of Monitor
No description provided.
(Block List, Max: 1) A mapping containing recovery_window and trigger_window values, e.g. last_15m . Can only be used for, and are required for, anomaly monitors. (see below for nested schema) A mapping containing recovery_window and trigger_window values, e.g. last_15m . Can only be used for, and are required for, anomaly monitors.
(Block List, Max: 1) Alert thresholds of the monitor. (see below for nested schema) Alert thresholds of the monitor.
alert. Controls what granularity a monitor alerts on. Only available for monitors with groupings. For instance, a monitor grouped by cluster, namespace, and pod can be configured to only notify on each new cluster violating the alert conditions by setting notify_by to ['cluster']. Tags mentioned in notify_by must be a subset of the grouping tags in the query. For example, a query grouped by cluster and namespace cannot notify on region. Setting notify_by to [*] configures the monitor to notify as a simple-alert.
notification messages should be sent. Valid values are alert, warn, no data. The types of statuses for which re-notification messages should be sent. Valid values are alert, warn, no data.
(Set of String) A list of unique role identifiers to define which roles are allowed to edit the monitor. Editing a monitor includes any updates to the monitor configuration, monitor deletion, and muting of the monitor for any amount of time. Roles unique identifiers can be pulled from the Roles API in the data.id field. A list of unique role identifiers to define which roles are allowed to edit the monitor. Editing a monitor includes any updates to the monitor configuration, monitor deletion, and muting of the monitor for any amount of time. Roles unique identifiers can be pulled from the Roles API in the data.id field.
(Block List) Configuration options for scheduling. (see below for nested schema) Configuration options for scheduling.
(Block List) Configuration options for the custom schedules. If start is omitted, the monitor creation time will be used. (see below for nested schema) Configuration options for the custom schedules. If start is omitted, the monitor creation time will be used.
(Block List) Configuration options for the evaluation window. If hour_starts is set, no other fields may be set. Otherwise, day_starts and month_starts must be set together. (see below for nested schema) Configuration options for the evaluation window. If hour_starts is set, no other fields may be set. Otherwise, day_starts and month_starts must be set together.
(Set of String) A list of tags to associate with your monitor. This can help you categorize and filter monitors in the manage monitors page of the UI. Note: it's not currently possible to filter by these tags when querying via the API A list of tags to associate with your monitor. This can help you categorize and filter monitors in the manage monitors page of the UI. Note: it's not currently possible to filter by these tags when querying via the API
(Block List, Max: 1) (see below for nested schema)
(Block List) A timeseries formula and functions events query. (see below for nested schema) A timeseries formula and functions events query.
(Block List, Min: 1) The compute options. (see below for nested schema) The compute options.
(List of String) An array of index names to query in the stream. An array of index names to query in the stream.
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.
(Block List, Max: 1) A mapping containing recovery_window and trigger_window values, e.g. last_15m . Can only be used for, and are required for, anomaly monitors. (see below for nested schema) A mapping containing recovery_window and trigger_window values, e.g. last_15m . Can only be used for, and are required for, anomaly monitors.
(Block List, Max: 1) Alert thresholds of the monitor. (see below for nested schema) Alert thresholds of the monitor.
alert. Controls what granularity a monitor alerts on. Only available for monitors with groupings. For instance, a monitor grouped by cluster, namespace, and pod can be configured to only notify on each new cluster violating the alert conditions by setting notify_by to ['cluster']. Tags mentioned in notify_by must be a subset of the grouping tags in the query. For example, a query grouped by cluster and namespace cannot notify on region. Setting notify_by to [*] configures the monitor to notify as a simple-alert.
notification messages should be sent. Valid values are alert, warn, no data. The types of statuses for which re-notification messages should be sent. Valid values are alert, warn, no data.
(Set of String) A list of unique role identifiers to define which roles are allowed to edit the monitor. Editing a monitor includes any updates to the monitor configuration, monitor deletion, and muting of the monitor for any amount of time. Roles unique identifiers can be pulled from the Roles API in the data.id field. A list of unique role identifiers to define which roles are allowed to edit the monitor. Editing a monitor includes any updates to the monitor configuration, monitor deletion, and muting of the monitor for any amount of time. Roles unique identifiers can be pulled from the Roles API in the data.id field.
(Block List) Configuration options for scheduling. (see below for nested schema) Configuration options for scheduling.
(Block List) Configuration options for the custom schedules. If start is omitted, the monitor creation time will be used. (see below for nested schema) Configuration options for the custom schedules. If start is omitted, the monitor creation time will be used.
(Block List) Configuration options for the evaluation window. If hour_starts is set, no other fields may be set. Otherwise, day_starts and month_starts must be set together. (see below for nested schema) Configuration options for the evaluation window. If hour_starts is set, no other fields may be set. Otherwise, day_starts and month_starts must be set together.
(Set of String) A list of tags to associate with your monitor. This can help you categorize and filter monitors in the manage monitors page of the UI. Note: it's not currently possible to filter by these tags when querying via the API A list of tags to associate with your monitor. This can help you categorize and filter monitors in the manage monitors page of the UI. Note: it's not currently possible to filter by these tags when querying via the API
(Block List, Max: 1) (see below for nested schema)
(Block List) A timeseries formula and functions events query. (see below for nested schema) A timeseries formula and functions events query.
(Block List, Min: 1) The compute options. (see below for nested schema) The compute options.
(List of String) An array of index names to query in the stream. An array of index names to query in the stream.
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.
MonitorStatus defines the observed state of Monitor.
No description provided.
(Block List, Max: 1) A mapping containing recovery_window and trigger_window values, e.g. last_15m . Can only be used for, and are required for, anomaly monitors. (see below for nested schema) A mapping containing recovery_window and trigger_window values, e.g. last_15m . Can only be used for, and are required for, anomaly monitors.
(Block List, Max: 1) Alert thresholds of the monitor. (see below for nested schema) Alert thresholds of the monitor.
alert. Controls what granularity a monitor alerts on. Only available for monitors with groupings. For instance, a monitor grouped by cluster, namespace, and pod can be configured to only notify on each new cluster violating the alert conditions by setting notify_by to ['cluster']. Tags mentioned in notify_by must be a subset of the grouping tags in the query. For example, a query grouped by cluster and namespace cannot notify on region. Setting notify_by to [*] configures the monitor to notify as a simple-alert.
notification messages should be sent. Valid values are alert, warn, no data. The types of statuses for which re-notification messages should be sent. Valid values are alert, warn, no data.
(Set of String) A list of unique role identifiers to define which roles are allowed to edit the monitor. Editing a monitor includes any updates to the monitor configuration, monitor deletion, and muting of the monitor for any amount of time. Roles unique identifiers can be pulled from the Roles API in the data.id field. A list of unique role identifiers to define which roles are allowed to edit the monitor. Editing a monitor includes any updates to the monitor configuration, monitor deletion, and muting of the monitor for any amount of time. Roles unique identifiers can be pulled from the Roles API in the data.id field.
(Block List) Configuration options for scheduling. (see below for nested schema) Configuration options for scheduling.
(Block List) Configuration options for the custom schedules. If start is omitted, the monitor creation time will be used. (see below for nested schema) Configuration options for the custom schedules. If start is omitted, the monitor creation time will be used.
(Block List) Configuration options for the evaluation window. If hour_starts is set, no other fields may be set. Otherwise, day_starts and month_starts must be set together. (see below for nested schema) Configuration options for the evaluation window. If hour_starts is set, no other fields may be set. Otherwise, day_starts and month_starts must be set together.
(Set of String) A list of tags to associate with your monitor. This can help you categorize and filter monitors in the manage monitors page of the UI. Note: it's not currently possible to filter by these tags when querying via the API A list of tags to associate with your monitor. This can help you categorize and filter monitors in the manage monitors page of the UI. Note: it's not currently possible to filter by these tags when querying via the API
(Block List, Max: 1) (see below for nested schema)
(Block List) A timeseries formula and functions events query. (see below for nested schema) A timeseries formula and functions events query.
(Block List, Min: 1) The compute options. (see below for nested schema) The compute options.
(List of String) An array of index names to query in the stream. An array of index names to query in the stream.
Conditions of the resource.
foo
apiVersion: datadog.upbound.io/v1alpha1
kind: Monitor
metadata:
annotations:
meta.upbound.io/example-id: monitor/v1alpha1/monitor
labels:
testing.upbound.io/example-name: foo
name: foo
spec:
forProvider:
escalationMessage: Escalation message @pagerduty
includeTags: true
message: "Monitor triggered. Notify: @hipchat-channel"
monitorThresholds:
- critical: "4"
warning: "2"
name: Name for monitor foo
query: avg(last_1h):avg:aws.ec2.cpu{environment:foo,host:foo} by {host} > 4
tags:
- foo:bar
- team:fooBar
type: metric alert