You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4df8655
Browse filesBrowse the repository at this point in the historyBrowse files
ci.datadog-api-spec
committed
Regenerate client from commit 0f9d450 of spec repo
Copy file name to clipboardExpand all lines: src/datadog_api_client/v1/model/usage_summary_date.py
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1318,7 +1318,13 @@ def __init__(
1318
1318
:param fargate_tasks_count_hwm: Shows the average of all Fargate tasks over all hours in the current date for all organizations.
1319
1319
:type fargate_tasks_count_hwm: int, optional
1320
1320
1321
-
:param feature_flags_config_requests_sum: Shows the sum of all Feature Flags Client-Side SDK config requests over all hours in the current date for all organizations.
1321
+
:param feature_flags_config_requests_sum: Shows the sum of all Feature Flags configuration-request usage units from client-side and server-side SDK
1322
+
requests over all hours in the current date for all organizations. Each metered client-side request
1323
+
contributes 1 unit, and each metered server-side request contributes 10 units. This value already includes
1324
+
the server-side multiplier, so do not multiply it again. For example, 100 metered client-side requests and
1325
+
10 metered server-side requests total 200 units, not 110. Periods before server-side metering began include
1326
+
no server-side requests.
1327
+
See `Monthly Flag Configuration Requests <https://docs.datadoghq.com/feature_flags/concepts/monthly_flag_configuration_requests/>`_.
:param flex_logs_compute_large_avg: Shows the average number of Flex Logs Compute Large Instances over all hours in the current date for the given org.
Copy file name to clipboardExpand all lines: src/datadog_api_client/v1/model/usage_summary_date_org.py
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1338,7 +1338,13 @@ def __init__(
1338
1338
:param fargate_tasks_count_hwm: Shows the high-water mark of all Fargate tasks over all hours in the current date for the given org.
1339
1339
:type fargate_tasks_count_hwm: int, optional
1340
1340
1341
-
:param feature_flags_config_requests_sum: Shows the sum of all Feature Flags Client-Side SDK config requests over all hours in the current date for the given org.
1341
+
:param feature_flags_config_requests_sum: Shows the sum of all Feature Flags configuration-request usage units from client-side and server-side SDK
1342
+
requests over all hours in the current date for the given org. Each metered client-side request contributes
1343
+
1 unit, and each metered server-side request contributes 10 units. This value already includes the
1344
+
server-side multiplier, so do not multiply it again. For example, 100 metered client-side requests and 10
1345
+
metered server-side requests total 200 units, not 110. Periods before server-side metering began include no
1346
+
server-side requests.
1347
+
See `Monthly Flag Configuration Requests <https://docs.datadoghq.com/feature_flags/concepts/monthly_flag_configuration_requests/>`_.
:param flex_logs_compute_large_avg: Shows the average number of Flex Logs Compute Large Instances over all hours in the current date for the given org.
Copy file name to clipboardExpand all lines: src/datadog_api_client/v1/model/usage_summary_response.py
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1363,7 +1363,13 @@ def __init__(
1363
1363
:param fargate_tasks_count_hwm_sum: Shows the sum of the high-water marks of all Fargate tasks over all hours in the current month for all organizations.
1364
1364
:type fargate_tasks_count_hwm_sum: int, optional
1365
1365
1366
-
:param feature_flags_config_requests_agg_sum: Shows the sum of all Feature Flags Client-Side SDK config requests over all hours in the current month for all organizations.
1366
+
:param feature_flags_config_requests_agg_sum: Shows the sum of all Feature Flags configuration-request usage units from client-side and server-side SDK
1367
+
requests over all hours in the current month for all organizations. Each metered client-side request
1368
+
contributes 1 unit, and each metered server-side request contributes 10 units. This value already includes
1369
+
the server-side multiplier, so do not multiply it again. For example, 100 metered client-side requests and
1370
+
10 metered server-side requests total 200 units, not 110. Periods before server-side metering began include
1371
+
no server-side requests.
1372
+
See `Monthly Flag Configuration Requests <https://docs.datadoghq.com/feature_flags/concepts/monthly_flag_configuration_requests/>`_.
:param flex_logs_compute_large_avg_sum: Shows the average number of Flex Logs Compute Large Instances over all hours in the current months for all organizations.
Copy file name to clipboardExpand all lines: src/datadog_api_client/v2/api/tag_rules_api.py
+9-5Lines changed: 9 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ class TagRulesApi:
26
26
scoped to a particular telemetry source (such as logs, spans, or metrics). Rules can be
27
27
``blocking`` (data not matching the rule is rejected) or ``surfacing`` (matching data is
28
28
highlighted but not blocked). Each rule reports a compliance ``score`` derived from how
29
-
much recent telemetry adheres to the rule.
29
+
much recent telemetry adheres to the rule. RUM supports only ``surfacing`` rules.
30
30
"""
31
31
32
32
def__init__(self, api_client=None):
@@ -254,7 +254,8 @@ def delete_tag_rule(
254
254
255
255
Delete a tag rule. By default the rule is soft-deleted so it can be recovered later
256
256
and so that historical score data remains queryable. Pass ``hard_delete=true`` to remove
257
-
the rule permanently.
257
+
the rule permanently. Deleting a ``blocking`` rule additionally requires the
258
+
``telemetry_rules_activate`` permission.
258
259
259
260
:param rule_id: The unique identifier of the tag rule to delete.
260
261
:type rule_id: str
@@ -288,7 +289,7 @@ def get_tag_rule(
288
289
:type rule_id: str
289
290
:param include: Comma-separated list of related resources to include alongside the rule. Currently the only supported value is ``score``.
290
291
:type include: TagRuleInclude, optional
291
-
:param ts_start: Start of the time window used for compliance score computation, as a Unix timestamp in milliseconds.
292
+
:param ts_start: Start of the time window used for compliance score computation, as a Unix timestamp in milliseconds. Defaults to approximately 4 hours before the current time for metrics, or 24 hours before the current time for other sources. The API clamps earlier values to this default, regardless of ``ts_end``.
292
293
:type ts_start: int, optional
293
294
:param ts_end: End of the time window used for compliance score computation, as a Unix timestamp in milliseconds. Must be in the past and greater than ``ts_start``.
294
295
:type ts_end: int, optional
@@ -324,7 +325,7 @@ def get_tag_rule_score(
324
325
325
326
:param rule_id: The unique identifier of the tag rule.
326
327
:type rule_id: str
327
-
:param ts_start: Start of the time window used for compliance score computation, as a Unix timestamp in milliseconds.
328
+
:param ts_start: Start of the time window used for compliance score computation, as a Unix timestamp in milliseconds. Defaults to approximately 4 hours before the current time for metrics, or 24 hours before the current time for other sources. The API clamps earlier values to this default, regardless of ``ts_end``.
328
329
:type ts_start: int, optional
329
330
:param ts_end: End of the time window used for compliance score computation, as a Unix timestamp in milliseconds. Must be in the past and greater than ``ts_start``.
330
331
:type ts_end: int, optional
@@ -365,7 +366,7 @@ def list_tag_rules(
365
366
:type include: TagRuleInclude, optional
366
367
:param filter_source: Restrict the result set to rules whose source matches the given value.
367
368
:type filter_source: TagRuleSource, optional
368
-
:param ts_start: Start of the time window used for compliance score computation, as a Unix timestamp in milliseconds. Defaults to a recent window appropriate for the source.
369
+
:param ts_start: Start of the time window used for compliance score computation, as a Unix timestamp in milliseconds. Defaults to approximately 4 hours before the current time for metrics, or 24 hours before the current time for other sources. The API clamps earlier values to this default, regardless of ``ts_end``.
369
370
:type ts_start: int, optional
370
371
:param ts_end: End of the time window used for compliance score computation, as a Unix timestamp in milliseconds. Must be in the past and greater than ``ts_start``.
371
372
:type ts_end: int, optional
@@ -402,6 +403,9 @@ def update_tag_rule(
402
403
Update one or more attributes of an existing tag rule. Only the fields supplied in the
403
404
request body are modified; omitted fields retain their current values. The rule's
404
405
``source`` cannot be changed after creation.
406
+
Promoting a rule from ``surfacing`` to ``blocking`` additionally requires the
407
+
``telemetry_rules_activate`` permission, and your organization must have access to
408
+
blocking rules. You can't promote RUM rules to ``blocking``.
405
409
406
410
:param rule_id: The unique identifier of the tag rule to update.
0 commit comments