Skip to content

Expose use_legacy_search_syntax flag in the Observability Pipelines API #34155

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

Merged
api-clients-generation-pipeline merged 1 commit into from
Jan 28, 2026
Merged

Expose use_legacy_search_syntax flag in the Observability Pipelines API #34155

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
35 changes: 21 additions & 14 deletions content/en/api/v2/observability-pipelines/examples.json
View file
Open in desktop

Large diffs are not rendered by default.

12 changes: 12 additions & 0 deletions data/api/v2/full_spec.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38150,6 +38150,18 @@ components:
items:
$ref: '#/components/schemas/ObservabilityPipelineConfigSourceItem'
type: array
use_legacy_search_syntax:
description: 'Set to `true` to continue using the legacy search syntax while
migrating filter queries. After migrating all queries to the new syntax,
set to `false`.

The legacy syntax is deprecated and will eventually be removed.

Requires Observability Pipelines Worker 2.11 or later.

See [Upgrade Your Filter Queries to the New Search Syntax](https://docs.datadoghq.com/observability_pipelines/guide/upgrade_your_filter_queries_to_the_new_search_syntax/)
for more information.'
type: boolean
required:
- sources
- destinations
Expand Down
Loading