From 4b7a9e0d2b696d3ca89a0f42fd328b6206944b4f Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Fri, 2 Oct 2026 15:44:26 +0000 Subject: [PATCH] Regenerate client from commit 6242232 of spec repo --- .generator/schemas/v2/openapi.yaml | 16 ++++++++++++---- .../v2/api/logs_archive_searches_api.py | 13 +++++++++---- tests/v2/features/logs_archive_searches.feature | 14 +++++++++----- 3 files changed, 30 insertions(+), 13 deletions(-) diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml index 9dd8e972ab..3c1b8d09e5 100644 --- a/.generator/schemas/v2/openapi.yaml +++ b/.generator/schemas/v2/openapi.yaml @@ -232992,11 +232992,19 @@ tags: Search your logs and send them to your Datadog platform over HTTP. See the [Log Management page](https://docs.datadoghq.com/logs/) for more information. name: Logs - description: |- - Search the logs stored in a Logs Archive without reindexing them, and optionally rehydrate - the matches into a retained historical view. + Archive Search queries logs directly from long-term storage archives without prior + rehydration and charges only for the data scanned. - See the [Rehydrating from Archives](https://app.datadoghq.com/logs/pipelines/historical-views) - page for the searches currently running in Datadog. + A search runs in one of two modes. By default it scans the archive and retains up to + 100,000 matching logs for 24 hours on a dedicated results page. Include a `rehydration` + object to run a Search & Rehydration instead, which retains the matches for a custom + retention period and makes them available in Log Explorer, Dashboards, and Notebooks. + + A search requires the `logs_write_historical_view` or `logs_write_archive_search` + permission. Rehydration requires `logs_write_historical_view`. + externalDocs: + description: Find out more at + url: https://docs.datadoghq.com/logs/explorer/archive_search/ name: Logs Archive Searches - description: |- Archives forward all the logs ingested to a cloud storage system. diff --git a/src/datadog_api_client/v2/api/logs_archive_searches_api.py b/src/datadog_api_client/v2/api/logs_archive_searches_api.py index dc9c7576dd..ed0084debe 100644 --- a/src/datadog_api_client/v2/api/logs_archive_searches_api.py +++ b/src/datadog_api_client/v2/api/logs_archive_searches_api.py @@ -13,11 +13,16 @@ class LogsArchiveSearchesApi: """ - Search the logs stored in a Logs Archive without reindexing them, and optionally rehydrate - the matches into a retained historical view. + Archive Search queries logs directly from long-term storage archives without prior + rehydration and charges only for the data scanned. - See the `Rehydrating from Archives `_ - page for the searches currently running in Datadog. + A search runs in one of two modes. By default it scans the archive and retains up to + 100,000 matching logs for 24 hours on a dedicated results page. Include a ``rehydration`` + object to run a Search & Rehydration instead, which retains the matches for a custom + retention period and makes them available in Log Explorer, Dashboards, and Notebooks. + + A search requires the ``logs_write_historical_view`` or ``logs_write_archive_search`` + permission. Rehydration requires ``logs_write_historical_view``. """ def __init__(self, api_client=None): diff --git a/tests/v2/features/logs_archive_searches.feature b/tests/v2/features/logs_archive_searches.feature index 185e088c68..89e33b6e0f 100644 --- a/tests/v2/features/logs_archive_searches.feature +++ b/tests/v2/features/logs_archive_searches.feature @@ -1,10 +1,14 @@ @endpoint(logs-archive-searches) @endpoint(logs-archive-searches-v2) Feature: Logs Archive Searches - Search the logs stored in a Logs Archive without reindexing them, and - optionally rehydrate the matches into a retained historical view. See the - [Rehydrating from - Archives](https://app.datadoghq.com/logs/pipelines/historical-views) page - for the searches currently running in Datadog. + Archive Search queries logs directly from long-term storage archives + without prior rehydration and charges only for the data scanned. A search + runs in one of two modes. By default it scans the archive and retains up + to 100,000 matching logs for 24 hours on a dedicated results page. Include + a `rehydration` object to run a Search & Rehydration instead, which + retains the matches for a custom retention period and makes them available + in Log Explorer, Dashboards, and Notebooks. A search requires the + `logs_write_historical_view` or `logs_write_archive_search` permission. + Rehydration requires `logs_write_historical_view`. Background: Given a valid "apiKeyAuth" key in the system