Security Monitoring Suppression - Add data_exclusion_query field (#1940)

Co-authored-by: ci.datadog-api-spec <[email protected]>
Co-authored-by: api-clients-generation-pipeline[bot] <54105614+api-clients-generation-pipeline[bot]@users.noreply.github.com> a570a08

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

datadog_api_client.v2.model.html

@@ -41201,6 +41201,7 @@ <h1 id="datadog-api-client-v2-model--page-root">datadog_api_client.v2.model<a cl
 <dd class="field-odd"><ul class="simple">
 <li><p><strong>creation_date</strong> (<em>int</em><em>, </em><em>optional</em>) – A Unix millisecond timestamp given the creation date of the suppression rule.</p></li>
 <li><p><strong>creator</strong> (<a class="reference internal" href="#datadog_api_client.v2.model.security_monitoring_user.SecurityMonitoringUser" title="datadog_api_client.v2.model.security_monitoring_user.SecurityMonitoringUser"><em>SecurityMonitoringUser</em></a><em>, </em><em>optional</em>) – A user.</p></li>
+<li><p><strong>data_exclusion_query</strong> (<em>str</em><em>, </em><em>optional</em>) – An exclusion query on the input data of the security rules, which could be logs, Agent events, or other types of data based on the security rule. Events matching this query are ignored by any detection rules referenced in the suppression rule.</p></li>
 <li><p><strong>description</strong> (<em>str</em><em>, </em><em>optional</em>) – A description for the suppression rule.</p></li>
 <li><p><strong>enabled</strong> (<em>bool</em><em>, </em><em>optional</em>) – Whether the suppression rule is enabled.</p></li>
 <li><p><strong>expiration_date</strong> (<em>int</em><em>, </em><em>optional</em>) – A Unix millisecond timestamp giving an expiration date for the suppression rule. After this date, it won’t suppress signals anymore.</p></li>
@@ -41225,12 +41226,13 @@ <h1 id="datadog-api-client-v2-model--page-root">datadog_api_client.v2.model<a cl
 <dl class="field-list simple">
 <dt class="field-odd">Parameters<span class="colon">:</span></dt>
 <dd class="field-odd"><ul class="simple">
+<li><p><strong>data_exclusion_query</strong> (<em>str</em><em>, </em><em>optional</em>) – An exclusion query on the input data of the security rules, which could be logs, Agent events, or other types of data based on the security rule. Events matching this query are ignored by any detection rules referenced in the suppression rule.</p></li>
 <li><p><strong>description</strong> (<em>str</em><em>, </em><em>optional</em>) – A description for the suppression rule.</p></li>
 <li><p><strong>enabled</strong> (<em>bool</em>) – Whether the suppression rule is enabled.</p></li>
 <li><p><strong>expiration_date</strong> (<em>int</em><em>, </em><em>optional</em>) – A Unix millisecond timestamp giving an expiration date for the suppression rule. After this date, it won’t suppress signals anymore.</p></li>
 <li><p><strong>name</strong> (<em>str</em>) – The name of the suppression rule.</p></li>
 <li><p><strong>rule_query</strong> (<em>str</em>) – The rule query of the suppression rule, with the same syntax as the search bar for detection rules.</p></li>
-<li><p><strong>suppression_query</strong> (<em>str</em>) – The suppression query of the suppression rule. If a signal matches this query, it is suppressed and is not triggered . Same syntax as the queries to search signals in the signal explorer.</p></li>
+<li><p><strong>suppression_query</strong> (<em>str</em><em>, </em><em>optional</em>) – The suppression query of the suppression rule. If a signal matches this query, it is suppressed and is not triggered. It uses the same syntax as the queries to search signals in the Signals Explorer.</p></li>
 </ul>
 </dd>
 </dl>
@@ -41318,6 +41320,7 @@ <h1 id="datadog-api-client-v2-model--page-root">datadog_api_client.v2.model<a cl
 <dl class="field-list simple">
 <dt class="field-odd">Parameters<span class="colon">:</span></dt>
 <dd class="field-odd"><ul class="simple">
+<li><p><strong>data_exclusion_query</strong> (<em>str</em><em>, </em><em>optional</em>) – An exclusion query on the input data of the security rules, which could be logs, Agent events, or other types of data based on the security rule. Events matching this query are ignored by any detection rules referenced in the suppression rule.</p></li>
 <li><p><strong>description</strong> (<em>str</em><em>, </em><em>optional</em>) – A description for the suppression rule.</p></li>
 <li><p><strong>enabled</strong> (<em>bool</em><em>, </em><em>optional</em>) – Whether the suppression rule is enabled.</p></li>
 <li><p><strong>expiration_date</strong> (<em>int</em><em>, </em><em>none_type</em><em>, </em><em>optional</em>) – A Unix millisecond timestamp giving an expiration date for the suppression rule. After this date, it won’t suppress signals anymore. If unset, the expiration date of the suppression rule is left untouched. If set to <code class="docutils literal notranslate"><span class="pre">null</span></code> , the expiration date is removed.</p></li>