[ML] Add Lens and Discover integration to index based Data Visualizer#89471
[ML] Add Lens and Discover integration to index based Data Visualizer#89471qn895 merged 22 commits intoelastic:masterfrom
Conversation
|
Pinging @elastic/ml-ui (:ml) |
pheyos
left a comment
There was a problem hiding this comment.
Good to have functional tests as part of this PR! 🎉 Left a few comments.
Additionally, we might want to add the new features to the permission tests and would also like to validate some discover and lens page content. I'll take a closer look and report back with more details.
…chart, add boolean chart
…chart, add boolean chart
pheyos
left a comment
There was a problem hiding this comment.
I've noticed that when I open Discover in the same browser tab, it correctly applies the selected time range. But opening the Discover link in a new browser tab falls back to Last 15 minutes. Not sure if this can be fixed on our side.
peteharverson
left a comment
There was a problem hiding this comment.
Tested latest edits - looks good overall. Just one more edit needed for date field types I think.
pheyos
left a comment
There was a problem hiding this comment.
Great to see the added permission tests and the trial / basic license test split!
pheyos
left a comment
There was a problem hiding this comment.
For the extended Discover checks:
We already validate that Discover displays the query as expected. IMO it would be good to also add a second assertion for the hit count of that discover page. That way we can be sure that data is loaded as expected. I've created an example, how this could look like.
For the Lens link validation:
I'd suggest to have a separate test file, because it would interrupt the existing index_data_visualizer tests badly. I think this would be good to have in a follow-up PR because it will require some additional work.
What do you think @peteharverson ?
|
Adding the hit count assertion for the Discover drilldown looks like it is worth including in this PR @pheyos. Adding new tests for the Lens link in a follow-up PR is sensible. Would be great to have even some basic validation that expected content is displayed in the Lens page. |
| import { CombinedQuery } from '../../../common'; | ||
|
|
||
| export function getActions( | ||
| indexPattern: IndexPattern, |
There was a problem hiding this comment.
I guess it should be IIndexPattern interface instead
There was a problem hiding this comment.
note: we should replace all IndexPattern imports with IIndexPattern later because otherwise, this class end up in our bundle
Thanks! Good catch. I added |
peteharverson
left a comment
There was a problem hiding this comment.
Tested latest edits for date fields and the Discover 'open in new tab' behavior, and LGTM
pheyos
left a comment
There was a problem hiding this comment.
Open Discover in new tab works well now for me and the extended Discover checks are looking good! Just one comment around the trial/basic test split:
pheyos
left a comment
There was a problem hiding this comment.
Tested and functional tests LGTM
💚 Build SucceededMetrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
Summary
Part of #86387. This PR brings:
Checklist
Delete any items that are not applicable to this PR.