Skip to content

Putting the ingest otel processor behind the logs stream feature flag #129667

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.

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
merged 1 commit into from
Jun 18, 2025

Conversation

masseyke
Copy link
Member

This puts the ingest otel processor behind the logs stream feature flag. The processor is still available in snapshots, or in releases if -Des.logs_stream_feature_flag_enabled=true is passed in on server startup.

@masseyke masseyke added >non-issue :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP v8.19.0 v9.1.0 labels Jun 18, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@elasticsearchmachine elasticsearchmachine added the Team:Data Management Meta label for data/management team label Jun 18, 2025
@masseyke masseyke added the auto-backport Automatically create backport pull requests when merged label Jun 18, 2025
@masseyke masseyke requested a review from jbaiera June 18, 2025 20:27
@masseyke
Copy link
Member Author

masseyke commented Jun 18, 2025

An example of testing this locally in non-snapshot mode:

./gradlew ":modules:ingest-otel:yamlRestTest" -Dbuild.snapshot=false -Dtests.jvm.argline="-Dbuild.snapshot=false" -Dlicense.key=x-pack/license-tools/src/test/resources/public.key

Copy link
Member

@dakrone dakrone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM assuming CI is happy

@masseyke masseyke merged commit 92e4244 into elastic:main Jun 18, 2025
26 of 27 checks passed
@masseyke masseyke deleted the ingest-otel-processor-feature-flag branch June 18, 2025 22:40
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.19 Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 129667

@masseyke
Copy link
Member Author

💚 All backports created successfully

Status Branch Result
8.19

Questions ?

Please refer to the Backport tool documentation

masseyke added a commit to masseyke/elasticsearch that referenced this pull request Jun 20, 2025
…elastic#129667)

(cherry picked from commit 92e4244)

# Conflicts:
#	test/test-clusters/src/main/java/org/elasticsearch/test/cluster/FeatureFlag.java
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged backport pending :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >non-issue Team:Data Management Meta label for data/management team v8.19.0 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants