Skip to content
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

Import mapping definitions from the "Agent Common Schema" #1017

Open
jsoriano opened this issue Oct 26, 2022 · 0 comments
Open

Import mapping definitions from the "Agent Common Schema" #1017

jsoriano opened this issue Oct 26, 2022 · 0 comments
Labels
Team:Ecosystem Label for the Packages Ecosystem team

Comments

@jsoriano
Copy link
Member

This is blocked by the definition of elastic/package-spec#441

Allow to import mappings from the "Agent Common Schema" into packages on build time.

This feature would work similarly to the import of external fields, but would import sets of fields from the schemas defined in elastic/package-spec#441.

I would propose to:

  • Import these definitions into the current fields directories, in new files, so current versions of Fleet would benefit of definitions included in packages following this approach.
  • It should be also a well-known name, so Fleet could eventually take over this behaviour if (TBD issue) is implemented.

So for example the mappings for add_host_metadata could be imported in fields/imported_beats_add_host_metadata.yml, and eventually Fleet can know if it should include these fields or not depending on the used policy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Ecosystem Label for the Packages Ecosystem team
Projects
None yet
Development

No branches or pull requests

2 participants