kris
February 15, 2023, 11:29pm
1
OpenSearch Community Meeting - 2023-0328 - Hope we see you all there!
Agenda:
Date: Tue, Mar 28, 2023
Time: 15:00 (UTC -8)
Event page
Meetup page
Meeting Link
Meeting ID: 849 0710 3587
Passcode: 969188
Would you like to present? Tag @kris @dtaivpp @nateynate and we’ll work to get you added to the agenda!
Feel free to comment on this agenda before the meeting if you want to add an item or have a question.
After the meeting, we will post the chat log and any meeting notes. We welcome you to keep the conversation going here on the forum.
========
By joining the OpenSearch Community Meeting, you grant OpenSearch, and our affiliates the right to record, film, photograph, and capture your voice and image during the OpenSearch Community Meeting (the “Recordings”). You grant to us an irrevocable, nonexclusive, perpetual, worldwide, royalty-free right and license to use, reproduce, modify, distribute, and translate, for any purpose, all or any part of the Recordings and Your Materials. For example, we may distribute Recordings or snippets of Recordings via our social media outlets.
kris
February 24, 2023, 1:31am
2
Leave a comment and let us know if you’re interested in presenting!
kris
March 29, 2023, 3:45pm
5
Chat log from the meeting:
14:59:05 From Kris Freedain to Waiting Room Participants:
Hello All - we’ll get going in just a minute
15:01:41 From Joel Martens to Everyone:
Hi everyone!
15:02:44 From Kris Freedain to Everyone:
Hello Everyone!!
15:03:11 From Jeff Huss to Everyone:
Hello!
15:03:49 From Patti Juric to Everyone:
Stand P16
15:04:02 From Kris Freedain to Everyone:
Haystack
Come and hear from the AWS OpenSearch team at Haystack US 2023
15:04:09 From Patti Juric to Everyone:
Observability Day T10
15:04:32 From Kris Freedain to Everyone:
KubeCon https://events.linuxfoundation.org/open-source-summit-north-america/
15:04:58 From Kris Freedain to Everyone:
OpenSearchCon 2023 coming!! (Watch for details)
15:15:50 From Aparna Sundar to Everyone:
If the community wants to talk to us, please sign up: Search application builders: How can OpenSearch better support you?
15:19:40 From Kris Freedain to Everyone:
link to the GH issue Mingshi is demoing: https://github.com/opensearch-project/OpenSearch/issues/1018
15:32:38 From Kris Freedain to Everyone:
Admin Panel UI
Looking for OpenSearch usability study candidates!
15:32:41 From Mikayla Thompson to Everyone:
Is there a github issue for the first (search) presentation?
15:32:52 From Kris Freedain to Everyone:
Notifications on index operation statuses RFC:
[RFC] Notification on index operation statuses · Issue #687 · opensearch-project/index-management-dashboards-plugin · GitHub
Component templates UI RFC:
[RFC] UX for Component Templates in Index Management Dashboards Plugin · Issue #688 · opensearch-project/index-management-dashboards-plugin · GitHub
OpenSearch Admin Usability Study:
https://forum.opensearch.org/t/looking-for-opensearch-usability-study-candidates/
15:48:14 From Monica Kugler to Everyone:
OpenSearch Admin Usability Study:
https://forum.opensearch.org/t/looking-for-opensearch-usability-study-candidates/
15:50:03 From Kris Freedain to Everyone:
Read the results! OpenSearch Project Q1 community survey results · OpenSearch
15:52:02 From Aparna Sundar to Everyone:
Click on the “take the survey” button on: https://opensearch.org/
15:53:49 From Mikayla Thompson to Everyone:
Is there a github issue for the first (search) presentation?
15:54:31 From David Tippett to Everyone:
Mikayla I don’t think there is a specific link as it’s covered over a lot of different issues. If there is something specific you’d like to know more about though you can shoot me a DM and I can send links
15:54:52 From Mikayla Thompson to Everyone:
Reacted to “Mikayla I don’t thin…” with
15:55:07 From Patti Juric to Everyone:
Awesome meeting!
15:55:09 From Kris Freedain to Everyone:
We’ll have events pages live this week for the Spark Integrations and Simple Schema work Joshua spoke about
15:55:24 From Kris Freedain to Everyone:
Thank you everyone!!
15:55:28 From Andriy Redko to Everyone:
Thank you guys!
15:56:36 From anan to Everyone:
Thank you~
15:57:46 From Joel Martens to Everyone:
Thanks everyone
kris
March 29, 2023, 4:02pm
6
We’ve just published the talk schedule for Haystack US 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
Notifications on index operation statuses RFC:
opened 07:16PM - 27 Mar 23 UTC
closed 09:29PM - 03 Aug 23 UTC
enhancement
## 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.
<img width="370" alt="image" src="https://user-images.githubusercontent.com/3692324/228043500-6eb14da0-5085-4858-8c3b-443becb82bac.png">
Users who set up notification will receive status updates through the defined channels. In this example receive via a slack channel:
<img width="589" alt="image" src="https://user-images.githubusercontent.com/3692324/228043689-dfbe0c95-df54-4158-a5c3-9c2adeef14f3.png">
## 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:
opened 12:57AM - 28 Mar 23 UTC
closed 02:19AM - 26 May 23 UTC
enhancement
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/
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.