diff --git a/.apigentools-info b/.apigentools-info index 40cf01c9770..e6a4b38daa2 100644 --- a/.apigentools-info +++ b/.apigentools-info @@ -4,13 +4,13 @@ "spec_versions": { "v1": { "apigentools_version": "1.6.6", - "regenerated": "2024-11-25 19:59:41.593757", - "spec_repo_commit": "3c840607" + "regenerated": "2024-11-26 13:36:08.732682", + "spec_repo_commit": "cf1aa5ea" }, "v2": { "apigentools_version": "1.6.6", - "regenerated": "2024-11-25 19:59:41.612823", - "spec_repo_commit": "3c840607" + "regenerated": "2024-11-26 13:36:08.752592", + "spec_repo_commit": "cf1aa5ea" } } } \ No newline at end of file diff --git a/tests/scenarios/features/v1/logs_indexes.feature b/tests/scenarios/features/v1/logs_indexes.feature index f449dcbb519..d53c83665a1 100644 --- a/tests/scenarios/features/v1/logs_indexes.feature +++ b/tests/scenarios/features/v1/logs_indexes.feature @@ -10,47 +10,47 @@ Feature: Logs Indexes And a valid "appKeyAuth" key in the system And an instance of "LogsIndexes" API - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-core Scenario: Create an index returns "Invalid Parameter Error" response Given new "CreateLogsIndex" request And body with value {"daily_limit": 300000000, "daily_limit_reset": {"reset_time": "14:00", "reset_utc_offset": "+02:00"}, "daily_limit_warning_threshold_percentage": 70, "exclusion_filters": [{"filter": {"query": "*", "sample_rate": 1.0}, "name": "payment"}], "filter": {"query": "source:python"}, "name": "main", "num_flex_logs_retention_days": 360, "num_retention_days": 15} When the request is sent Then the response status is 400 Invalid Parameter Error - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-core Scenario: Create an index returns "OK" response Given new "CreateLogsIndex" request And body with value {"daily_limit": 300000000, "daily_limit_reset": {"reset_time": "14:00", "reset_utc_offset": "+02:00"}, "daily_limit_warning_threshold_percentage": 70, "exclusion_filters": [{"filter": {"query": "*", "sample_rate": 1.0}, "name": "payment"}], "filter": {"query": "source:python"}, "name": "main", "num_flex_logs_retention_days": 360, "num_retention_days": 15} When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-core Scenario: Get all indexes returns "OK" response Given new "ListLogIndexes" request When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-core Scenario: Get an index returns "Not Found" response Given new "GetLogsIndex" request And request contains "name" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-core Scenario: Get an index returns "OK" response Given new "GetLogsIndex" request And request contains "name" parameter from "REPLACE.ME" When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-core Scenario: Get indexes order returns "OK" response Given new "GetLogsIndexOrder" request When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-core Scenario: Update an index returns "Invalid Parameter Error" response Given new "UpdateLogsIndex" request And request contains "name" parameter from "REPLACE.ME" @@ -58,7 +58,7 @@ Feature: Logs Indexes When the request is sent Then the response status is 400 Invalid Parameter Error - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-core Scenario: Update an index returns "OK" response Given new "UpdateLogsIndex" request And request contains "name" parameter from "REPLACE.ME" @@ -66,14 +66,14 @@ Feature: Logs Indexes When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-core Scenario: Update indexes order returns "Bad Request" response Given new "UpdateLogsIndexOrder" request And body with value {"index_names": ["main", "payments", "web"]} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-core Scenario: Update indexes order returns "OK" response Given new "UpdateLogsIndexOrder" request And body with value {"index_names": ["main", "payments", "web"]} diff --git a/tests/scenarios/features/v2/logs.feature b/tests/scenarios/features/v2/logs.feature index 183db4a9d65..7763729af5f 100644 --- a/tests/scenarios/features/v2/logs.feature +++ b/tests/scenarios/features/v2/logs.feature @@ -105,7 +105,7 @@ Feature: Logs Then the response status is 200 OK And the response has 3 items - @integration-only @skip-terraform-config @skip-validation @team:DataDog/event-platform-intake @team:DataDog/logs-backend + @integration-only @skip-terraform-config @skip-validation @team:DataDog/event-platform-intake @team:DataDog/logs-backend @team:DataDog/logs-ingestion 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"}] @@ -113,7 +113,7 @@ Feature: Logs When the request is sent Then the response status is 202 Response from server (always 202 empty JSON). - @integration-only @skip-terraform-config @skip-validation @team:DataDog/event-platform-intake @team:DataDog/logs-backend + @integration-only @skip-terraform-config @skip-validation @team:DataDog/event-platform-intake @team:DataDog/logs-backend @team:DataDog/logs-ingestion 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"}] @@ -121,28 +121,28 @@ Feature: Logs When the request is sent Then the response status is 202 Request accepted for processing (always 202 empty JSON). - @generated @skip @team:DataDog/event-platform-intake @team:DataDog/logs-backend + @generated @skip @team:DataDog/event-platform-intake @team:DataDog/logs-backend @team:DataDog/logs-ingestion 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:DataDog/event-platform-intake @team:DataDog/logs-backend + @generated @skip @team:DataDog/event-platform-intake @team:DataDog/logs-backend @team:DataDog/logs-ingestion 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:DataDog/event-platform-intake @team:DataDog/logs-backend + @generated @skip @team:DataDog/event-platform-intake @team:DataDog/logs-backend @team:DataDog/logs-ingestion 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:DataDog/event-platform-intake @team:DataDog/logs-backend + @team:DataDog/event-platform-intake @team:DataDog/logs-backend @team:DataDog/logs-ingestion 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/scenarios/features/v2/logs_archives.feature b/tests/scenarios/features/v2/logs_archives.feature index a3c89c04277..ca158d28418 100644 --- a/tests/scenarios/features/v2/logs_archives.feature +++ b/tests/scenarios/features/v2/logs_archives.feature @@ -11,75 +11,75 @@ Feature: Logs Archives And a valid "appKeyAuth" key in the system And an instance of "LogsArchives" API - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Create an archive returns "Bad Request" response Given new "CreateLogsArchive" request And body with value {"data": {"attributes": {"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, "name": "Nginx Archive", "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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Create an archive returns "OK" response Given new "CreateLogsArchive" request And body with value {"data": {"attributes": {"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, "name": "Nginx Archive", "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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Grant role to an archive returns "Bad Request" response Given new "AddReadRoleToArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -87,7 +87,7 @@ Feature: Logs Archives When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Grant role to an archive returns "Not found" response Given new "AddReadRoleToArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -95,7 +95,7 @@ Feature: Logs Archives When the request is sent Then the response status is 404 Not found - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Grant role to an archive returns "OK" response Given new "AddReadRoleToArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -103,28 +103,28 @@ Feature: Logs Archives When the request is sent Then the response status is 204 OK - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Revoke role from an archive returns "Bad Request" response Given new "RemoveRoleFromArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -132,7 +132,7 @@ Feature: Logs Archives When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Revoke role from an archive returns "Not found" response Given new "RemoveRoleFromArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -140,7 +140,7 @@ Feature: Logs Archives When the request is sent Then the response status is 404 Not found - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Revoke role from an archive returns "OK" response Given new "RemoveRoleFromArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -148,7 +148,7 @@ Feature: Logs Archives When the request is sent Then the response status is 204 OK - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Update an archive returns "Bad Request" response Given new "UpdateLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -156,7 +156,7 @@ Feature: Logs Archives When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Update an archive returns "Not found" response Given new "UpdateLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -164,7 +164,7 @@ Feature: Logs Archives When the request is sent Then the response status is 404 Not found - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Update an archive returns "OK" response Given new "UpdateLogsArchive" request And request contains "archive_id" parameter from "REPLACE.ME" @@ -172,21 +172,21 @@ Feature: Logs Archives When the request is sent Then the response status is 200 OK - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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/scenarios/features/v2/logs_custom_destinations.feature b/tests/scenarios/features/v2/logs_custom_destinations.feature index 4fca0b6611f..4410834fdca 100644 --- a/tests/scenarios/features/v2/logs_custom_destinations.feature +++ b/tests/scenarios/features/v2/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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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"}} @@ -77,28 +77,28 @@ 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" - @skip-java @skip-python @skip-rust @skip-typescript @team:DataDog/logs-backend + @skip-java @skip-python @skip-rust @skip-typescript @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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"}} @@ -121,21 +121,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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Delete a custom destination returns "OK" response Given new "DeleteLogsCustomDestination" request And there is a valid "custom_destination" in the system @@ -143,21 +143,21 @@ Feature: Logs Custom Destinations When the request is sent Then the response status is 204 OK - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Get a custom destination returns "OK" response Given new "GetLogsCustomDestination" request And there is a valid "custom_destination" in the system @@ -179,7 +179,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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Get all custom destinations returns "OK" response Given new "ListLogsCustomDestinations" request And there is a valid "custom_destination" in the system @@ -196,7 +196,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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Update a custom destination returns "Bad Request" response Given new "UpdateLogsCustomDestination" request And there is a valid "custom_destination" in the system @@ -205,7 +205,7 @@ Feature: Logs Custom Destinations When the request is sent Then the response status is 400 Bad Request - @skip @team:DataDog/logs-backend + @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Update a custom destination returns "Conflict" response Given new "UpdateLogsCustomDestination" request And request contains "custom_destination_id" parameter from "REPLACE.ME" @@ -213,7 +213,7 @@ Feature: Logs Custom Destinations When the request is sent Then the response status is 409 Conflict - @team:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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" @@ -221,7 +221,7 @@ Feature: Logs Custom Destinations When the request is sent Then the response status is 404 Not Found - @team:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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/scenarios/features/v2/logs_metrics.feature b/tests/scenarios/features/v2/logs_metrics.feature index 080d8b83b58..a2ad8c77cb1 100644 --- a/tests/scenarios/features/v2/logs_metrics.feature +++ b/tests/scenarios/features/v2/logs_metrics.feature @@ -10,21 +10,21 @@ Feature: Logs Metrics And a valid "appKeyAuth" key in the system And an instance of "LogsMetrics" API - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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"}}}} @@ -35,14 +35,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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Delete a log-based metric returns "OK" response Given there is a valid "logs_metric" in the system And new "DeleteLogsMetric" request @@ -50,14 +50,14 @@ Feature: Logs Metrics When the request is sent Then the response status is 204 OK - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Get a log-based metric returns "OK" response Given there is a valid "logs_metric" in the system And new "GetLogsMetric" request @@ -66,7 +66,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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Get all log-based metrics returns "OK" response Given there is a valid "logs_metric" in the system And new "ListLogsMetrics" request @@ -74,7 +74,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:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Update a log-based metric returns "Bad Request" response Given new "UpdateLogsMetric" request And request contains "metric_id" parameter from "REPLACE.ME" @@ -82,7 +82,7 @@ Feature: Logs Metrics When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/logs-backend + @generated @skip @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Update a log-based metric returns "Not Found" response Given new "UpdateLogsMetric" request And request contains "metric_id" parameter from "REPLACE.ME" @@ -90,7 +90,7 @@ Feature: Logs Metrics When the request is sent Then the response status is 404 Not Found - @team:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding Scenario: Update a log-based metric returns "OK" response Given there is a valid "logs_metric" in the system And new "UpdateLogsMetric" request @@ -100,7 +100,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:DataDog/logs-backend + @team:DataDog/logs-backend @team:DataDog/logs-forwarding 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