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

Manage Fleet system indices within Elasticsearch #70689

Merged
merged 11 commits into from
Apr 7, 2021

Conversation

jaymode
Copy link
Member

@jaymode jaymode commented Mar 22, 2021

This commit moves the management of seven system indices that are used
by Fleet to an Elasticsearch plugin. The mappings were taken largely
untouched from the Fleet server project, with the exception of adding
a _meta field with a version key to enable the system indices
infrastructure to manage these indices.

This commit moves the management of seven system indices that are used
by Fleet to an Elasticsearch plugin. The mappings were taken largely
untouched from the Fleet server project, with the exception of adding
a _meta field with a version key to enable the system indices
infrastructure to manage these indices.
@jaymode jaymode added >enhancement :Core/Infra/Core Core issues without another label v8.0.0 v7.13.0 labels Mar 22, 2021
@elasticmachine elasticmachine added the Team:Core/Infra Meta label for core/infra team label Mar 22, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@aleksmaus
Copy link
Member

Thank you!

@williamrandolph
Copy link
Contributor

@jaymode What are your thoughts on adding tests that verify the configuration and mappings of these system indices? On the one hand, we're adding some untested code here; on the other, this might be covered by the fleet tests already.

@jaymode
Copy link
Member Author

jaymode commented Mar 23, 2021

@williamrandolph I agree that we want to add a basic verification test and I am planning to add one. I wanted to get this up sooner rather than later for the fleet team to verify

@jaymode jaymode marked this pull request as draft March 23, 2021 14:40
@jaymode jaymode marked this pull request as ready for review April 1, 2021 15:54
Copy link
Contributor

@williamrandolph williamrandolph left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@aleksmaus
Copy link
Member

@jaymode we made some changes to mappings. will push the update later today.

@aleksmaus
Copy link
Member

Jay, I tested e2e with the agent. There are couple of follow up PRs in the Kibana and Fleet Server. Should be good to merge now.

@jaymode jaymode merged commit 0b0543f into elastic:master Apr 7, 2021
@jaymode jaymode deleted the fleet_system_indices branch April 7, 2021 14:34
jaymode added a commit that referenced this pull request Apr 7, 2021
This commit moves the management of seven system indices that are used
by Fleet to an Elasticsearch plugin. The mappings were taken largely
untouched from the Fleet server project, with the exception of adding
a _meta field with a version key to enable the system indices
infrastructure to manage these indices.

Co-authored-by: Aleksandr Maus <aleksandr.maus@elastic.co>
Backport of #70689
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >enhancement Team:Core/Infra Meta label for core/infra team v7.13.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants