Skip to content

Commit 4df8655

Browse files
author
ci.datadog-api-spec
committed
Regenerate client from commit 0f9d450 of spec repo
1 parent 9462562 commit 4df8655

20 files changed

Lines changed: 193 additions & 91 deletions

‎.generator/schemas/v1/openapi.yaml‎

Lines changed: 24 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25417,7 +25417,14 @@ components:
2541725417
format: int64
2541825418
type: integer
2541925419
feature_flags_config_requests_sum:
25420-
description: Shows the sum of all Feature Flags Client-Side SDK config requests over all hours in the current date for all organizations.
25420+
description: |-
25421+
Shows the sum of all Feature Flags configuration-request usage units from client-side and server-side SDK
25422+
requests over all hours in the current date for all organizations. Each metered client-side request
25423+
contributes 1 unit, and each metered server-side request contributes 10 units. This value already includes
25424+
the server-side multiplier, so do not multiply it again. For example, 100 metered client-side requests and
25425+
10 metered server-side requests total 200 units, not 110. Periods before server-side metering began include
25426+
no server-side requests.
25427+
See [Monthly Flag Configuration Requests](https://docs.datadoghq.com/feature_flags/concepts/monthly_flag_configuration_requests/).
2542125428
format: int64
2542225429
type: integer
2542325430
flex_logs_compute_large_avg:
@@ -26658,7 +26665,14 @@ components:
2665826665
format: int64
2665926666
type: integer
2666026667
feature_flags_config_requests_sum:
26661-
description: Shows the sum of all Feature Flags Client-Side SDK config requests over all hours in the current date for the given org.
26668+
description: |-
26669+
Shows the sum of all Feature Flags configuration-request usage units from client-side and server-side SDK
26670+
requests over all hours in the current date for the given org. Each metered client-side request contributes
26671+
1 unit, and each metered server-side request contributes 10 units. This value already includes the
26672+
server-side multiplier, so do not multiply it again. For example, 100 metered client-side requests and 10
26673+
metered server-side requests total 200 units, not 110. Periods before server-side metering began include no
26674+
server-side requests.
26675+
See [Monthly Flag Configuration Requests](https://docs.datadoghq.com/feature_flags/concepts/monthly_flag_configuration_requests/).
2666226676
format: int64
2666326677
type: integer
2666426678
flex_logs_compute_large_avg:
@@ -27910,7 +27924,14 @@ components:
2791027924
format: int64
2791127925
type: integer
2791227926
feature_flags_config_requests_agg_sum:
27913-
description: Shows the sum of all Feature Flags Client-Side SDK config requests over all hours in the current month for all organizations.
27927+
description: |-
27928+
Shows the sum of all Feature Flags configuration-request usage units from client-side and server-side SDK
27929+
requests over all hours in the current month for all organizations. Each metered client-side request
27930+
contributes 1 unit, and each metered server-side request contributes 10 units. This value already includes
27931+
the server-side multiplier, so do not multiply it again. For example, 100 metered client-side requests and
27932+
10 metered server-side requests total 200 units, not 110. Periods before server-side metering began include
27933+
no server-side requests.
27934+
See [Monthly Flag Configuration Requests](https://docs.datadoghq.com/feature_flags/concepts/monthly_flag_configuration_requests/).
2791427935
format: int64
2791527936
type: integer
2791627937
flex_logs_compute_large_avg_sum:

‎.generator/schemas/v2/openapi.yaml‎

Lines changed: 78 additions & 51 deletions
Large diffs are not rendered by default.

‎examples/v2/tag-rules/CreateTagRule.py‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,15 +20,15 @@
2020
negated=False,
2121
required=True,
2222
rule_type=TagRuleCreateType.SURFACING,
23-
scope="env",
23+
scope="env:prod",
2424
source=TagRuleSource.LOGS,
2525
tag_key="service",
2626
tag_value_patterns=[
2727
"api",
2828
"web",
2929
],
3030
),
31-
type=TagRuleResourceType.TAG_RULE,
31+
type=TagRuleResourceType.TAG_POLICY,
3232
),
3333
)
3434

‎examples/v2/tag-rules/UpdateTagRule.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@
1818
tag_value_patterns=[],
1919
),
2020
id="123",
21-
type=TagRuleResourceType.TAG_RULE,
21+
type=TagRuleResourceType.TAG_POLICY,
2222
),
2323
)
2424

‎src/datadog_api_client/v1/model/usage_summary_date.py‎

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1318,7 +1318,13 @@ def __init__(
13181318
:param fargate_tasks_count_hwm: Shows the average of all Fargate tasks over all hours in the current date for all organizations.
13191319
:type fargate_tasks_count_hwm: int, optional
13201320
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/>`_.
13221328
:type feature_flags_config_requests_sum: int, optional
13231329
13241330
: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.

‎src/datadog_api_client/v1/model/usage_summary_date_org.py‎

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1338,7 +1338,13 @@ def __init__(
13381338
: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.
13391339
:type fargate_tasks_count_hwm: int, optional
13401340
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/>`_.
13421348
:type feature_flags_config_requests_sum: int, optional
13431349
13441350
: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.

‎src/datadog_api_client/v1/model/usage_summary_response.py‎

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1363,7 +1363,13 @@ def __init__(
13631363
: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.
13641364
:type fargate_tasks_count_hwm_sum: int, optional
13651365
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/>`_.
13671373
:type feature_flags_config_requests_agg_sum: int, optional
13681374
13691375
: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.

‎src/datadog_api_client/v2/api/tag_rules_api.py‎

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ class TagRulesApi:
2626
scoped to a particular telemetry source (such as logs, spans, or metrics). Rules can be
2727
``blocking`` (data not matching the rule is rejected) or ``surfacing`` (matching data is
2828
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.
3030
"""
3131

3232
def __init__(self, api_client=None):
@@ -254,7 +254,8 @@ def delete_tag_rule(
254254
255255
Delete a tag rule. By default the rule is soft-deleted so it can be recovered later
256256
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.
258259
259260
:param rule_id: The unique identifier of the tag rule to delete.
260261
:type rule_id: str
@@ -288,7 +289,7 @@ def get_tag_rule(
288289
:type rule_id: str
289290
:param include: Comma-separated list of related resources to include alongside the rule. Currently the only supported value is ``score``.
290291
: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``.
292293
:type ts_start: int, optional
293294
: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``.
294295
:type ts_end: int, optional
@@ -324,7 +325,7 @@ def get_tag_rule_score(
324325
325326
:param rule_id: The unique identifier of the tag rule.
326327
: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``.
328329
:type ts_start: int, optional
329330
: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``.
330331
:type ts_end: int, optional
@@ -365,7 +366,7 @@ def list_tag_rules(
365366
:type include: TagRuleInclude, optional
366367
:param filter_source: Restrict the result set to rules whose source matches the given value.
367368
: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``.
369370
:type ts_start: int, optional
370371
: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``.
371372
:type ts_end: int, optional
@@ -402,6 +403,9 @@ def update_tag_rule(
402403
Update one or more attributes of an existing tag rule. Only the fields supplied in the
403404
request body are modified; omitted fields retain their current values. The rule's
404405
``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``.
405409
406410
:param rule_id: The unique identifier of the tag rule to update.
407411
:type rule_id: str

‎src/datadog_api_client/v2/model/tag_rule_attributes.py‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -119,6 +119,7 @@ def __init__(
119119
120120
:param rule_type: How the rule is enforced. ``blocking`` rejects telemetry that violates the rule.
121121
``surfacing`` only highlights non-compliant telemetry without blocking it.
122+
RUM supports only ``surfacing`` rules.
122123
:type rule_type: TagRuleType
123124
124125
:param scope: The scope the rule applies within.

‎src/datadog_api_client/v2/model/tag_rule_create_attributes.py‎

Lines changed: 16 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,9 @@
2020

2121
class TagRuleCreateAttributes(ModelNormal):
2222
validations = {
23+
"tag_key": {},
2324
"tag_value_patterns": {
25+
"max_items": 30,
2426
"min_items": 1,
2527
},
2628
}
@@ -68,9 +70,11 @@ def __init__(
6870
**kwargs,
6971
):
7072
"""
71-
Attributes that can be supplied when creating a tag rule.
73+
Attributes that can be supplied when creating a tag rule. If ``tag_value_patterns``
74+
contains ``*`` , set ``required`` and ``negated`` to different values. If both are ``false`` ,
75+
the rule has no effect. If both are ``true`` , no value can satisfy the rule.
7276
73-
:param enabled: Whether the rule is currently enforced. Defaults to ``true`` for newly created rules.
77+
:param enabled: The API ignores this value on creation and always enables new rules. To disable a rule, use the "Update a tag rule" endpoint.
7478
:type enabled: bool, optional
7579
7680
:param name: Human-readable name for the tag rule.
@@ -86,18 +90,23 @@ def __init__(
8690
creation time.
8791
:type rule_type: TagRuleCreateType
8892
89-
:param scope: The scope the rule applies within. Typically an environment, team, or
90-
organization-level identifier used to limit where the rule is enforced.
93+
:param scope: The scope the rule applies within. For logs and spans, use a search query, such
94+
as ``env:prod`` , or ``*`` to match all telemetry. For metrics, use a metric selector
95+
with an optional tag filter, such as ``system.cpu.*{env:prod}``. A metric wildcard
96+
is allowed only once, at the end of the metric selector.
9197
:type scope: str
9298
9399
:param source: The telemetry source that a tag rule applies to.
94100
:type source: TagRuleSource
95101
96-
:param tag_key: The tag key that the rule governs (for example, ``service`` ).
102+
:param tag_key: The tag key that the rule governs (for example, ``service`` ). Allowed characters
103+
are ASCII letters, digits, underscores, hyphens, periods, and slashes. The keys
104+
``host`` and ``device`` are not supported in any letter case.
97105
:type tag_key: str
98106
99-
:param tag_value_patterns: One or more patterns that valid values for the tag key must match. At least one
100-
pattern is required.
107+
:param tag_value_patterns: Between 1 and 30 non-empty patterns that valid values for the tag key must match.
108+
Allowed characters are ASCII letters, digits, underscores, colons, hyphens,
109+
periods, commas, slashes, and asterisks.
101110
:type tag_value_patterns: [str]
102111
"""
103112
if enabled is not unset:

0 commit comments

Comments
 (0)