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

provide mapping as artefacts for use with component templates #21051

Closed
jaakoob opened this issue Sep 10, 2020 · 10 comments
Closed

provide mapping as artefacts for use with component templates #21051

jaakoob opened this issue Sep 10, 2020 · 10 comments
Labels

Comments

@jaakoob
Copy link

jaakoob commented Sep 10, 2020

Describe the enhancement:

It would be nice if the mappings for the beats fields would be published as artefacts for use with content templates.

Describe a specific use case for the enhancement or feature:

No Elastic Beat is directly connected to Logstash and a Index Pattern which differs from the standard Beat Index Pattern/ ILM Policys is used. It should be possible to load an appropriate mapping for the used beats as component template. Therefore the mappings are required to be released as artefacts.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Sep 10, 2020
@andresrc andresrc added Team:Ingest Management Team:Services (Deprecated) Label for the former Integrations-Services team labels Sep 11, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ingest-management (Team:Ingest Management)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-services (Team:Services)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Sep 11, 2020
@ruflin
Copy link
Contributor

ruflin commented Sep 14, 2020

@jaakoob I wonder if the ingest manager will solve your problem here: https://www.elastic.co/blog/introducing-elastic-agent-and-ingest-manager The assets are all loaded centrally through Kibana instead of from the Beats. Also the indexing strategy changed quite a bit which might help you too.

@andresrc andresrc removed the Team:Services (Deprecated) Label for the former Integrations-Services team label Sep 14, 2020
@jaakoob
Copy link
Author

jaakoob commented Sep 15, 2020

I use an extended ECS so ingest manager would have to provide component templates so that I can use the beat fields in combination with my extended ECS. I am also not interested in dashboard and visualization templates, so ingest manger can´t do much for me.

@ruflin
Copy link
Contributor

ruflin commented Sep 15, 2020

Having a package with ECS components and parts is a discussion we had in an other issue, but couldn't find it. I know @webmat was thinking about this too.

@webmat
Copy link
Contributor

webmat commented Sep 22, 2020

Yeah step 1 of before working on an ECS package is literally just to produce new artifacts in the ECS project (tracked here elastic/ecs#961), but @jaakoob has already chimed in over there :-)

@honzakral
Copy link

Getting artefacts based on ECS would be ideal, but as an interim solution it would be great to have the settings and mappings installed as component templates with the index template consisting primarily of just the list of those components. That way users could reuse the mappings/settings without having to modify the provided template which requires maintenance with every new release. Previously this was easily solved by creating another template that would be merged with the default one but with component template this now requires essentially copy/pasting the entire template.

This is also the case for templates managed by the elastic agent.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 27, 2021
@jsoriano jsoriano added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Oct 29, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Oct 29, 2021
@jlind23 jlind23 added Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team and removed Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team labels Mar 7, 2022
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic
Copy link

botelastic bot commented Mar 7, 2023

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Mar 7, 2023
@botelastic botelastic bot closed this as completed Sep 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants