Update description for notify_by monitor option (#1106)

Co-authored-by: ci.datadog-api-spec <[email protected]>
Co-authored-by: api-clients-generation-pipeline[bot] <54105614+api-clients-generation-pipeline[bot]@users.noreply.github.com>

Author: api-clients-generation-pipeline[bot]

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.4",
-            "regenerated": "2022-10-14 07:43:55.828324",
-            "spec_repo_commit": "13ac1a3a"
+            "regenerated": "2022-10-14 14:06:45.194856",
+            "spec_repo_commit": "7eb6ca7a"
         },
         "v2": {
             "apigentools_version": "1.6.4",
-            "regenerated": "2022-10-14 07:43:55.842327",
-            "spec_repo_commit": "13ac1a3a"
+            "regenerated": "2022-10-14 14:06:45.212757",
+            "spec_repo_commit": "7eb6ca7a"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -6280,18 +6280,20 @@ components:
           type: boolean
         notify_by:
           description: 'Controls what granularity a monitor alerts on. Only available
-            for multi-alerts.
+            for monitors with groupings.
 
-            For instance, a monitor grouped by `cluster`, `namespace`, `pod` can be
-            configured to only notify on each
+            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` have to be a subset of the grouping tags in the query.
+            in `notify_by` must be a subset of the grouping tags in the query.
 
-            For example, a query grouped by `cluster`, `namespace` cannot notify on
-            `region`.'
+            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.'
           items:
             description: A grouping tag.
             type: string

lib/datadog_api_client/v1/models/monitor_options.rb

@@ -94,11 +94,12 @@ class MonitorOptions
     # A Boolean indicating whether tagged users is notified on changes to this monitor.
     attr_accessor :notify_audit
 
-    # Controls what granularity a monitor alerts on. Only available for multi-alerts.
-    # For instance, a monitor grouped by `cluster`, `namespace`, `pod` can be configured to only notify on each
+    # 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` have to be a subset of the grouping tags in the query.
-    # For example, a query grouped by `cluster`, `namespace` cannot notify on `region`.
+    # 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.
     attr_accessor :notify_by
 
     # A Boolean indicating whether this monitor notifies when data stops reporting.