Point in time in opensearch dashboards discussion

[bharath-techie]

Stack management creation flow

Here is an early design snapshot of stack management page for point in time

• We show list of PITs that are created within OpenSearch dashboards with multiple different data sources.
• We also show PITs ( which has 'time' instead of name ) that are created in backend which can be imported into a new dashboard saved object.

Design preview of create PIT side drawer

[bharath-techie]

@kavilla @KrooshalUX @kgcreative

Created this issue thread to discuss on open questions / ideas around point in time dashboards implementation.

[bharath-techie]

@kavilla

• As per the above design, since we show all PITs across all data sources - we need to make 'List all PITs' API call to all data sources and then paginate the results.
  • This could cause performance issues depending on the number of PITs in each cluster and number of data sources connected to the OS dashboards.
  • Do we have any mechanism ( like a coordinator ) which can query data from all data sources and give an aggregate result ? (or)
  • Is there any other mechanism to query from multiple data sources (or) any feature which does this to take notes from

@KrooshalUX @kgcreative

We can also scope the functionality in initial release to tackle some of these issues, so would like to know your thoughts on the following :

• Should we scope initial release with support of PITs only for local data source ? ( or )
• Should we enable filter based on 'data source' by default for point in time ?

[joshuarrrr]

Also tagging @kristenTian and @zhongnansu here who may have some perspective to share from working on the multiple data source feature.

[shanilpa]

Hey everyone, here are some updates to the Stack Management UI. This is not a final version - so please provide feedback

@KrooshalUX @kgcreative @bharath-techie

UI 01: Stack Management

UI 01.1: PIT Landing Page

UI 01.2: PIT expanded Data Source Filter

UI 01.3: Data source tooltip on hover

UI 01.4: Quick-Actions on hover

UI 01.5: Actions pop-over on click

What was updated:

1. A refresh button and time since last update was added to the top right to allow the user to refresh the table to get the most accurate time estimate but also give them a reference point for the expiration time.
2. Tabs for "expiring soon" and "expired" were removed as the table offers sorting functionality to allow the user to do this.
3. A searchable multi-select data source filter (UI 01.2 above) was added to allow users to scope down the options represented in the table below.
4. The cluster name + index pattern was added to the data source column. Clicking the Index Pattern takes the user to the Index Pattern Object Detail Page in Stack Management. Backend PIT's are not clickable.
5. Estimated time remaining was simplified visually to follow a similar structure and shorten the width of text to allow for more space for other columns. All time should be an approximate since it is dependent on the refresh time. For PIT's set to expire in 60+ minutes we just offer the hour estimate no minutes.
6. If the data source name is too long a user can hover over it which reveals the full name in a tooltip. (UI 01.3 above)
7. When a user hovers over the Actions menu they are presented with 2 quick actions. For a PIT created in OSD it allows them to create from template, and extend time. For a backend PIT they only have the edit option. (UI 01.4 above)
8. When a user clicks the action menu they are presented with a pop-over that lists all the actions they can perform. For backend PIT's they can only edit

Questions:

1. What might a Data source path look like? Can someone share some examples - I might have a better UX implementation depending on what these paths look like.
2. This still feels like a huge performance demand - even with the filter? Is it possible to do a call for data in the first 3 and last 3 pages in pagination to reduce the amount of queries being made?