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
#### monitoring:v1
The following keys were added:
- schemas.Scorecard.properties.breakdowns (Total Keys: 2)
#### monitoring:v3
The following keys were added:
- schemas.Criteria.properties.filter.type (Total Keys: 1)
Copy file name to clipboardexpand all lines: docs/dyn/monitoring_v3.projects.snoozes.html
+12-6
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,8 @@ <h3>Method Details</h3>
109
109
110
110
{ # A Snooze will prevent any alerts from being opened, and close any that are already open. The Snooze will work on alerts that match the criteria defined in the Snooze. The Snooze will be active from interval.start_time through interval.end_time.
111
111
"criteria": { # Criteria specific to the AlertPolicys that this Snooze applies to. The Snooze will suppress alerts that come from one of the AlertPolicys whose names are supplied. # Required. This defines the criteria for applying the Snooze. See Criteria for more information.
112
-
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation.
112
+
"filter": "A String", # Optional. The filter string to match on Alert fields when silencing the alerts. It follows the standard https://google.aip.dev/160 syntax. A filter string used to apply the snooze to specific incidents that have matching filter values. Filters can be defined for snoozes that apply to one alerting policy. Filters must be a string formatted as one or more resource labels with specific label values. If multiple resource labels are used, then they must be connected with an AND operator. For example, the following filter applies the snooze to incidents that have an instance ID of 1234567890 and a zone of us-central1-a: resource.labels.instance_id="1234567890" AND resource.labels.zone="us-central1-a"
113
+
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation. Exactly 1 alert policy is required if filter is specified at the same time.
113
114
"A String",
114
115
],
115
116
},
@@ -131,7 +132,8 @@ <h3>Method Details</h3>
131
132
132
133
{ # A Snooze will prevent any alerts from being opened, and close any that are already open. The Snooze will work on alerts that match the criteria defined in the Snooze. The Snooze will be active from interval.start_time through interval.end_time.
133
134
"criteria": { # Criteria specific to the AlertPolicys that this Snooze applies to. The Snooze will suppress alerts that come from one of the AlertPolicys whose names are supplied. # Required. This defines the criteria for applying the Snooze. See Criteria for more information.
134
-
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation.
135
+
"filter": "A String", # Optional. The filter string to match on Alert fields when silencing the alerts. It follows the standard https://google.aip.dev/160 syntax. A filter string used to apply the snooze to specific incidents that have matching filter values. Filters can be defined for snoozes that apply to one alerting policy. Filters must be a string formatted as one or more resource labels with specific label values. If multiple resource labels are used, then they must be connected with an AND operator. For example, the following filter applies the snooze to incidents that have an instance ID of 1234567890 and a zone of us-central1-a: resource.labels.instance_id="1234567890" AND resource.labels.zone="us-central1-a"
136
+
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation. Exactly 1 alert policy is required if filter is specified at the same time.
135
137
"A String",
136
138
],
137
139
},
@@ -160,7 +162,8 @@ <h3>Method Details</h3>
160
162
161
163
{ # A Snooze will prevent any alerts from being opened, and close any that are already open. The Snooze will work on alerts that match the criteria defined in the Snooze. The Snooze will be active from interval.start_time through interval.end_time.
162
164
"criteria": { # Criteria specific to the AlertPolicys that this Snooze applies to. The Snooze will suppress alerts that come from one of the AlertPolicys whose names are supplied. # Required. This defines the criteria for applying the Snooze. See Criteria for more information.
163
-
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation.
165
+
"filter": "A String", # Optional. The filter string to match on Alert fields when silencing the alerts. It follows the standard https://google.aip.dev/160 syntax. A filter string used to apply the snooze to specific incidents that have matching filter values. Filters can be defined for snoozes that apply to one alerting policy. Filters must be a string formatted as one or more resource labels with specific label values. If multiple resource labels are used, then they must be connected with an AND operator. For example, the following filter applies the snooze to incidents that have an instance ID of 1234567890 and a zone of us-central1-a: resource.labels.instance_id="1234567890" AND resource.labels.zone="us-central1-a"
166
+
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation. Exactly 1 alert policy is required if filter is specified at the same time.
164
167
"A String",
165
168
],
166
169
},
@@ -195,7 +198,8 @@ <h3>Method Details</h3>
195
198
"snoozes": [ # Snoozes matching this list call.
196
199
{ # A Snooze will prevent any alerts from being opened, and close any that are already open. The Snooze will work on alerts that match the criteria defined in the Snooze. The Snooze will be active from interval.start_time through interval.end_time.
197
200
"criteria": { # Criteria specific to the AlertPolicys that this Snooze applies to. The Snooze will suppress alerts that come from one of the AlertPolicys whose names are supplied. # Required. This defines the criteria for applying the Snooze. See Criteria for more information.
198
-
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation.
201
+
"filter": "A String", # Optional. The filter string to match on Alert fields when silencing the alerts. It follows the standard https://google.aip.dev/160 syntax. A filter string used to apply the snooze to specific incidents that have matching filter values. Filters can be defined for snoozes that apply to one alerting policy. Filters must be a string formatted as one or more resource labels with specific label values. If multiple resource labels are used, then they must be connected with an AND operator. For example, the following filter applies the snooze to incidents that have an instance ID of 1234567890 and a zone of us-central1-a: resource.labels.instance_id="1234567890" AND resource.labels.zone="us-central1-a"
202
+
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation. Exactly 1 alert policy is required if filter is specified at the same time.
199
203
"A String",
200
204
],
201
205
},
@@ -235,7 +239,8 @@ <h3>Method Details</h3>
235
239
236
240
{ # A Snooze will prevent any alerts from being opened, and close any that are already open. The Snooze will work on alerts that match the criteria defined in the Snooze. The Snooze will be active from interval.start_time through interval.end_time.
237
241
"criteria": { # Criteria specific to the AlertPolicys that this Snooze applies to. The Snooze will suppress alerts that come from one of the AlertPolicys whose names are supplied. # Required. This defines the criteria for applying the Snooze. See Criteria for more information.
238
-
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation.
242
+
"filter": "A String", # Optional. The filter string to match on Alert fields when silencing the alerts. It follows the standard https://google.aip.dev/160 syntax. A filter string used to apply the snooze to specific incidents that have matching filter values. Filters can be defined for snoozes that apply to one alerting policy. Filters must be a string formatted as one or more resource labels with specific label values. If multiple resource labels are used, then they must be connected with an AND operator. For example, the following filter applies the snooze to incidents that have an instance ID of 1234567890 and a zone of us-central1-a: resource.labels.instance_id="1234567890" AND resource.labels.zone="us-central1-a"
243
+
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation. Exactly 1 alert policy is required if filter is specified at the same time.
239
244
"A String",
240
245
],
241
246
},
@@ -258,7 +263,8 @@ <h3>Method Details</h3>
258
263
259
264
{ # A Snooze will prevent any alerts from being opened, and close any that are already open. The Snooze will work on alerts that match the criteria defined in the Snooze. The Snooze will be active from interval.start_time through interval.end_time.
260
265
"criteria": { # Criteria specific to the AlertPolicys that this Snooze applies to. The Snooze will suppress alerts that come from one of the AlertPolicys whose names are supplied. # Required. This defines the criteria for applying the Snooze. See Criteria for more information.
261
-
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation.
266
+
"filter": "A String", # Optional. The filter string to match on Alert fields when silencing the alerts. It follows the standard https://google.aip.dev/160 syntax. A filter string used to apply the snooze to specific incidents that have matching filter values. Filters can be defined for snoozes that apply to one alerting policy. Filters must be a string formatted as one or more resource labels with specific label values. If multiple resource labels are used, then they must be connected with an AND operator. For example, the following filter applies the snooze to incidents that have an instance ID of 1234567890 and a zone of us-central1-a: resource.labels.instance_id="1234567890" AND resource.labels.zone="us-central1-a"
267
+
"policies": [ # The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation. Exactly 1 alert policy is required if filter is specified at the same time.
Copy file name to clipboardexpand all lines: googleapiclient/discovery_cache/documents/monitoring.v1.json
+8-1
Original file line number
Diff line number
Diff line change
@@ -753,7 +753,7 @@
753
753
}
754
754
}
755
755
},
756
-
"revision": "20241212",
756
+
"revision": "20250125",
757
757
"rootUrl": "https://monitoring.googleapis.com/",
758
758
"schemas": {
759
759
"Aggregation": {
@@ -2236,6 +2236,13 @@
2236
2236
"$ref": "Empty",
2237
2237
"description": "Will cause the Scorecard to show only the value, with no indicator to its value relative to its thresholds."
2238
2238
},
2239
+
"breakdowns": {
2240
+
"description": "Optional. The collection of breakdowns to be applied to the dataset. A breakdown is a way to slice the data. For example, you can break down the data by region.",
2241
+
"items": {
2242
+
"$ref": "Breakdown"
2243
+
},
2244
+
"type": "array"
2245
+
},
2239
2246
"dimensions": {
2240
2247
"description": "Optional. A dimension is a structured label, class, or category for a set of measurements in your data.",
Copy file name to clipboardexpand all lines: googleapiclient/discovery_cache/documents/monitoring.v3.json
+6-2
Original file line number
Diff line number
Diff line change
@@ -2720,7 +2720,7 @@
2720
2720
}
2721
2721
}
2722
2722
},
2723
-
"revision": "20250111",
2723
+
"revision": "20250125",
2724
2724
"rootUrl": "https://monitoring.googleapis.com/",
2725
2725
"schemas": {
2726
2726
"Aggregation": {
@@ -3414,8 +3414,12 @@
3414
3414
"description": "Criteria specific to the AlertPolicys that this Snooze applies to. The Snooze will suppress alerts that come from one of the AlertPolicys whose names are supplied.",
3415
3415
"id": "Criteria",
3416
3416
"properties": {
3417
+
"filter": {
3418
+
"description": "Optional. The filter string to match on Alert fields when silencing the alerts. It follows the standard https://google.aip.dev/160 syntax. A filter string used to apply the snooze to specific incidents that have matching filter values. Filters can be defined for snoozes that apply to one alerting policy. Filters must be a string formatted as one or more resource labels with specific label values. If multiple resource labels are used, then they must be connected with an AND operator. For example, the following filter applies the snooze to incidents that have an instance ID of 1234567890 and a zone of us-central1-a: resource.labels.instance_id=\"1234567890\" AND resource.labels.zone=\"us-central1-a\"",
3419
+
"type": "string"
3420
+
},
3417
3421
"policies": {
3418
-
"description": "The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation.",
3422
+
"description": "The specific AlertPolicy names for the alert that should be snoozed. The format is: projects/[PROJECT_ID_OR_NUMBER]/alertPolicies/[POLICY_ID] There is a limit of 16 policies per snooze. This limit is checked during snooze creation. Exactly 1 alert policy is required if filter is specified at the same time.",
0 commit comments