SLO-3271: Update documentation for the transitions returned by SLO history (#2284)

Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>
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.6",
-            "regenerated": "2024-05-14 14:47:45.391704",
-            "spec_repo_commit": "48746015"
+            "regenerated": "2024-05-14 16:40:02.086463",
+            "spec_repo_commit": "45952461"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-05-14 14:47:45.409386",
-            "spec_repo_commit": "48746015"
+            "regenerated": "2024-05-14 16:40:02.105876",
+            "spec_repo_commit": "45952461"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -10661,9 +10661,24 @@ 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 documentatio](https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data)
+
+            for detailed information.'
           example:
           - - 1579212382
             - 0
@@ -10843,9 +10858,26 @@ 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](https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data)
+
+            for detailed information.'
           example:
           - - 1579212382
             - 0

src/main/java/com/datadog/api/client/v1/model/SLOHistoryMonitor.java

@@ -177,9 +177,14 @@ public SLOHistoryMonitor addHistoryItem(List<Double> historyItem) {
   }
 
   /**
-   * For <code>monitor</code> based SLOs, this includes the aggregated history as arrays that
-   * include timeseries and uptime data where <code>0=monitor</code> is in <code>OK</code> state and
-   * <code>1=monitor</code> is in <code>alert</code> state.
+   * 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
+   * <code>0</code> for state means uptime, <code>1</code> means downtime, and <code>2</code> means
+   * no data. Periods of no data are counted either as uptime or downtime depending on monitor
+   * settings. See <a
+   * href="https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data">SLO
+   * documentatio</a> for detailed information.
    *
    * @return history
    */

src/main/java/com/datadog/api/client/v1/model/SLOHistorySLIData.java

@@ -177,9 +177,15 @@ public SLOHistorySLIData addHistoryItem(List<Double> historyItem) {
   }
 
   /**
-   * For <code>monitor</code> based SLOs, this includes the aggregated history as arrays that
-   * include timeseries and uptime data where <code>0=monitor</code> is in <code>OK</code> state and
-   * <code>1=monitor</code> is in <code>alert</code> state.
+   * The state transition history for <code>monitor</code> or <code>time-slice</code> 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 <code>0</code> for state means uptime, <code>1
+   * </code> means downtime, and <code>2</code> 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 <a
+   * href="https://docs.datadoghq.com/service_management/service_level_objectives/monitor/#missing-data">SLO
+   * documentation</a> for detailed information.
    *
    * @return history
    */