-
Notifications
You must be signed in to change notification settings - Fork 525
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
Move setting of data_stream fields to processor #5717
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
/test |
This pull request is now in conflicts. Could you fix it @axw? 🙏
|
Moving this back into draft while I fix conflicts will do that in a follow up |
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.
Great to get rid of a lot of the *transformConfig
dependencies when transforming the events to beat events.
(cherry picked from commit 29cfed3) # Conflicts: # beater/beater.go # model/apmevent.go # model/error_test.go # model/metricset.go # model/metricset_test.go # model/profile.go # model/profile_test.go # model/span_test.go # model/transaction.go # model/transaction_test.go # transform/transform.go
@Mergifyio backport 7.x |
Command
|
Motivation/summary
Move the logic associated with setting data_stream fields out of model, into a model processor. Most of our tests will not run the model processor, hence why the data_stream fields disappear from approvals. Importantly, the TestFleetIntegration system test's approval file (which doesn't and shouldn't show up in the diff) retains the fields.
Checklist
- [ ] Update CHANGELOG.asciidoc- [ ] Documentation has been updatedHow to test these changes
Non-functional change.
Related issues
#4410
#4120
#3565