toepkerd-zz
commented
2 years ago Important Next Steps
- Add Frontend Component: currently, the framework only allows raw API request and response. A frontend component should be added that allows UI users to access the service. For example, a "Get Suggestions" button in the Monitor configuration page.
- Automated Actionability: suggestions given to the user propose a healing action, but expect the user to implement the healing action themselves. System should be upgraded that requires suggestions added to the framework to also implement an automatic healing action (similar to right-clicking a red underlined word in Microsoft Word, and letting it respell the word for you).
- Persisting Rules: currently, suggestions are given based on inspections of static, Monitor configuration snapshots. Suggestions should be upgraded to persist, and constantly monitor configurations for situations where a suggestion is warranted, rather than waiting for users to ask for them explicitly.
- Check Cluster/Index Metrics: upgrade suggestions to factor in cluster metrics such as spikes in cluster strain or JVM pressure, which would allow the suggestions' healing action to mitigate those spikes
- Generalizability and Pluggability: continue to refactor framework such that other services and plugins outside of OpenSearch Alerting can use it to provide user suggestions to their frameworks
- Miscellaneous TODOs: clean up miscellaneous TODOs in the current Suggestions Framework.
Is your feature request related to a problem? Users often get overwhelmed by the many monitor configuration options available to them. As such, they tend to create convoluted monitor configurations, which beat around the bush of what they actually seek, while also introducing unnecessary overhead.
What solution would you like? A suggestions framework will support suggestions that can be given to the user to help enhance their monitor configurations.