search

opensearch-project / OpenSearch-Dashboards

📊 Open source visualization dashboards for OpenSearch.
https://opensearch.org/docs/latest/dashboards/index/
Apache License 2.0
1.68k stars 884 forks source link

[FEATURE] Best Practices in application #1622

Open kavilla opened 2 years ago

kavilla commented 2 years ago

Is your feature request related to a problem? Please describe. Origin: https://github.com/opensearch-project/OpenSearch-Dashboards/issues/1602

End users can end up doing something that could eventually lead to consequences. There are best practices guides but not a lot about index-patterns.

Describe the solution you'd like

Within application best practices that can do quick verification that can prevent end users that can alert the user before they end up in productivity pain. For example, if they create an index-pattern * but they have hundreds of indices with millions of documents within those said indices then * index-pattern doesn't provide real-time insight that can assist users. It also can be blocked by default settings to ensure the health of the machine that the application is being served on.

Describe alternatives you've considered

More documentation on index-patterns.

Additional context

n/a

kavilla commented 2 years ago

cc: @tmarkley, @ahopp, @opensearch-project/opensearch-ux.

ahopp commented 2 years ago

@kavilla I think this is a great idea - I'm not sure about the details in terms of configuring rules, but in general having the ability to guide (or warn) users a bit more paternalistically would be huge for any given admins ops. This would also be huge for downstream managed services or ISVs trying to decrease ops load cause by bad configuration or unintended configuration issues.

@KrooshalUX @kgcreative @btzeng Do you all have thoughts on general patterns for warnings we'd want to employee in these situations?