feat(monitoring)!: update the API

BREAKING CHANGE: This release has breaking changes.

#### monitoring:v1

The following keys were deleted:
- schemas.DashboardFilter.properties.applyToNewWidgets.description
- schemas.DashboardFilter.properties.applyToNewWidgets.type

The following keys were added:
- schemas.Scorecard.properties.dimensions.description
- schemas.Scorecard.properties.dimensions.items.$ref
- schemas.Scorecard.properties.dimensions.type
- schemas.Scorecard.properties.measures.description
- schemas.Scorecard.properties.measures.items.$ref
- schemas.Scorecard.properties.measures.type

#### monitoring:v3

The following keys were added:
- schemas.Documentation.properties.links.description
- schemas.Documentation.properties.links.items.$ref
- schemas.Documentation.properties.links.type
- schemas.Link.description
- schemas.Link.id
- schemas.Link.properties.displayName.description
- schemas.Link.properties.displayName.type
- schemas.Link.properties.url.description
- schemas.Link.properties.url.type
- schemas.Link.type

The following keys were changed:
- resources.projects.resources.snoozes.methods.patch.parameters.name.description
- schemas.Documentation.properties.content.description
- schemas.Documentation.properties.subject.description
- schemas.PrometheusQueryLanguageCondition.properties.labels.description
- schemas.ServiceLevelObjective.properties.goal.description
- schemas.Snooze.properties.name.description

Author: yoshi-automation

discovery/monitoring-v1.json

@@ -753,7 +753,7 @@
       }
     }
   },
-  "revision": "20240505",
+  "revision": "20240616",
   "rootUrl": "https://monitoring.googleapis.com/",
   "schemas": {
     "Aggregation": {
@@ -1111,10 +1111,6 @@
       "description": "A filter to reduce the amount of data charted in relevant widgets.",
       "id": "DashboardFilter",
       "properties": {
-        "applyToNewWidgets": {
-          "description": "Whether to apply this filter to new widgets by default",
-          "type": "boolean"
-        },
         "filterType": {
           "description": "The specified filter type",
           "enum": [
@@ -2145,10 +2141,24 @@
           "$ref": "Empty",
           "description": "Will cause the Scorecard to show only the value, with no indicator to its value relative to its thresholds."
         },
+        "dimensions": {
+          "description": "Optional. A dimension is a structured label, class, or category for a set of measurements in your data.",
+          "items": {
+            "$ref": "Dimension"
+          },
+          "type": "array"
+        },
         "gaugeView": {
           "$ref": "GaugeView",
           "description": "Will cause the scorecard to show a gauge chart."
         },
+        "measures": {
+          "description": "Optional. A measure is a measured value of a property in your data. For example, rainfall in inches, number of units sold, revenue gained, etc.",
+          "items": {
+            "$ref": "Measure"
+          },
+          "type": "array"
+        },
         "sparkChartView": {
           "$ref": "SparkChartView",
           "description": "Will cause the scorecard to show a spark chart."

discovery/monitoring-v3.json

@@ -1758,7 +1758,7 @@
               ],
               "parameters": {
                 "name": {
-                  "description": "Required. The name of the Snooze. The format is: projects/[PROJECT_ID_OR_NUMBER]/snoozes/[SNOOZE_ID] The ID of the Snooze will be generated by the system.",
+                  "description": "Required. Identifier. The name of the Snooze. The format is: projects/[PROJECT_ID_OR_NUMBER]/snoozes/[SNOOZE_ID] The ID of the Snooze will be generated by the system.",
                   "location": "path",
                   "pattern": "^projects/[^/]+/snoozes/[^/]+$",
                   "required": true,
@@ -2714,7 +2714,7 @@
       }
     }
   },
-  "revision": "20240526",
+  "revision": "20240616",
   "rootUrl": "https://monitoring.googleapis.com/",
   "schemas": {
     "Aggregation": {
@@ -3457,15 +3457,22 @@
       "id": "Documentation",
       "properties": {
         "content": {
-          "description": "The body of the documentation, interpreted according to mime_type. The content may not exceed 8,192 Unicode characters and may not exceed more than 10,240 bytes when encoded in UTF-8 format, whichever is smaller. This text can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables).",
+          "description": "The body of the documentation, interpreted according to mime_type. The content may not exceed 8,192 Unicode characters and may not exceed more than 10,240 bytes when encoded in UTF-8 format, whichever is smaller. This text can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables#doc-vars).",
           "type": "string"
         },
+        "links": {
+          "description": "Optional. Links to content such as playbooks, repositories, and other resources. This field can contain up to 3 entries.",
+          "items": {
+            "$ref": "Link"
+          },
+          "type": "array"
+        },
         "mimeType": {
           "description": "The format of the content field. Presently, only the value \"text/markdown\" is supported. See Markdown (https://en.wikipedia.org/wiki/Markdown) for more information.",
           "type": "string"
         },
         "subject": {
-          "description": "Optional. The subject line of the notification. The subject line may not exceed 10,240 bytes. In notifications generated by this policy, the contents of the subject line after variable expansion will be truncated to 255 bytes or shorter at the latest UTF-8 character boundary. The 255-byte limit is recommended by this thread (https://stackoverflow.com/questions/1592291/what-is-the-email-subject-length-limit). It is both the limit imposed by some third-party ticketing products and it is common to define textual fields in databases as VARCHAR(255).The contents of the subject line can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables). If this field is missing or empty, a default subject line will be generated.",
+          "description": "Optional. The subject line of the notification. The subject line may not exceed 10,240 bytes. In notifications generated by this policy, the contents of the subject line after variable expansion will be truncated to 255 bytes or shorter at the latest UTF-8 character boundary. The 255-byte limit is recommended by this thread (https://stackoverflow.com/questions/1592291/what-is-the-email-subject-length-limit). It is both the limit imposed by some third-party ticketing products and it is common to define textual fields in databases as VARCHAR(255).The contents of the subject line can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables#doc-vars). If this field is missing or empty, a default subject line will be generated.",
           "type": "string"
         }
       },
@@ -4106,6 +4113,21 @@
       },
       "type": "object"
     },
+    "Link": {
+      "description": "Links to content such as playbooks, repositories, and other resources.",
+      "id": "Link",
+      "properties": {
+        "displayName": {
+          "description": "A short display name for the link. The display name must not be empty or exceed 63 characters. Example: \"playbook\".",
+          "type": "string"
+        },
+        "url": {
+          "description": "The url of a webpage. A url can be templatized by using variables in the path or the query parameters. The total length of a URL should not exceed 2083 characters before and after variable expansion. Example: \"https://my_domain.com/playbook?name=${resource.name}\"",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "ListAlertPoliciesResponse": {
       "description": "The protocol for the ListAlertPolicies response.",
       "id": "ListAlertPoliciesResponse",
@@ -5158,7 +5180,7 @@
           "additionalProperties": {
             "type": "string"
           },
-          "description": "Optional. Labels to add to or overwrite in the PromQL query result. Label names must be valid (https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels). Label values can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables). The only available variable names are the names of the labels in the PromQL result, including \"__name__\" and \"value\". \"labels\" may be empty.",
+          "description": "Optional. Labels to add to or overwrite in the PromQL query result. Label names must be valid (https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels). Label values can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables#doc-vars). The only available variable names are the names of the labels in the PromQL result, including \"__name__\" and \"value\". \"labels\" may be empty.",
           "type": "object"
         },
         "query": {
@@ -5459,7 +5481,7 @@
           "type": "string"
         },
         "goal": {
-          "description": "The fraction of service that must be good in order for this objective to be met. 0 < goal <= 0.999.",
+          "description": "The fraction of service that must be good in order for this objective to be met. 0 < goal <= 0.9999.",
           "format": "double",
           "type": "number"
         },
@@ -5503,7 +5525,7 @@
           "description": "Required. The Snooze will be active from interval.start_time through interval.end_time. interval.start_time cannot be in the past. There is a 15 second clock skew to account for the time it takes for a request to reach the API from the UI."
         },
         "name": {
-          "description": "Required. The name of the Snooze. The format is: projects/[PROJECT_ID_OR_NUMBER]/snoozes/[SNOOZE_ID] The ID of the Snooze will be generated by the system.",
+          "description": "Required. Identifier. The name of the Snooze. The format is: projects/[PROJECT_ID_OR_NUMBER]/snoozes/[SNOOZE_ID] The ID of the Snooze will be generated by the system.",
           "type": "string"
         }
       },

src/apis/monitoring/v3.ts

@@ -618,15 +618,19 @@ export namespace monitoring_v3 {
    */
   export interface Schema$Documentation {
     /**
-     * The body of the documentation, interpreted according to mime_type. The content may not exceed 8,192 Unicode characters and may not exceed more than 10,240 bytes when encoded in UTF-8 format, whichever is smaller. This text can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables).
+     * The body of the documentation, interpreted according to mime_type. The content may not exceed 8,192 Unicode characters and may not exceed more than 10,240 bytes when encoded in UTF-8 format, whichever is smaller. This text can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables#doc-vars).
      */
     content?: string | null;
+    /**
+     * Optional. Links to content such as playbooks, repositories, and other resources. This field can contain up to 3 entries.
+     */
+    links?: Schema$Link[];
     /**
      * The format of the content field. Presently, only the value "text/markdown" is supported. See Markdown (https://en.wikipedia.org/wiki/Markdown) for more information.
      */
     mimeType?: string | null;
     /**
-     * Optional. The subject line of the notification. The subject line may not exceed 10,240 bytes. In notifications generated by this policy, the contents of the subject line after variable expansion will be truncated to 255 bytes or shorter at the latest UTF-8 character boundary. The 255-byte limit is recommended by this thread (https://stackoverflow.com/questions/1592291/what-is-the-email-subject-length-limit). It is both the limit imposed by some third-party ticketing products and it is common to define textual fields in databases as VARCHAR(255).The contents of the subject line can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables). If this field is missing or empty, a default subject line will be generated.
+     * Optional. The subject line of the notification. The subject line may not exceed 10,240 bytes. In notifications generated by this policy, the contents of the subject line after variable expansion will be truncated to 255 bytes or shorter at the latest UTF-8 character boundary. The 255-byte limit is recommended by this thread (https://stackoverflow.com/questions/1592291/what-is-the-email-subject-length-limit). It is both the limit imposed by some third-party ticketing products and it is common to define textual fields in databases as VARCHAR(255).The contents of the subject line can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables#doc-vars). If this field is missing or empty, a default subject line will be generated.
      */
     subject?: string | null;
   }
@@ -1068,6 +1072,19 @@ export namespace monitoring_v3 {
      */
     width?: number | null;
   }
+  /**
+   * Links to content such as playbooks, repositories, and other resources.
+   */
+  export interface Schema$Link {
+    /**
+     * A short display name for the link. The display name must not be empty or exceed 63 characters. Example: "playbook".
+     */
+    displayName?: string | null;
+    /**
+     * The url of a webpage. A url can be templatized by using variables in the path or the query parameters. The total length of a URL should not exceed 2083 characters before and after variable expansion. Example: "https://my_domain.com/playbook?name=${resource.name\}"
+     */
+    url?: string | null;
+  }
   /**
    * The protocol for the ListAlertPolicies response.
    */
@@ -1737,7 +1754,7 @@ export namespace monitoring_v3 {
      */
     evaluationInterval?: string | null;
     /**
-     * Optional. Labels to add to or overwrite in the PromQL query result. Label names must be valid (https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels). Label values can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables). The only available variable names are the names of the labels in the PromQL result, including "__name__" and "value". "labels" may be empty.
+     * Optional. Labels to add to or overwrite in the PromQL query result. Label names must be valid (https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels). Label values can be templatized by using variables (https://cloud.google.com/monitoring/alerts/doc-variables#doc-vars). The only available variable names are the names of the labels in the PromQL result, including "__name__" and "value". "labels" may be empty.
      */
     labels?: {[key: string]: string} | null;
     /**
@@ -1947,7 +1964,7 @@ export namespace monitoring_v3 {
      */
     displayName?: string | null;
     /**
-     * The fraction of service that must be good in order for this objective to be met. 0 < goal <= 0.999.
+     * The fraction of service that must be good in order for this objective to be met. 0 < goal <= 0.9999.
      */
     goal?: number | null;
     /**
@@ -1984,7 +2001,7 @@ export namespace monitoring_v3 {
      */
     interval?: Schema$TimeInterval;
     /**
-     * Required. The name of the Snooze. The format is: projects/[PROJECT_ID_OR_NUMBER]/snoozes/[SNOOZE_ID] The ID of the Snooze will be generated by the system.
+     * Required. Identifier. The name of the Snooze. The format is: projects/[PROJECT_ID_OR_NUMBER]/snoozes/[SNOOZE_ID] The ID of the Snooze will be generated by the system.
      */
     name?: string | null;
   }
@@ -6103,7 +6120,7 @@ export namespace monitoring_v3 {
   export interface Params$Resource$Projects$Snoozes$Patch
     extends StandardParameters {
     /**
-     * Required. The name of the Snooze. The format is: projects/[PROJECT_ID_OR_NUMBER]/snoozes/[SNOOZE_ID] The ID of the Snooze will be generated by the system.
+     * Required. Identifier. The name of the Snooze. The format is: projects/[PROJECT_ID_OR_NUMBER]/snoozes/[SNOOZE_ID] The ID of the Snooze will be generated by the system.
      */
     name?: string;
     /**