docs/v1/SLOHistoryMonitor.md in datadog_api_client-1.4.0 vs docs/v1/SLOHistoryMonitor.md in datadog_api_client-1.5.0
- old
+ new
@@ -1,23 +1,23 @@
# DatadogAPIClient::V1::SLOHistoryMonitor
## Properties
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **error_budget_remaining** | **Hash<String, Float>** | A mapping of threshold `timeframe` to the remaining error budget. | [optional] |
-| **errors** | [**Array<SLOHistoryResponseErrorWithType>**](SLOHistoryResponseErrorWithType.md) | An array of error objects returned while querying the history data for the service level objective. | [optional] |
-| **group** | **String** | For groups in a grouped SLO, this is the group name. | [optional] |
-| **history** | **Array<Array<Float>>** | For `monitor` based SLOs, this includes the aggregated history as arrays that include time series and uptime data where `0=monitor` is in `OK` state and `1=monitor` is in `alert` state. | [optional] |
-| **monitor_modified** | **Integer** | For `monitor` based SLOs, this is the last modified timestamp in epoch seconds of the monitor. | [optional] |
-| **monitor_type** | **String** | For `monitor` based SLOs, this describes the type of monitor. | [optional] |
-| **name** | **String** | For groups in a grouped SLO, this is the group name. For monitors in a multi-monitor SLO, this is the monitor name. | [optional] |
-| **precision** | **Float** | The amount of decimal places the SLI value is accurate to for the given from `&&` to timestamp. Use `span_precision` instead. | [optional] |
-| **preview** | **Boolean** | For `monitor` based SLOs, when `true` this indicates that a replay is in progress to give an accurate uptime calculation. | [optional] |
-| **sli_value** | **Float** | The current SLI value of the SLO over the history window. | [optional] |
-| **span_precision** | **Float** | The amount of decimal places the SLI value is accurate to for the given from `&&` to timestamp. | [optional] |
-| **uptime** | **Float** | Use `sli_value` instead. | [optional] |
+| Name | Type | Description | Notes |
+| -------------------------- | -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **error_budget_remaining** | **Hash<String, Float>** | A mapping of threshold `timeframe` to the remaining error budget. | [optional] |
+| **errors** | [**Array<SLOHistoryResponseErrorWithType>**](SLOHistoryResponseErrorWithType.md) | An array of error objects returned while querying the history data for the service level objective. | [optional] |
+| **group** | **String** | For groups in a grouped SLO, this is the group name. | [optional] |
+| **history** | **Array<Array<Float>>** | For `monitor` based SLOs, this includes the aggregated history as arrays that include time series and uptime data where `0=monitor` is in `OK` state and `1=monitor` is in `alert` state. | [optional] |
+| **monitor_modified** | **Integer** | For `monitor` based SLOs, this is the last modified timestamp in epoch seconds of the monitor. | [optional] |
+| **monitor_type** | **String** | For `monitor` based SLOs, this describes the type of monitor. | [optional] |
+| **name** | **String** | For groups in a grouped SLO, this is the group name. For monitors in a multi-monitor SLO, this is the monitor name. | [optional] |
+| **precision** | **Float** | The amount of decimal places the SLI value is accurate to for the given from `&&` to timestamp. Use `span_precision` instead. | [optional] |
+| **preview** | **Boolean** | For `monitor` based SLOs, when `true` this indicates that a replay is in progress to give an accurate uptime calculation. | [optional] |
+| **sli_value** | **Float** | The current SLI value of the SLO over the history window. | [optional] |
+| **span_precision** | **Float** | The amount of decimal places the SLI value is accurate to for the given from `&&` to timestamp. | [optional] |
+| **uptime** | **Float** | Use `sli_value` instead. | [optional] |
## Example
```ruby
require 'datadog_api_client/v1'
@@ -35,6 +35,5 @@
sli_value: 99.99,
span_precision: 2,
uptime: 99.99
)
```
-