Open
Description
openedon May 16, 2024
As a part of the work to consolidate our Trained Models view and remove Alerts and Insights > Machine Learning, we need to include ML jobs within Saved Objects management.
Some considerations:
- Are we confident that grouping ML jobs along with other Kibana Saved Objects makes sense to users?
- Jobs would have limited options compared to other Saved Objects.
-
- This is not unique though, as there are other SO with specific actions available to them.
-
- For instance, rules cannot be shared or copied across spaces, but still exist here. Maps, can only be copied
- We already account for objects that cannot be deleted: Tooltip on delete button show
Selected objects can't be deleted because they are either Elastic managed or hidden objects
ML Jobs space synchronization
Type | Space visibility |
---|---|
DFA and Anomaly Jobs | Available in current space when created, need to be shared to other/all spaces |
ELSER and E5 Models | Available to all spaces initially |
Trained Model installed through Eland or API | Available to all spaces initially, however…Sync notes |
- Hourly sync runs to make Trained Models available in all spaces
- If I want it available in the current space before that sync, I need to click ‘Synchronize saved objects’
- This does not update all spaces
Open questions:
We also have the ‘Refresh’ option on the Saved Objects. We could put synchronize next to it or b) call the sync action on refresh or c) have sync be optional on refresh
Could we provide an inspect and relationship view for ML objects?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment