Regenerate client from commit f77b7d9c of spec repo

DataDog · May 14, 2024 · 301c0a5 · 301c0a5
1 parent e84d8b2
commit 301c0a5
Show file tree

Hide file tree

Showing 5 changed files with 60 additions and 33 deletions.
diff --git a/.apigentools-info b/.apigentools-info
@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-05-10 16:41:07.106081",
-            "spec_repo_commit": "d6c22916"
+            "regenerated": "2024-05-14 14:48:58.885128",
+            "spec_repo_commit": "f77b7d9c"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-05-10 16:41:14.900488",
-            "spec_repo_commit": "d6c22916"
+            "regenerated": "2024-05-14 14:49:07.024905",
+            "spec_repo_commit": "f77b7d9c"
         }
     }
 }
diff --git a/content/en/api/v1/service-level-objectives/examples.json b/content/en/api/v1/service-level-objectives/examples.json
diff --git a/data/api/v1/full_spec.yaml b/data/api/v1/full_spec.yaml
@@ -10760,9 +10760,22 @@ components:
           example: name
           type: string
         history:
-          description: For `monitor` based SLOs, this includes the aggregated history
-            as arrays that include timeseries and uptime data where `0=monitor` is
-            in `OK` state and `1=monitor` is in `alert` state.
+          description: 'The state transition history for the monitor. It is represented
+            as
+
+            an array of pairs. Each pair is an array containing the timestamp of the
+            transition
+
+            as an integer in Unix epoch format in the first element, and the state
+            as an integer in the
+
+            second element. An integer value of `0` for state means uptime, `1` means
+            downtime, and `2` means no data.
+
+            Periods of no data are counted either as uptime or downtime depending
+            on monitor settings.
+
+            See SLO documentation for detailed information.'
           example:
           - - 1579212382
             - 0
@@ -10942,9 +10955,23 @@ components:
           example: name
           type: string
         history:
-          description: For `monitor` based SLOs, this includes the aggregated history
-            as arrays that include timeseries and uptime data where `0=monitor` is
-            in `OK` state and `1=monitor` is in `alert` state.
+          description: 'The state transition history for `monitor` or `time-slice`
+            SLOs. It is represented as
+
+            an array of pairs. Each pair is an array containing the timestamp of the
+            transition
+
+            as an integer in Unix epoch format in the first element, and the state
+            as an integer in the
+
+            second element. An integer value of `0` for state means uptime, `1` means
+            downtime, and `2` means no data.
+
+            Periods of no data count as uptime in time-slice SLOs, while for monitor
+            SLOs, no data is counted
+
+            either as uptime or downtime depending on monitor settings. See SLO documentation
+            for detailed information.'
           example:
           - - 1579212382
             - 0