-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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] Replace datasources
with inputs
when generating agent config
#69226
Merged
jen-huang
merged 6 commits into
elastic:master
from
jen-huang:ingest/flatten-agent-config
Jun 17, 2020
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
e67d5e7
Adjust agent config generation, change `datasources` to `inputs`
jen-huang fbcf50c
Add dataset.type
jen-huang e1bbbb5
Remove dead code
jen-huang e70c6d8
Revert "Add dataset.type"
jen-huang c54005a
Update endpoint policy test assertion
jen-huang 35085f0
Merge remote-tracking branch 'upstream/master' into ingest/flatten-ag…
jen-huang File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
190 changes: 0 additions & 190 deletions
190
x-pack/plugins/ingest_manager/common/services/datasource_to_agent_datasource.test.ts
This file was deleted.
Oops, something went wrong.
60 changes: 0 additions & 60 deletions
60
x-pack/plugins/ingest_manager/common/services/datasource_to_agent_datasource.ts
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I propose to move this under
meta
. All things that the agent does not directly understand but potentially should be used for logging, should go into ameta
object. I assume currently this has no effect on the agent side? @michalpristas ?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.
agent uses this to group inputs together and provide per output configurations as current implementation is one beat per output, we rely heavily on this field. if it's not present in the tree (input upwards) we assume default output
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 I think you talk about line 18 here with the output? I'm referring to line 19.
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.
oh ok, i think we dont use package