# OpenSearch Community Meeting - 2023-0328 **URL:** \ **Category:** Community\ **Tags:** community-meeting\ **Created:** [February 15, 2023, 11:29pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0328/12531 "2023-02-15T23:29:25Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![kris](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/kris/32/2208_2.png) [@kris](https://forum.opensearch.org/u/kris)\ **Post date:** [March 29, 2023, 4:02pm UTC](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0328/12531/6 "2023-03-29T16:02:31Z")
![Slide1](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/8/8a011630ce4490f64758f7fad830b88681e0697d.png) ![Slide4](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/f/f40c879ca1fec61156c382b6a41a13ef5525f77c.png) > [@Come and hear from the AWS OpenSearch team at Haystack US 2023](https://forum.opensearch.org/t/come-and-hear-from-the-aws-opensearch-team-at-haystack-us-2023/13552): > > We’ve just published the [talk schedule for Haystack US 2023](https://haystackconf.com/2023/) and I’m pleased to say Stavros and David will be talking about " Talking to Non-Searchers about Search Relevance" - hope you can join us at the search relevance conference! Early bird tickets are available now until March 31st and there’s also a remote option. Best Charlie ![Slide5](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/f/f5c2f2cef1a0eb6ff304217533184046bee6083b.png) ![Screen Shot 2023-03-29 at 8.59.54 AM](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/c/cfc7cecabb08bd4c4d7338f8beb6f1d0f6413864.png) ![Screen Shot 2023-03-29 at 9.00.03 AM](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/0/08bc7844c5599452a31b8605913092f09b18ba30.jpeg) ![Screen Shot 2023-03-29 at 9.00.13 AM](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/e/e159a3d3a755c7ddb9ac57c947043d8bdfccfe7d.jpeg) ![Screen Shot 2023-03-29 at 9.00.23 AM](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/6/6f31570e9ddc3b1885c88b55ba309dfa58fcc4dc.png) ![Screen Shot 2023-03-29 at 9.00.33 AM](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/b/b0f08128962ce7ad2c712a38b52070fa654d9cf4.png) ![Screen Shot 2023-03-29 at 9.00.42 AM](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/9/98e269ab057e847757e1ce918ad11e6b6b9a4c99.png) ![Screen Shot 2023-03-29 at 9.00.50 AM](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/3/315a6d11be9ab4451023752bdc5b756e21974584.png) ![Screen Shot 2023-03-29 at 9.00.59 AM](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/b/b807276f789866db37384b303781c0bb6743130d.png) ![Screen Shot 2023-03-29 at 9.01.08 AM](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/3/3378efc6b313618f45dca86dd891a75c6785aadf.png) ![Slide1](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/7/733463bfa6a139e220b567ad9125c71f7576f395.png) ![Slide2](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/8/8d9779af9b9e8802f1ae456c86669cc3bd0dbaf7.png) ![Slide3](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/e/e70c8faa9d641b93710600479b2ae5fdc7799670.png) ![Slide4](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/2/23414e8ce6bcb2ce07edf1dfbd709b8ab55353c6.png) ![Slide5](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/e/e2d812ffaf3e28b198af41d2eea98728dbdfebd3.png) ![Slide6](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/a/a79d35bbd1da9a1dcd42d896ca658a96807e7ad4.png) ![Slide7](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/4/43294d1f36fd17778bdb944482410b51b88e07b4.png) ![Slide1](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/3/32cdacf4e560be27a3566fcc9120c52ddb5d1ee7.png) ![Slide2](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/a/a690c5f75f3859f99456a9ab1a5bdcd8c22b29b3.png) ![Slide3](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/1/110f05f0c939e579789f31d194494b46c71a1df6.png) ![Slide4](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/7/76ac300ba012c7bb0a3d5ffe046553c26937ddf0.png) Notifications on index operation statuses RFC: > > > \## Problem statement ## > Index operations may take tens of minutes or even hours… to complete (e.g. reindex, split). However, there is no way for admins to get informed on status or the completion of long running operations. Admins also do not currently have any visibility to track their jobs and get notified when an operation is complete through the channel of their choice. Currently they have to be actively on Dashboards UI to see updates via toast notification banners, but others won’t be able to see the toast because they are not in the same UI session. Another workaround is to manually run different APIs to check the operation status until it’s done, which is not convenient at all. We plan to enhance this experience through this notification feature. > > \## What are you proposing? ## > We’d like to increase visibility on monitoring long-running index operations through notifications. Admins can get notified through their email or slack channels (channels defined in Notification framework) on upcoming operations that have been completed or failed. In addition, admins can configure these notifications globally, so they will not need to manually configure notifications for every single operation. Users can also add run time notifications when submit those long-running index operations. For this feature, we will be focusing on operations that are long running and not notify users for create/read/update where it can be done quickly and currently has the toast functionality. > > This issue focuses on the user experience of configuring notifications for index operations in Dashboards. It's based on this \[API propsal issue\](https://github.com/opensearch-project/index-management/issues/700). > > \### What is the user experience going to be? ### > \#### Global notifications on index operation statuses #### > Admin can also define global notification settings for long running operations. Admins can go to “Index management” section of Dashboards to configure global notifications for index operations. Admins can then choose who to get notified, so users don’t need to configure notification every time they trigger an operation. > !\[image\](https://user-images.githubusercontent.com/3692324/236956742-65768bcd-3af2-447b-b944-dadf4511121f.png) > > > \#### View notification settings while starting shrink or other index operations #### > If the notification settings is defined globally, users who trigger an operation (e.g. Shrink index flow) will see the notification channels selected for them. Users will have the option to add additional notification channels for this workflow, but users won’t be able to remove the channels defined globally by the admin. > !\[image\](https://user-images.githubusercontent.com/3692324/228043213-143117c5-1716-4728-a5c3-52fbc1263242.png) > > If there are not global notification settings defined, users can opt-in to get notified on this operation’s status (Failed/ completed). Users can select who to get notified from a list of channels defined in notification framework. The notification settings will only be for this particular operation. > !\[image\](https://user-images.githubusercontent.com/3692324/228043315-204662e9-1b3d-4f7f-be72-6ab523fc6ed4.png) > > \#### Notified on operation statuses #### > Users who triggered operations within Dashboards will be informed of the operation’s status (Failed/completed) through in-app toast messages. > \image > > Users who set up notification will receive status updates through the defined channels. In this example receive via a slack channel: > \image > > \## Your feedback is needed! ## > Any comments about the overall direction are welcome. Some specific questions: > > \* When managing and administrating OpenSearch, what are your use cases where notification would be useful? > \* What statuses do you find useful to get notified? > > Thank you! Component templates UI RFC: > > > This is a RFC issue for UX work related to \[component template API\](https://open…search.org/docs/latest/im-plugin/index-templates/#composable-index-templates) and using the components to create index templates in OpenSearch Dashboards UI. > > \## Context ## > To help reducing the number of templates, users can create component templates as reusable building blocks of index templates. In this proposal, users will be able to use the Index Management UI to create component templates and assemble them into index templates. > > \## User flows ## > The scope of this UX work focuses on these high level user flows in Index Management UI: > > \* Create / Manage / Delete Component templates > \* Associate component templates when creating an Index template > \* View and configure Index template > > \## Your feedback is needed! ## > Any comments about the overall direction are welcome. Some specific questions: > > \- What pain points do you have when defining configurations for your indexes? > \- How are you using index templates and component templates? > \- Have a use case that is not covered in this issue? Feel free to share them! > > Thank you! OpenSearch Admin Usability Study: [https://forum.opensearch.org/t/looking-for-opensearch-usability-study-candidates/](https://forum.opensearch.org/t/looking-for-opensearch-usability-study-candidates/) > **[OpenSearch Project Q1 community survey results](https://opensearch.org/blog/q1-survey-results/)** > > OpenSearch is a community-driven, Apache 2.0-licensed open source search and analytics suite that makes it easy to ingest, search, visualize, and analyze data. ![Slide6](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/2/2a95e98ab3e7ff4cc95e13cc6acefc2220c54da9.png) ![Slide9](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/a/a3872820de2e6c03ae76d82b4c284e37fd002438.png) --- _[View the full topic](https://forum.opensearch.org/t/opensearch-community-meeting-2023-0328/12531)._