<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ### Problem to solve As the capabilities of Elasticsearch have grown in GitLab, we've continued to expand settings and options for configuration. These new settings have grown beyond their existing location in `Settings -> Integrations -> Elasticsearch` and a new Elasticsearch Administration area is needed. ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> GitLab Instance Administrators managing Elasticsearch ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> New settings are being introduced to Elasticsearch within future versions of GitLab to support [batch sizing](https://gitlab.com/gitlab-org/gitlab-ee/issues/12375), multiple index versions to support [zero-downtime Elasticsearch re-indexing](https://gitlab.com/gitlab-org/gitlab-ee/issues/10156) and more in continued support of improving Self-Managed and getting [Elasticsearch across more of GitLab.com](https://gitlab.com/groups/gitlab-org/-/epics/153). Some of these settings require more details and index specific information to be properly configured. It's also not currently possible to see the [status of the Index](https://gitlab.com/gitlab-org/gitlab-ee/issues/2973) leaving Elasticsearch administrators wondering if the process is working and checking in other data sources. ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> A redesign and information up-leveling of Elasticsearch to support these new configuration options and workflow for managing Elasticsearch. Userflow: https://app.mural.co/invitation/mural/gitlab2474/1562843823190?sender=mvanremmerden4805&key=0a7246e6-a62d-49dd-90d5-a671e06d0ea2 Prototype: https://sketch.cloud/s/qw9WV/a/78rGp8/play Screenshots: https://sketch.cloud/s/qw9WV and in the Designs tab. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> Elasticsearch administration is only available to Instance Administrators. ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> All Elasticsearch administration documentation will need to be updated to reflect the new settings and options available for configuration. ### Links / references