-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Ingest Manager] Move to datastream instead of dataset #20420
[Ingest Manager] Move to datastream instead of dataset #20420
Conversation
abc1960
to
f4f3527
Compare
Pinging @elastic/ingest-management (Team:Ingest Management) |
Tested OK with elastic/kibana#74414 tested basic scenario, assigning custom config |
Also tested on my end and looks like it works as expected. I hope you mean |
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.
Looks like you got all of them!
[Ingest Manager] Move to datastream instead of dataset (elastic#20420)
[Ingest Manager] Move to datastream instead of dataset (elastic#20420)
[Ingest Manager] Move to datastream instead of dataset (elastic#20420)
elastic#20482) [Ingest Manager] Move to datastream instead of dataset (elastic#20420)
What does this PR do?
This PR moves away from
dataset.*
fields and usesdatastream.*
fields instead.It also requires fleet to send configuration with new fields in inputs definition.
This PR includes config change on top of event decorators.
Why is it important?
elastic/integrations#213
elastic/elasticsearch#60592
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.