Skip to content

Replace logs-forwarding and logs-ingestion team ownership #4183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dd-octo-sts wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Replace logs-forwarding and logs-ingestion team ownership #4183

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions tests/v2/features/logs.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,15 +128,15 @@ 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"}]
And request contains "Content-Encoding" parameter with value "deflate"
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"}]
Expand All @@ -145,15 +145,15 @@ 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"}]
And request contains "Content-Encoding" parameter with value "gzip"
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"}]
Expand All @@ -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"}]
Expand Down
12 changes: 6 additions & 6 deletions tests/v2/features/logs_archive_searches.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,47 +16,47 @@ 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
And body with value {"data": {"attributes": {"archive_id": "mhmyYmyLTOaFYKvhNadu1w", "description": "Investigating the checkout latency spike.", "from": "2026-01-01T00:00:00Z", "name": "checkout-latency-investigation", "query": "service:checkout status:error", "rehydration": {"max_rehydrated_events": 1000000, "retention_days": 15, "tier": "standard"}, "to": "2026-01-02T00:00:00Z"}, "type": "archive_search"}}
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
And body with value {"data": {"attributes": {"archive_id": "mhmyYmyLTOaFYKvhNadu1w", "description": "Investigating the checkout latency spike.", "from": "2026-01-01T00:00:00Z", "name": "checkout-latency-investigation", "query": "service:checkout status:error", "rehydration": {"max_rehydrated_events": 1000000, "retention_days": 15, "tier": "standard"}, "to": "2026-01-02T00:00:00Z"}, "type": "archive_search"}}
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
And body with value {"data": {"attributes": {"archive_id": "mhmyYmyLTOaFYKvhNadu1w", "description": "Investigating the checkout latency spike.", "from": "2026-01-01T00:00:00Z", "name": "checkout-latency-investigation", "query": "service:checkout status:error", "rehydration": {"max_rehydrated_events": 1000000, "retention_days": 15, "tier": "standard"}, "to": "2026-01-02T00:00:00Z"}, "type": "archive_search"}}
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
And request contains "archive_search_id" parameter from "REPLACE.ME"
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
And request contains "archive_search_id" parameter from "REPLACE.ME"
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
Expand Down
Loading
Loading