docs/v2/SecurityMonitoringRuleCase.md in datadog_api_client-1.4.0 vs docs/v2/SecurityMonitoringRuleCase.md in datadog_api_client-1.5.0
- old
+ new
@@ -1,15 +1,15 @@
# DatadogAPIClient::V2::SecurityMonitoringRuleCase
## Properties
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **condition** | **String** | A rule case contains logical operations (`>`,`>=`, `&&`, `||`) to determine if a signal should be generated based on the event counts in the previously defined queries. | [optional] |
-| **name** | **String** | Name of the case. | [optional] |
-| **notifications** | **Array<String>** | Notification targets for each rule case. | [optional] |
-| **status** | [**SecurityMonitoringRuleSeverity**](SecurityMonitoringRuleSeverity.md) | | [optional] |
+| Name | Type | Description | Notes |
+| ----------------- | ----------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------- | ----------------------------------------------------------------------------------------------------------------- | ---------- |
+| **condition** | **String** | A rule case contains logical operations (`>`,`>=`, `&&`, ` | | `) to determine if a signal should be generated based on the event counts in the previously defined queries. | [optional] |
+| **name** | **String** | Name of the case. | [optional] |
+| **notifications** | **Array<String>** | Notification targets for each rule case. | [optional] |
+| **status** | [**SecurityMonitoringRuleSeverity**](SecurityMonitoringRuleSeverity.md) | | [optional] |
## Example
```ruby
require 'datadog_api_client/v2'
@@ -19,6 +19,5 @@
name: null,
notifications: null,
status: null
)
```
-