-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ML][Maps] Add show-in-maps button to ML UX #69064
Comments
Pinging @elastic/kibana-gis (Team:Geo) |
Pinging @elastic/ml-ui (:ml) |
This ended up taking a slightly different direction: As a first step, maps are now (7.12 and up) embedded inside the anomaly-explorer application, to show maps with anomaly data: #88416 -- Next steps: Investigate further, on how to add this hotlinking experience between ML-Maps. This will require Maps to allow interfacing with data which are not index patterns, in this case the internal ml-anomaly-index, which has a custom API.
|
update: created #90497 as a POC on how ML-plugin could register a new source-type with the Maps-plugin. to be discussed. Will add more detailed description in that PR. |
Closed by #128697 |
When anomalies have a spatial component (e.g. geo_point or geo_shape), consider the possibility of adding a button to the job results (and potentially datatransform). Pressing this button would open the Maps app with a map of the ML-job (with separate layers showing anomalies, reference values, ...)
It behave similar to the "visualize" buttons in Discover when geo_point or geo_shape fields are detected.
This would automate a common manual workflow.
There were some lower-level efforts that likely make this possible, specifically the addition of multi-layer templates: #67544
Similarly, Maps could add a "ML" layer-wizard in Maps itself. If Maps detects an ML-index pattern with geo-fields, Maps can provide a layer-template shortcut (similar to Observability or Security layers).
See also #59659
cc @benwtrent @nreese @jsanz @alvarezmelissa87
The text was updated successfully, but these errors were encountered: