Skip to content

Add end-to-end acknowledgements to Observability Pipelines #4938

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
api-clients-generation-pipeline wants to merge 1 commit into
base: master
Choose a base branch
from
+15 −0
Open

Add end-to-end acknowledgements to Observability Pipelines #4938

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
5 changes: 5 additions & 0 deletions .generator/schemas/v2/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73676,6 +73676,11 @@ components:
items:
$ref: '#/components/schemas/ObservabilityPipelineConfigDestinationItem'
type: array
end_to_end_acknowledgements:
description: |-
Enables end-to-end event delivery confirmation. Without a disk buffer, sources acknowledge events after delivery to all final destinations; when a disk buffer provides the acknowledgment boundary, they acknowledge after durable persistence.
Defaults to `false` when omitted. Requires Observability Pipelines Worker 2.14 or later. All configured sources must support this behavior.
type: boolean
pipeline_type:
$ref: '#/components/schemas/ObservabilityPipelineConfigPipelineType'
processor_groups:
Expand Down
1 change: 1 addition & 0 deletions features/v2/observability_pipelines.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ Feature: Observability Pipelines
And the response "data.attributes.config.sources" has length 1
And the response "data.attributes.config.processor_groups" has length 1
And the response "data.attributes.config.destinations" has length 1
And the response "data.attributes.config" does not have field "end_to_end_acknowledgements"

@team:DataDog/observability-pipelines
Scenario: Create a pipeline with dedupe processor with cache returns "OK" response
Expand Down
9 changes: 9 additions & 0 deletions packages/datadog-api-client-v2/models/ObservabilityPipelineConfig.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,11 @@ export class ObservabilityPipelineConfig {
* A list of destination components where processed logs are sent.
*/
"destinations": Array<ObservabilityPipelineConfigDestinationItem>;
/**
* Enables end-to-end event delivery confirmation. Without a disk buffer, sources acknowledge events after delivery to all final destinations; when a disk buffer provides the acknowledgment boundary, they acknowledge after durable persistence.
* Defaults to `false` when omitted. Requires Observability Pipelines Worker 2.14 or later. All configured sources must support this behavior.
*/
"endToEndAcknowledgements"?: boolean;
/**
* The type of data being ingested. Defaults to `logs` if not specified.
*/
Expand Down Expand Up @@ -66,6 +71,10 @@ export class ObservabilityPipelineConfig {
type: "Array<ObservabilityPipelineConfigDestinationItem>",
required: true,
},
endToEndAcknowledgements: {
baseName: "end_to_end_acknowledgements",
type: "boolean",
},
pipelineType: {
baseName: "pipeline_type",
type: "ObservabilityPipelineConfigPipelineType",
Expand Down
Loading