-
Notifications
You must be signed in to change notification settings - Fork 474
system: convert visualisations to lens #5740
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
Conversation
🌐 Coverage report
|
LGTM but I'd like @cmacknz to have a look as well, I don't have much experience with this. |
@rdner Agreed, I'd also like to wait for the kibana people too. @drewdaemon Can you take a look? |
Not a visualization expert, don't wait for my approval on this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally speaking, this LGTM and I'm certainly happy to see this PR!
To state it "out-loud," this PR is limited to the following dashboards
[System Windows Security] User Management Events
[System] Windows Overview
[System Windows Security] User Logons
[System Windows Security] Group Management Events
[System Windows Security] Failed and Blocked Accounts
A few comments
- I see that you are using the Legacy Metric Lens visualization. We recommend using the new Metric visualization instead, since the Legacy Metric will eventually be deprecated.
- We generally recommend replacing tag clouds with horizontal bar charts to allow you to convert to Lens. See this comment for more info.
- The description for the dashboard called
[System Windows Security] Failed and Blocked Accounts
includes mention of TSVB. Can we remove that?
- I see that an old palette got transferred over automatically by the convert-to-Lens function in many of the visualizations. If there's no objection, could we change all those palettes to the current system default?
@drewdaemon Queries:
|
No, you have to do it manually ATM. I think I pretty much explained the pros and cons of switching to horizontal bar in the comment I linked you to. We may add Tag Cloud to Lens before serverless, so if you feel strongly you can leave them as they are. Worst-case scenario is that on serverless, they are read-only. At the end of the day, this is your call.
You can just delete the whole palette property.
We've received this feedback before and are making the font larger and the breakpoints more generous in 8.8. But, we don't give users control over the size to promote alignment between metrics. Whitespace in visualizations isn't always wasted—it can actually promote faster comprehension. See this discuss post for more of our design thinking and the problems the new design solves. Again, the choice is yours, but we would really like to see the new metric adopted here. We are actively working on ironing out the imperfections in the new design to where the legacy metric can be deprecated and eventually removed. |
Agree that in context whitespace is useful. I don't think it adds here since it's not separating things that need separation. My concern is the size and the non-centrality (tight border adjacency reduces the helpful whitespace) of the indicator and how that impacts on DEI (due to visual impairment). I didn't see anything in that post that gave evidence for reduced cognitive load with the new design unless perhaps appealing to the non-conformity of size. Did I miss it? |
Thanks for the feedback.
I'm glad you're thinking this way. It does occur to me that most of the other textual data displayed in our visualizations are smaller than this (e.g. on a slice label, in a legend). We're also careful with contrast (we enforce WCAG AA compliance) which may mitigate some of the concern. However, I'll bring this up with the team since it could be an important area for improvement.
I think that the value of the new design is made clearer on the screenshots in that discussion. With the old metric, a) the visual alignment across multiple metrics is often broken and b) figures that actually have a smaller numeric value often appear larger, both sources of cognitive load. If you want to discuss more or don't feel like I've fully understood your feedback, please feel free to reach out in As I said above, new investment will center on the metric visualization. However, I'm merely acting as a consultant so you have the final say here. |
Thanks @drewdaemon. I've removed the palette clauses, but I'll leave the metrics as they are until further discussion has been had. |
FWIW, the team just decided to add tag cloud to Lens some time this year. Maybe around 8.10. |
@drewdaemon , @elastic/security-external-integrations can we get some feedback/approval on this PR, it has been opened for a while? cc @andrewkroh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies. I thought I had already approved!
No "Convert to Lens" option was available for "Logon Sources [Windows System Security]".
Word cloud, "Target Users [Windows System Security]", not converted.
Did not convert "Group Management Events - Target Groups - Tag Cloud [Windows System Security]". In the "Group Management Events - Groups vs Actions - Heatmap [Windows System Security]" the horizontal axis is visually broken because labels may not be rotated or omitted.
Note that in the case of the user events, this appears to result in significant semantic differences.
@rdner Can you approve please? |
Package system - 1.27.0 containing this change is available at https://epr.elastic.co/search?package=system |
What does this PR do?
Converts visualisations to Lens where possible.
Checklist
changelog.yml
file.Author's Checklist
Caveats:
Concerns:
I am concerned about the application of this change since it requires all users to be on 8.7 to pick up any future bug fixes.
How to test this PR locally
Related issues
Screenshots
Overview
User Logon Information
Logon Failed and Account Lockout
fold
User Management Events
fold
Group Management Events
fold