-
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] Moved from stream to dataset #18967
Changes from 2 commits
87d0d57
e149f3b
89e02ce
6aff6bf
a114c26
0c21420
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,7 +8,7 @@ filebeat: | |
index: logs-generic-default | ||
processors: | ||
- add_fields: | ||
target: "stream" | ||
target: "dataset" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I tested this and it does not work as expected. The result is:
But it should be
I think the reason is on line 14 where it still states There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. oh right |
||
fields: | ||
type: logs | ||
dataset: generic | ||
|
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.
There a small thing missing here:
dataset.dataset
need to be changed fordataset.name
, this will create these fields:@michalpristas @ruflin The field in the agent configuration will also need to changes? Meaning we will need to adjust the index name generation.
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.
in configuration i would expect this
to become this
is that correct?
but this feels weird as you can have
i dont recall if we agreed to handle configuration change as a separate pack of PRs or the same with this one @ruflin
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.
@michalpristas Please handle config changes as a separate PR as it also has effects in Kibana. I plan to open an issue for this. These config changes we should directly in combination with the potential removal of datasources.