You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- INTMDB-369: Fix parsing of `delivery_type_config` when using `point_in_time` for `cloud_backup_snapshot_restore_job`, in [\#813](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/813)
8
+
- INTMDB-322: Validated serverless alert_configurations and improved documentation on usage, addressing issue [\#722](https://github.com/mongodb/terraform-provider-mongodbatlas/issues/722) in [\#819](https://github.com/mongodb/terraform-provider-mongodbatlas/pull/819)
Copy file name to clipboardExpand all lines: website/docs/d/alert_configuration.html.markdown
+5-5
Original file line number
Diff line number
Diff line change
@@ -104,7 +104,7 @@ In addition to all arguments above, the following attributes are exported:
104
104
105
105
-> ***IMPORTANT:*** Event Type has many possible values. All current options at available at https://docs.atlas.mongodb.com/reference/api/alert-configurations-create-config/ Details for both conditional and metric based alerts can be found by selecting the tabs on the [alert config page](https://docs.atlas.mongodb.com/reference/api/alert-configurations-create-config/) and checking the latest eventTypeName options.
106
106
107
-
-> **NOTE:** If `event_type` is set to OUTSIDE_METRIC_THRESHOLD, the metricThreshold field must also be set.
107
+
-> **NOTE:** If `event_type` is set to `OUTSIDE_METRIC_THRESHOLD` or `OUTSIDE_SERVERLESS_METRIC_THRESHOLD`, the `metric_threshold_config` field must also be configured.
108
108
109
109
### Matchers
110
110
Rules to apply when matching an object against this alert configuration. Only entities that match all these rules are checked for an alert condition. You can filter using the matchers array only when the eventTypeName specifies an event for a host, replica set, or sharded cluster.
@@ -143,10 +143,10 @@ Rules to apply when matching an object against this alert configuration. Only en
143
143
-`CONFIG`
144
144
-`MONGOS`
145
145
146
-
### Metric Threshold Config
147
-
The threshold that causes an alert to be triggered. Required if `event_type_name` : "OUTSIDE_METRIC_THRESHOLD".
The threshold that causes an alert to be triggered. Required if `event_type_name` : `OUTSIDE_METRIC_THRESHOLD` or `OUTSIDE_SERVERLESS_METRIC_THRESHOLD`.
148
148
149
-
*`metric_name` - Name of the metric to check. The full list of current options is available [here](https://docs.atlas.mongodb.com/reference/alert-host-metrics/#measurement-types)
149
+
*`metric_name` - Name of the metric to check. The full list being quite large, please refer to atlas docs [here for general metrics](https://docs.atlas.mongodb.com/reference/alert-host-metrics/#measurement-types) and [here for serverless metrics](https://www.mongodb.com/docs/atlas/reference/api/alert-configurations-create-config/#serverless-measurements)
150
150
151
151
*`operator` - Operator to apply when checking the current metric value against the threshold value.
152
152
Accepted values are:
@@ -175,7 +175,7 @@ The threshold that causes an alert to be triggered. Required if `event_type_name
175
175
176
176
*`mode` - This must be set to AVERAGE. Atlas computes the current metric value as an average.
177
177
178
-
### Threshold Config
178
+
### Threshold Config (`threshold_config`)
179
179
*`operator` - Operator to apply when checking the current metric value against the threshold value.
-> ***IMPORTANT:*** Event Type has many possible values. All current options at available at https://docs.atlas.mongodb.com/reference/api/alert-configurations-create-config/ Details for both conditional and metric based alerts can be found by selecting the tabs on the [alert config page](https://docs.atlas.mongodb.com/reference/api/alert-configurations-create-config/) and checking the latest eventTypeName options.
129
129
130
-
-> **NOTE:** If `event_type` is set to OUTSIDE_METRIC_THRESHOLD, the metricThreshold field must also be set.
130
+
-> **NOTE:** If `event_type` is set to `OUTSIDE_METRIC_THRESHOLD` or `OUTSIDE_SERVERLESS_METRIC_THRESHOLD`, the `metric_threshold_config` field must also be configured.
131
131
132
132
### Matchers
133
133
Rules to apply when matching an object against this alert configuration. Only entities that match all these rules are checked for an alert condition. You can filter using the matchers array only when the eventTypeName specifies an event for a host, replica set, or sharded cluster.
@@ -167,10 +167,10 @@ Rules to apply when matching an object against this alert configuration. Only en
167
167
-`CONFIG`
168
168
-`MONGOS`
169
169
170
-
### Metric Threshold Config
171
-
The threshold that causes an alert to be triggered. Required if `event_type_name` : "OUTSIDE_METRIC_THRESHOLD".
The threshold that causes an alert to be triggered. Required if `event_type_name` : `OUTSIDE_METRIC_THRESHOLD` or `OUTSIDE_SERVERLESS_METRIC_THRESHOLD`
172
172
173
-
*`metric_name` - Name of the metric to check. The full list of current options is available [here](https://docs.atlas.mongodb.com/reference/alert-host-metrics/#measurement-types)
173
+
*`metric_name` - Name of the metric to check. The full list being quite large, please refer to atlas docs [here for general metrics](https://docs.atlas.mongodb.com/reference/alert-host-metrics/#measurement-types) and [here for serverless metrics](https://www.mongodb.com/docs/atlas/reference/api/alert-configurations-create-config/#serverless-measurements)
174
174
*`operator` - Operator to apply when checking the current metric value against the threshold value.
175
175
Accepted values are:
176
176
-`GREATER_THAN`
@@ -198,7 +198,7 @@ The threshold that causes an alert to be triggered. Required if `event_type_name
198
198
199
199
*`mode` - This must be set to AVERAGE. Atlas computes the current metric value as an average.
200
200
201
-
### Threshold Config
201
+
### Threshold Config (`threshold_config`)
202
202
*`operator` - Operator to apply when checking the current metric value against the threshold value.
`mongodbatlas_cloud_backup_snapshot_restore_job` provides a resource to create a new restore job from a cloud backup snapshot of a specified cluster. The restore job can be one of three types:
11
+
`mongodbatlas_cloud_backup_snapshot_restore_job` provides a resource to create a new restore job from a cloud backup snapshot of a specified cluster. The restore job must define one of three delivery types:
12
12
***automated:** Atlas automatically restores the snapshot with snapshotId to the Atlas cluster with name targetClusterName in the Atlas project with targetGroupId.
13
13
14
14
***download:** Atlas provides a URL to download a .tar.gz of the snapshot with snapshotId. The contents of the archive contain the data files for your Atlas cluster.
@@ -92,17 +92,23 @@ description: |-
92
92
*`project_id` - (Required) The unique identifier of the project for the Atlas cluster whose snapshot you want to restore.
93
93
*`cluster_name` - (Required) The name of the Atlas cluster whose snapshot you want to restore.
94
94
*`snapshot_id` - (Required) Unique identifier of the snapshot to restore.
95
-
*`delivery_type_config` - (Required) Type of restore job to create. Possible values are: **download** or **automated**, only one must be set it in ``true``.
95
+
*`delivery_type_config` - (Required) Type of restore job to create. Possible configurations are: **download**, **automated**, or **pointInTime** only one must be set it in ``true``.
96
+
*`delivery_type_config.automated` - Set to `true` to use the automated configuration.
97
+
*`delivery_type_config.download` - Set to `true` to use the download configuration.
98
+
*`delivery_type_config.pointInTime` - Set to `true` to use the pointInTime configuration.
99
+
*`delivery_type_config.target_cluster_name` - Name of the target Atlas cluster to which the restore job restores the snapshot. Required for **automated** and **pointInTime**.
100
+
*`delivery_type_config.target_project_id` - Name of the target Atlas cluster to which the restore job restores the snapshot. Required for **automated** and **pointInTime**.
101
+
*`delivery_type_config.oplog_ts` - Optional setting for **pointInTime** configuration. Timestamp in the number of seconds that have elapsed since the UNIX epoch from which to you want to restore this snapshot. This is the first part of an Oplog timestamp.
102
+
*`delivery_type_config.oplog_inc` - Optional setting for **pointInTime** configuration. Oplog operation number from which to you want to restore this snapshot. This is the second part of an Oplog timestamp. Used in conjunction with `oplog_ts`.
103
+
*`delivery_type_config.point_in_time_utc_seconds` - Optional setting for **pointInTime** configuration. Timestamp in the number of seconds that have elapsed since the UNIX epoch from which you want to restore this snapshot. Used instead of oplog settings.
96
104
97
105
### Download
98
106
Atlas provides a URL to download a .tar.gz of the snapshot with snapshotId.
99
107
100
108
### Automated
101
-
Atlas automatically restores the snapshot with snapshotId to the Atlas cluster with name targetClusterName in the Atlas project with targetGroupId. if you want to use automated delivery type, you must to set the following arguments:
102
-
103
-
*`target_cluster_name` - (Required) Name of the target Atlas cluster to which the restore job restores the snapshot. Only required if deliveryType is automated.
104
-
*`target_group_id` - (Required) Unique ID of the target Atlas project for the specified targetClusterName. Only required if deliveryType is automated.
109
+
Atlas automatically restores the snapshot with snapshotId to the Atlas cluster with name targetClusterName in the Atlas project with targetProjectId. if you want to use automated delivery type, you must to set the arguments for the afformentioned properties.
105
110
111
+
### Point in time
106
112
107
113
## Attributes Reference
108
114
@@ -119,7 +125,7 @@ In addition to all arguments above, the following attributes are exported:
119
125
*`id` - The Terraform's unique identifier used internally for state management.
120
126
*`links` - One or more links to sub-resources and/or related resources. The relations between URLs are explained in the Web Linking Specification.
121
127
*`snapshot_id` - Unique identifier of the source snapshot ID of the restore job.
122
-
*`target_group_id` - Name of the target Atlas project of the restore job. Only visible if deliveryType is automated.
128
+
*`target_project_id` - Name of the target Atlas project of the restore job. Only visible if deliveryType is automated.
123
129
*`target_cluster_name` - Name of the target Atlas cluster to which the restore job restores the snapshot. Only visible if deliveryType is automated.
124
130
*`timestamp` - Timestamp in ISO 8601 date and time format in UTC when the snapshot associated to snapshotId was taken.
125
131
*`oplogTs` - Timestamp in the number of seconds that have elapsed since the UNIX epoch from which to you want to restore this snapshot.
0 commit comments