Update API docs for Error Tracking monitors (#366)

Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-11-05 22:28:16.921323",
-            "spec_repo_commit": "2db17c21"
+            "regenerated": "2024-11-06 20:54:46.694370",
+            "spec_repo_commit": "0f558cbc"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-11-05 22:28:16.941353",
-            "spec_repo_commit": "2db17c21"
+            "regenerated": "2024-11-06 20:54:46.713356",
+            "spec_repo_commit": "0f558cbc"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -28985,21 +28985,27 @@ paths:
         ##### Error Tracking Alert Query
 
 
-        Example(RUM): `error-tracking-rum(query).rollup(rollup_method[, measure]).last(time_window)
-        operator #`
+        "New issue" example: `error-tracking(query).source(issue_source).new().rollup(rollup_method[,
+        measure]).by(group_by).last(time_window) operator #`
 
-        Example(APM Traces): `error-tracking-traces(query).rollup(rollup_method[,
-        measure]).last(time_window) operator #`
+        "High impact issue" example: `error-tracking(query).source(issue_source).impact().rollup(rollup_method[,
+        measure]).by(group_by).last(time_window) operator #`
 
 
         - `query` The search query - following the [Log search syntax](https://docs.datadoghq.com/logs/search_syntax/).
 
+        - `issue_source` The issue source - supports `all`, `browser`, `mobile` and
+        `backend` and defaults to `all` if omitted.
+
         - `rollup_method` The stats roll-up method - supports `count`, `avg`, and
-        `cardinality`.
+        `cardinality` and defaults to `count` if omitted.
 
         - `measure` For `avg` and cardinality `rollup_method` - specify the measure
         or the facet name you want to use.
 
+        - `group by` Comma-separated list of attributes to group by - should contain
+        at least `issue.id`.
+
         - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
 
         - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.

src/datadogV1/api/api_monitors.rs

@@ -669,12 +669,14 @@ impl MonitorsAPI {
     ///
     /// ##### Error Tracking Alert Query
     ///
-    /// Example(RUM): `error-tracking-rum(query).rollup(rollup_method[, measure]).last(time_window) operator #`
-    /// Example(APM Traces): `error-tracking-traces(query).rollup(rollup_method[, measure]).last(time_window) operator #`
+    /// "New issue" example: `error-tracking(query).source(issue_source).new().rollup(rollup_method[, measure]).by(group_by).last(time_window) operator #`
+    /// "High impact issue" example: `error-tracking(query).source(issue_source).impact().rollup(rollup_method[, measure]).by(group_by).last(time_window) operator #`
     ///
     /// - `query` The search query - following the [Log search syntax](<https://docs.datadoghq.com/logs/search_syntax/>).
-    /// - `rollup_method` The stats roll-up method - supports `count`, `avg`, and `cardinality`.
+    /// - `issue_source` The issue source - supports `all`, `browser`, `mobile` and `backend` and defaults to `all` if omitted.
+    /// - `rollup_method` The stats roll-up method - supports `count`, `avg`, and `cardinality` and defaults to `count` if omitted.
     /// - `measure` For `avg` and cardinality `rollup_method` - specify the measure or the facet name you want to use.
+    /// - `group by` Comma-separated list of attributes to group by - should contain at least `issue.id`.
     /// - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
     /// - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
     /// - `#` an integer or decimal number used to set the threshold.
@@ -879,12 +881,14 @@ impl MonitorsAPI {
     ///
     /// ##### Error Tracking Alert Query
     ///
-    /// Example(RUM): `error-tracking-rum(query).rollup(rollup_method[, measure]).last(time_window) operator #`
-    /// Example(APM Traces): `error-tracking-traces(query).rollup(rollup_method[, measure]).last(time_window) operator #`
+    /// "New issue" example: `error-tracking(query).source(issue_source).new().rollup(rollup_method[, measure]).by(group_by).last(time_window) operator #`
+    /// "High impact issue" example: `error-tracking(query).source(issue_source).impact().rollup(rollup_method[, measure]).by(group_by).last(time_window) operator #`
     ///
     /// - `query` The search query - following the [Log search syntax](<https://docs.datadoghq.com/logs/search_syntax/>).
-    /// - `rollup_method` The stats roll-up method - supports `count`, `avg`, and `cardinality`.
+    /// - `issue_source` The issue source - supports `all`, `browser`, `mobile` and `backend` and defaults to `all` if omitted.
+    /// - `rollup_method` The stats roll-up method - supports `count`, `avg`, and `cardinality` and defaults to `count` if omitted.
     /// - `measure` For `avg` and cardinality `rollup_method` - specify the measure or the facet name you want to use.
+    /// - `group by` Comma-separated list of attributes to group by - should contain at least `issue.id`.
     /// - `time_window` #m (between 1 and 2880), #h (between 1 and 48).
     /// - `operator` `<`, `<=`, `>`, `>=`, `==`, or `!=`.
     /// - `#` an integer or decimal number used to set the threshold.