From 3718e07827a5545f040176c5aca9d6c9edb31a71 Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Thu, 22 Oct 2026 14:47:27 +0000 Subject: [PATCH] Regenerate client from commit 7edb743 of spec repo --- tests/v2/features/logs.feature | 16 +++--- .../v2/features/logs_archive_searches.feature | 12 ++-- tests/v2/features/logs_archives.feature | 50 ++++++++--------- .../features/logs_custom_destinations.feature | 56 +++++++++---------- tests/v2/features/logs_metrics.feature | 24 ++++---- 5 files changed, 79 insertions(+), 79 deletions(-) diff --git a/tests/v2/features/logs.feature b/tests/v2/features/logs.feature index 2f2f2bdfaf..067f67dad2 100644 --- a/tests/v2/features/logs.feature +++ b/tests/v2/features/logs.feature @@ -128,7 +128,7 @@ Feature: Logs Then the response status is 200 OK And the response has 3 items - @integration-only @skip-terraform-config @skip-validation @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-ingestion + @integration-only @skip-terraform-config @skip-validation @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Send deflate logs returns "Request accepted for processing (always 202 empty JSON)." response Given new "SubmitLog" request And body with value [{"ddsource": "nginx", "ddtags": "env:staging,version:5.1", "hostname": "i-012345678", "message": "2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World", "service": "payment"}] @@ -136,7 +136,7 @@ Feature: Logs When the request is sent Then the response status is 202 Response from server (always 202 empty JSON). - @skip-terraform-config @skip-validation @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-ingestion + @skip-terraform-config @skip-validation @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Send deflate logs with explicit compression returns "Request accepted for processing (always 202 empty JSON)." response Given new "SubmitLog" request And body with value [{"ddsource": "nginx", "ddtags": "env:staging,version:5.1", "hostname": "i-012345678", "message": "2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World", "service": "payment"}] @@ -145,7 +145,7 @@ Feature: Logs Then the response status is 202 Response from server (always 202 empty JSON). And the request uses "deflate" compression - @integration-only @skip-terraform-config @skip-validation @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-ingestion + @integration-only @skip-terraform-config @skip-validation @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Send gzip logs returns "Request accepted for processing (always 202 empty JSON)." response Given new "SubmitLog" request And body with value [{"ddsource": "nginx", "ddtags": "env:staging,version:5.1", "hostname": "i-012345678", "message": "2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World", "service": "payment"}] @@ -153,7 +153,7 @@ Feature: Logs When the request is sent Then the response status is 202 Request accepted for processing (always 202 empty JSON). - @skip-terraform-config @skip-validation @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-ingestion + @skip-terraform-config @skip-validation @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Send gzip logs with explicit compression returns "Request accepted for processing (always 202 empty JSON)." response Given new "SubmitLog" request And body with value [{"ddsource": "nginx", "ddtags": "env:staging,version:5.1", "hostname": "i-012345678", "message": "2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World", "service": "payment"}] @@ -162,28 +162,28 @@ Feature: Logs Then the response status is 202 Request accepted for processing (always 202 empty JSON). And the request uses "gzip" compression - @generated @skip @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-ingestion + @generated @skip @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Send logs returns "Bad Request" response Given new "SubmitLog" request And body with value [{"ddsource": "nginx", "ddtags": "env:staging,version:5.1", "hostname": "i-012345678", "message": "2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World", "service": "payment"}] When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-ingestion + @generated @skip @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Send logs returns "Payload Too Large" response Given new "SubmitLog" request And body with value [{"ddsource": "nginx", "ddtags": "env:staging,version:5.1", "hostname": "i-012345678", "message": "2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World", "service": "payment"}] When the request is sent Then the response status is 413 Payload Too Large - @generated @skip @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-ingestion + @generated @skip @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Send logs returns "Request Timeout" response Given new "SubmitLog" request And body with value [{"ddsource": "nginx", "ddtags": "env:staging,version:5.1", "hostname": "i-012345678", "message": "2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World", "service": "payment"}] When the request is sent Then the response status is 408 Request Timeout - @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-ingestion + @team:ddoghq/event-platform-intake @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Send logs returns "Request accepted for processing (always 202 empty JSON)." response Given new "SubmitLog" request And body with value [{"ddsource": "nginx", "ddtags": "env:staging,version:5.1", "hostname": "i-012345678", "message": "2019-11-19T14:37:58,995 INFO [process.name][20081] Hello World", "service": "payment", "status": "info"}] diff --git a/tests/v2/features/logs_archive_searches.feature b/tests/v2/features/logs_archive_searches.feature index 452f5bc642..a35e8776ca 100644 --- a/tests/v2/features/logs_archive_searches.feature +++ b/tests/v2/features/logs_archive_searches.feature @@ -16,7 +16,7 @@ Feature: Logs Archive Searches And a valid "appKeyAuth" key in the system And an instance of "LogsArchiveSearches" API - @generated @skip @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create an Archive Search returns "Bad Request" response Given operation "CreateArchiveSearch" enabled And new "CreateArchiveSearch" request @@ -24,7 +24,7 @@ Feature: Logs Archive Searches When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create an Archive Search returns "Not Found" response Given operation "CreateArchiveSearch" enabled And new "CreateArchiveSearch" request @@ -32,7 +32,7 @@ Feature: Logs Archive Searches When the request is sent Then the response status is 404 Not Found - @generated @skip @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create an Archive Search returns "OK" response Given operation "CreateArchiveSearch" enabled And new "CreateArchiveSearch" request @@ -40,7 +40,7 @@ Feature: Logs Archive Searches When the request is sent Then the response status is 200 OK - @generated @skip @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get an Archive Search returns "Bad Request" response Given operation "GetArchiveSearch" enabled And new "GetArchiveSearch" request @@ -48,7 +48,7 @@ Feature: Logs Archive Searches When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get an Archive Search returns "Not Found" response Given operation "GetArchiveSearch" enabled And new "GetArchiveSearch" request @@ -56,7 +56,7 @@ Feature: Logs Archive Searches When the request is sent Then the response status is 404 Not Found - @generated @skip @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get an Archive Search returns "OK" response Given operation "GetArchiveSearch" enabled And new "GetArchiveSearch" request diff --git a/tests/v2/features/logs_archives.feature b/tests/v2/features/logs_archives.feature index 5b842bdfd8..808ae35aef 100644 --- a/tests/v2/features/logs_archives.feature +++ b/tests/v2/features/logs_archives.feature @@ -9,75 +9,75 @@ Feature: Logs Archives And a valid "appKeyAuth" key in the system And an instance of "LogsArchives" API - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create an archive returns "Bad Request" response Given new "CreateLogsArchive" request And body with value {"data": {"attributes": {"compression_method": "GZIP", "destination": {"container": "container-name", "integration": {"client_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa", "tenant_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa"}, "storage_account": "account-name", "type": "azure"}, "include_tags": false, "lookup_attributes": ["trace_id", "user_id"], "name": "Nginx Archive", "partitioning_attributes": ["service", "status"], "query": "source:nginx", "rehydration_max_scan_size_in_gb": 100, "rehydration_tags": ["team:intake", "team:app"]}, "type": "archives"}} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create an archive returns "OK" response Given new "CreateLogsArchive" request And body with value {"data": {"attributes": {"compression_method": "GZIP", "destination": {"container": "container-name", "integration": {"client_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa", "tenant_id": "aaaaaaaa-1a1a-1a1a-1a1a-aaaaaaaaaaaa"}, "storage_account": "account-name", "type": "azure"}, "include_tags": false, "lookup_attributes": ["trace_id", "user_id"], "name": "Nginx Archive", "partitioning_attributes": ["service", "status"], "query": "source:nginx", "rehydration_max_scan_size_in_gb": 100, "rehydration_tags": ["team:intake", "team:app"]}, "type": "archives"}} When the request is sent Then the response status is 200 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Delete an archive returns "Bad Request" response Given new "DeleteLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Delete an archive returns "Not found" response Given new "DeleteLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not found - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Delete an archive returns "OK" response Given new "DeleteLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 204 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get all archives returns "OK" response Given new "ListLogsArchives" request When the request is sent Then the response status is 200 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get an archive returns "Bad Request" response Given new "GetLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get an archive returns "Not found" response Given new "GetLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not found - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get an archive returns "OK" response Given new "GetLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 200 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get archive order returns "OK" response Given new "GetLogsArchiveOrder" request When the request is sent Then the response status is 200 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Grant role to an archive returns "Bad Request" response Given new "AddReadRoleToArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -85,7 +85,7 @@ Feature: Logs Archives When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Grant role to an archive returns "Not found" response Given new "AddReadRoleToArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -93,7 +93,7 @@ Feature: Logs Archives When the request is sent Then the response status is 404 Not found - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Grant role to an archive returns "OK" response Given new "AddReadRoleToArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -101,28 +101,28 @@ Feature: Logs Archives When the request is sent Then the response status is 204 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: List read roles for an archive returns "Bad Request" response Given new "ListArchiveReadRoles" request And request contains "archive_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: List read roles for an archive returns "Not found" response Given new "ListArchiveReadRoles" request And request contains "archive_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not found - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: List read roles for an archive returns "OK" response Given new "ListArchiveReadRoles" request And request contains "archive_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 200 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Revoke role from an archive returns "Bad Request" response Given new "RemoveRoleFromArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -130,7 +130,7 @@ Feature: Logs Archives When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Revoke role from an archive returns "Not found" response Given new "RemoveRoleFromArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -138,7 +138,7 @@ Feature: Logs Archives When the request is sent Then the response status is 404 Not found - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Revoke role from an archive returns "OK" response Given new "RemoveRoleFromArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -146,7 +146,7 @@ Feature: Logs Archives When the request is sent Then the response status is 204 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update an archive returns "Bad Request" response Given new "UpdateLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -154,7 +154,7 @@ Feature: Logs Archives When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update an archive returns "Not found" response Given new "UpdateLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -162,7 +162,7 @@ Feature: Logs Archives When the request is sent Then the response status is 404 Not found - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update an archive returns "OK" response Given new "UpdateLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -170,21 +170,21 @@ Feature: Logs Archives When the request is sent Then the response status is 200 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update archive order returns "Bad Request" response Given new "UpdateLogsArchiveOrder" request And body with value {"data": {"attributes": {"archive_ids": ["a2zcMylnM4OCHpYusxIi1g", "a2zcMylnM4OCHpYusxIi2g", "a2zcMylnM4OCHpYusxIi3g"]}, "type": "archive_order"}} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update archive order returns "OK" response Given new "UpdateLogsArchiveOrder" request And body with value {"data": {"attributes": {"archive_ids": ["a2zcMylnM4OCHpYusxIi1g", "a2zcMylnM4OCHpYusxIi2g", "a2zcMylnM4OCHpYusxIi3g"]}, "type": "archive_order"}} When the request is sent Then the response status is 200 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update archive order returns "Unprocessable Entity" response Given new "UpdateLogsArchiveOrder" request And body with value {"data": {"attributes": {"archive_ids": ["a2zcMylnM4OCHpYusxIi1g", "a2zcMylnM4OCHpYusxIi2g", "a2zcMylnM4OCHpYusxIi3g"]}, "type": "archive_order"}} diff --git a/tests/v2/features/logs_custom_destinations.feature b/tests/v2/features/logs_custom_destinations.feature index 2b5534e611..477ebc7230 100644 --- a/tests/v2/features/logs_custom_destinations.feature +++ b/tests/v2/features/logs_custom_destinations.feature @@ -13,7 +13,7 @@ Feature: Logs Custom Destinations And a valid "appKeyAuth" key in the system And an instance of "LogsCustomDestinations" API - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a Basic HTTP custom destination returns "OK" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": false, "forward_tags": false, "forward_tags_restriction_list": ["datacenter", "host"], "forward_tags_restriction_list_type": "ALLOW_LIST", "forwarder_destination": {"auth": {"password": "datadog-custom-destination-password", "type": "basic", "username": "datadog-custom-destination-username"}, "endpoint": "https://example.com", "type": "http"}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} @@ -35,7 +35,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forward_tags_restriction_list" array contains value "host" And the response "data.attributes.forward_tags_restriction_list_type" is equal to "ALLOW_LIST" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a Custom Header HTTP custom destination returns "OK" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": false, "forward_tags": false, "forward_tags_restriction_list": ["datacenter", "host"], "forward_tags_restriction_list_type": "ALLOW_LIST", "forwarder_destination": {"auth": {"header_value": "my-secret", "type": "custom_header", "header_name": "MY-AUTHENTICATION-HEADER"}, "endpoint": "https://example.com", "type": "http"}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} @@ -57,7 +57,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forward_tags_restriction_list" array contains value "host" And the response "data.attributes.forward_tags_restriction_list_type" is equal to "ALLOW_LIST" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a Microsoft Sentinel custom destination returns "OK" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": false, "forward_tags": false, "forward_tags_restriction_list": ["datacenter", "host"], "forward_tags_restriction_list_type": "ALLOW_LIST", "forwarder_destination": {"type": "microsoft_sentinel", "tenant_id": "f3c9a8a1-4c2e-4d2e-b911-9f3c28c3c8b2", "client_id": "9a2f4d83-2b5e-429e-a35a-2b3c4182db71", "data_collection_endpoint": "https://my-dce-5kyl.eastus-1.ingest.monitor.azure.com", "data_collection_rule_id": "dcr-000a00a000a00000a000000aa000a0aa", "stream_name": "Custom-MyTable"}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} @@ -80,7 +80,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forward_tags_restriction_list" array contains value "host" And the response "data.attributes.forward_tags_restriction_list_type" is equal to "ALLOW_LIST" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a Splunk custom destination returns "OK" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": false, "forward_tags": false, "forward_tags_restriction_list": ["datacenter", "host"], "forward_tags_restriction_list_type": "ALLOW_LIST", "forwarder_destination": {"access_token": "my-access-token", "endpoint": "https://example.com", "type": "splunk_hec"}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} @@ -101,7 +101,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forward_tags_restriction_list" array contains value "host" And the response "data.attributes.forward_tags_restriction_list_type" is equal to "ALLOW_LIST" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a Splunk custom destination with a null sourcetype returns "OK" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": false, "forward_tags": false, "forwarder_destination": {"access_token": "my-access-token", "endpoint": "https://example.com", "type": "splunk_hec", "sourcetype": null}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} @@ -114,7 +114,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forwarder_destination" does not have field "access_token" And the response "data.attributes.forwarder_destination.sourcetype" is equal to null - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a Splunk custom destination with a sourcetype returns "OK" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": false, "forward_tags": false, "forwarder_destination": {"access_token": "my-access-token", "endpoint": "https://example.com", "type": "splunk_hec", "sourcetype": "my-sourcetype"}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} @@ -127,7 +127,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forwarder_destination" does not have field "access_token" And the response "data.attributes.forwarder_destination.sourcetype" is equal to "my-sourcetype" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a Splunk custom destination with an empty string sourcetype returns "OK" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": false, "forward_tags": false, "forwarder_destination": {"access_token": "my-access-token", "endpoint": "https://example.com", "type": "splunk_hec", "sourcetype": ""}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} @@ -140,7 +140,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forwarder_destination" does not have field "access_token" And the response "data.attributes.forwarder_destination.sourcetype" is equal to "" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a Splunk custom destination without a sourcetype returns "OK" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": false, "forward_tags": false, "forwarder_destination": {"access_token": "my-access-token", "endpoint": "https://example.com", "type": "splunk_hec"}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} @@ -153,28 +153,28 @@ Feature: Logs Custom Destinations And the response "data.attributes.forwarder_destination" does not have field "access_token" And the response "data.attributes.forwarder_destination" does not have field "sourcetype" - @skip-java @skip-python @skip-rust @skip-typescript @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @skip-java @skip-python @skip-rust @skip-typescript @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a custom destination returns "Bad Request" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"name": "Nginx logs"}, "type": "custom_destination"}} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a custom destination returns "Conflict" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": true, "forward_tags": true, "forward_tags_restriction_list": ["datacenter", "host"], "forward_tags_restriction_list_type": "ALLOW_LIST", "forwarder_destination": {"auth": {"password": "datadog-custom-destination-password", "type": "basic", "username": "datadog-custom-destination-username"}, "endpoint": "https://example.com", "type": "http"}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} When the request is sent Then the response status is 409 Conflict - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a custom destination returns "OK" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": true, "forward_tags": true, "forward_tags_restriction_list": ["datacenter", "host"], "forward_tags_restriction_list_type": "ALLOW_LIST", "forwarder_destination": {"auth": {"password": "datadog-custom-destination-password", "type": "basic", "username": "datadog-custom-destination-username"}, "endpoint": "https://example.com", "type": "http"}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} When the request is sent Then the response status is 200 OK - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create an Elasticsearch custom destination returns "OK" response Given new "CreateLogsCustomDestination" request And body with value {"data": {"attributes": {"enabled": false, "forward_tags": false, "forward_tags_restriction_list": ["datacenter", "host"], "forward_tags_restriction_list_type": "ALLOW_LIST", "forwarder_destination": {"auth": {"username": "my-username", "password": "my-password"}, "index_name": "nginx-logs", "index_rotation": "yyyy-MM-dd", "endpoint": "https://example.com", "type": "elasticsearch"}, "name": "Nginx logs", "query": "source:nginx"}, "type": "custom_destination"}} @@ -197,21 +197,21 @@ Feature: Logs Custom Destinations And the response "data.attributes.forward_tags_restriction_list" array contains value "host" And the response "data.attributes.forward_tags_restriction_list_type" is equal to "ALLOW_LIST" - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Delete a custom destination returns "Bad Request" response Given new "DeleteLogsCustomDestination" request And request contains "custom_destination_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Delete a custom destination returns "Not Found" response Given new "DeleteLogsCustomDestination" request And request contains "custom_destination_id" parameter with value "does-not-exist" When the request is sent Then the response status is 404 Not found - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Delete a custom destination returns "OK" response Given new "DeleteLogsCustomDestination" request And there is a valid "custom_destination" in the system @@ -219,21 +219,21 @@ Feature: Logs Custom Destinations When the request is sent Then the response status is 204 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get a custom destination returns "Bad Request" response Given new "GetLogsCustomDestination" request And request contains "custom_destination_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 400 Bad Request - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get a custom destination returns "Not Found" response Given new "GetLogsCustomDestination" request And request contains "custom_destination_id" parameter with value "does-not-exist" When the request is sent Then the response status is 404 Not found - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get a custom destination returns "OK" response Given new "GetLogsCustomDestination" request And there is a valid "custom_destination" in the system @@ -255,7 +255,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forward_tags_restriction_list" array contains value "host" And the response "data.attributes.forward_tags_restriction_list_type" is equal to "{{ custom_destination.data.attributes.forward_tags_restriction_list_type }}" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get all custom destinations returns "OK" response Given new "ListLogsCustomDestinations" request And there is a valid "custom_destination" in the system @@ -272,7 +272,7 @@ Feature: Logs Custom Destinations And the response "data" has item with field "attributes.forward_tags" with value false And the response "data" has item with field "attributes.forward_tags_restriction_list_type" with value "{{ custom_destination.data.attributes.forward_tags_restriction_list_type }}" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a Splunk custom destination with a null sourcetype returns "OK" response Given new "UpdateLogsCustomDestination" request And there is a valid "custom_destination_splunk_with_sourcetype" in the system @@ -287,7 +287,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forwarder_destination" does not have field "access_token" And the response "data.attributes.forwarder_destination.sourcetype" is equal to null - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a Splunk custom destination with a sourcetype returns "OK" response Given new "UpdateLogsCustomDestination" request And there is a valid "custom_destination_splunk" in the system @@ -302,7 +302,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forwarder_destination" does not have field "access_token" And the response "data.attributes.forwarder_destination.sourcetype" is equal to "new-sourcetype" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a Splunk custom destination's attributes preserves the absent sourcetype returns "OK" response Given new "UpdateLogsCustomDestination" request And there is a valid "custom_destination_splunk" in the system @@ -316,7 +316,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forwarder_destination.type" is equal to "splunk_hec" And the response "data.attributes.forwarder_destination" does not have field "sourcetype" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a Splunk custom destination's destination preserves the null sourcetype returns "OK" response Given new "UpdateLogsCustomDestination" request And there is a valid "custom_destination_splunk_with_null_sourcetype" in the system @@ -331,7 +331,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forwarder_destination" does not have field "access_token" And the response "data.attributes.forwarder_destination.sourcetype" is equal to null - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a Splunk custom destination's destination preserves the sourcetype returns "OK" response Given new "UpdateLogsCustomDestination" request And there is a valid "custom_destination_splunk_with_sourcetype" in the system @@ -346,7 +346,7 @@ Feature: Logs Custom Destinations And the response "data.attributes.forwarder_destination" does not have field "access_token" And the response "data.attributes.forwarder_destination.sourcetype" is equal to "my-sourcetype" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a custom destination returns "Bad Request" response Given new "UpdateLogsCustomDestination" request And there is a valid "custom_destination" in the system @@ -355,7 +355,7 @@ Feature: Logs Custom Destinations When the request is sent Then the response status is 400 Bad Request - @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a custom destination returns "Conflict" response Given new "UpdateLogsCustomDestination" request And request contains "custom_destination_id" parameter from "REPLACE.ME" @@ -363,7 +363,7 @@ Feature: Logs Custom Destinations When the request is sent Then the response status is 409 Conflict - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a custom destination returns "Not Found" response Given new "UpdateLogsCustomDestination" request And request contains "custom_destination_id" parameter with value "id-from-non-existing-custom-destination" @@ -371,7 +371,7 @@ Feature: Logs Custom Destinations When the request is sent Then the response status is 404 Not Found - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a custom destination returns "OK" response Given new "UpdateLogsCustomDestination" request And there is a valid "custom_destination" in the system diff --git a/tests/v2/features/logs_metrics.feature b/tests/v2/features/logs_metrics.feature index ac904962bc..31c072c3df 100644 --- a/tests/v2/features/logs_metrics.feature +++ b/tests/v2/features/logs_metrics.feature @@ -9,21 +9,21 @@ Feature: Logs Metrics And a valid "appKeyAuth" key in the system And an instance of "LogsMetrics" API - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a log-based metric returns "Bad Request" response Given new "CreateLogsMetric" request And body with value {"data": {"attributes": {"compute": {"aggregation_type": "distribution", "include_percentiles": true, "path": "@duration"}, "filter": {"query": "service:web* AND @http.status_code:[200 TO 299]"}, "group_by": [{"path": "@http.status_code", "tag_name": "status_code"}]}, "id": "logs.page.load.count", "type": "logs_metrics"}} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a log-based metric returns "Conflict" response Given new "CreateLogsMetric" request And body with value {"data": {"attributes": {"compute": {"aggregation_type": "distribution", "include_percentiles": true, "path": "@duration"}, "filter": {"query": "service:web* AND @http.status_code:[200 TO 299]"}, "group_by": [{"path": "@http.status_code", "tag_name": "status_code"}]}, "id": "logs.page.load.count", "type": "logs_metrics"}} When the request is sent Then the response status is 409 Conflict - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Create a log-based metric returns "OK" response Given new "CreateLogsMetric" request And body with value {"data": {"id": "{{ unique_alnum }}", "type": "logs_metrics", "attributes": {"compute": {"aggregation_type": "distribution", "include_percentiles": true, "path":"@duration"}}}} @@ -34,14 +34,14 @@ Feature: Logs Metrics And the response "data.attributes.compute.aggregation_type" is equal to "distribution" And the response "data.attributes.compute.include_percentiles" is equal to true - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Delete a log-based metric returns "Not Found" response Given new "DeleteLogsMetric" request And request contains "metric_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Delete a log-based metric returns "OK" response Given there is a valid "logs_metric" in the system And new "DeleteLogsMetric" request @@ -49,14 +49,14 @@ Feature: Logs Metrics When the request is sent Then the response status is 204 OK - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get a log-based metric returns "Not Found" response Given new "GetLogsMetric" request And request contains "metric_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get a log-based metric returns "OK" response Given there is a valid "logs_metric" in the system And new "GetLogsMetric" request @@ -65,7 +65,7 @@ Feature: Logs Metrics Then the response status is 200 OK And the response "data.attributes.filter.query" has the same value as "logs_metric.data.attributes.filter.query" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Get all log-based metrics returns "OK" response Given there is a valid "logs_metric" in the system And new "ListLogsMetrics" request @@ -73,7 +73,7 @@ Feature: Logs Metrics Then the response status is 200 OK And the response "data[0].type" is equal to "logs_metrics" - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a log-based metric returns "Bad Request" response Given new "UpdateLogsMetric" request And request contains "metric_id" parameter from "REPLACE.ME" @@ -81,7 +81,7 @@ Feature: Logs Metrics When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @generated @skip @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a log-based metric returns "Not Found" response Given new "UpdateLogsMetric" request And request contains "metric_id" parameter from "REPLACE.ME" @@ -89,7 +89,7 @@ Feature: Logs Metrics When the request is sent Then the response status is 404 Not Found - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a log-based metric returns "OK" response Given there is a valid "logs_metric" in the system And new "UpdateLogsMetric" request @@ -99,7 +99,7 @@ Feature: Logs Metrics Then the response status is 200 OK And the response "data.attributes.filter.query" is equal to "{{ logs_metric.data.attributes.filter.query }}-updated" - @team:ddoghq/logs-backend @team:ddoghq/logs-forwarding + @team:ddoghq/logs-backend @team:ddoghq/logs-federated-search @team:ddoghq/logs-routing Scenario: Update a log-based metric with include_percentiles field returns "OK" response Given there is a valid "logs_metric_percentile" in the system And new "UpdateLogsMetric" request