- 
                Notifications
    
You must be signed in to change notification settings  - Fork 25.6k
 
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
Putting the ingest otel processor behind the logs stream feature flag #129667
Conversation
| 
           Pinging @elastic/es-data-management (Team:Data Management)  | 
    
| 
           An example of testing this locally in non-snapshot mode:  | 
    
There was a problem hiding this 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
          💔 Backport failed
 You can use sqren/backport to manually backport by running   | 
    
          💚 All backports created successfully
 Questions ?Please refer to the Backport tool documentation  | 
    
…elastic#129667) (cherry picked from commit 92e4244) # Conflicts: # test/test-clusters/src/main/java/org/elasticsearch/test/cluster/FeatureFlag.java
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=trueis passed in on server startup.