-
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
provide mapping as artefacts for use with component templates #21051
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
Pinging @elastic/integrations-services (Team:Services) |
@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. |
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. |
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. |
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 :-) |
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. |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Hi! We're labeling this issue as |
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.
The text was updated successfully, but these errors were encountered: