-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Grouped features for space management #74151
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
3318288 to
dae6500
Compare
9fdacfa to
5acc79f
Compare
5f35d8a to
c392d66
Compare
c392d66 to
856ef22
Compare
legrego
left a comment
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.
Author's notes for reviewers
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.
note: no functional changes to this view. This is a re-org to support future changes to the avatar customization
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.
note: wrapping in <RedirectAppLinks> allows our links into the Role Management app to use client-side routing instead of forcing a full-page reload.
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.
Discussed with the design team, and the decision was to add an icon for the Management section to be consistent with the other feature categories.
Client Side Monitoring (CSM) is currently technically located in the APM plugins folder but from a user perspective it's a separate app (still under Observability). In 7.11 we hope to move CSM out of APM so it also technically is a separate app. @shahzad31 WDYT? |
@sorantis Yes it will keep following APM permission POV. Once we have synthetic data it might change but for now. It will remain as is. |
@legrego @sqren Could we consider changing the display string for the "APM" feature to say "APM and Client Side Monitoring"? Then at least the user would see that the one feature is really enabling two applications in the main nav. |
|
@elasticmachine merge upstream |
|
@jportner CI is struggling right now, but this is otherwise ready for another review. Note that EUI merged the bugfix I was waiting on, so |
spong
left a comment
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.
Security changes LGTM -- thanks @legrego! 🙂
andrewvc
left a comment
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.
LGTM from Uptime's side
|
@elasticmachine merge upstream |
jportner
left a comment
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.
More feedback and optional nits
- I like that you changed the "Enterprise Search" and "Management" categories so they're just a single checkbox!
- I like the accordion's
extraAction! - We could switch the order of the "Observability" features so they more closely match the order that's in the navigation pane (Logs, then Metrics, then APM and Client Side Monitoring, then Uptime)
- It's not immediately clear what disabling "Built-In Alerts" does..?
- Disabling "Actions" just disables the "Connectors" tab of the "Alerts and Actions" page... perhaps some of these features could use a tooltip describing what they are?
- Disabling the "Management" category entirely (0 / 8 features visible) still leaves the "Stack Management" page visible in the navigation pane (see screenshot below); I understand this is intended, but it's going to be confusing for end-users. Maybe we could use a tooltip for this category as well?
Good catch, sorry I missed that in the first review.
Hmm. @gmmorris would you expect this toggle to turn off "Index Threshold alerts" for the space?
Not a bad idea. I'd like to place this in the "Additional design edits for spaces management are out-of-scope for this PR, and will be addressed in a followup as time permits." category, at least for now. I really want to have time to group the features on the role management page in 7.10 as well, so that is my next ux focus for this grouping initiative. If I didn't have role management to work on as well, then I'd definitely consider this now.
Also a good idea. I don't yet know how to solve this holistically with my current approach, so I might 🙈 band-aid this for the time being by looking for this category explicitly, and rendering it differently. |
jportner
left a comment
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.
LGTM
💚 Build SucceededBuild metrics@kbn/optimizer bundle module count
page load bundle size
History
To update your PR or re-run it, just comment with: |
|
Doc updates (screenshots, etc) will follow after role management is updated as well |
* Grouped features for space management * Apply suggestions from code review Co-authored-by: Joe Portner <5295965+jportner@users.noreply.github.com> * Address PR Feedback * docs changes * updating types/docs * update APM feature name * Reintroduce extraAction following EUI update * change ordering of infra features, and render callout for management category Co-authored-by: Joe Portner <5295965+jportner@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Joe Portner <5295965+jportner@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>

Summary
Adds a new
categoryproperty to each registered featureThe feature schema has been updated to require a
category, which tells Kibana how to visually organize the various features.This PR exclusively uses the
DEFAULT_APP_CATEGORIESexposed by core for all registered features, but the schema will accept any category so long as it satisfies the underlyingAppCategoryinterface.Groups features by category for Spaces Management
The spaces management screen has been updated to take advantage of these categories. The old implementation displayed a flat table of features, and the ordering was not always predictable.
The updated interface organizes features according to the category in which they exist. Features can be toggled on/off independently as before, and users can also toggle entire categories.
Out of scope
elastic/eui#3881 prevents the categories from rendering anextraAction, which I would otherwise use to indicate that a section hasx/y features enabled. I don't consider this a blocker for merge however.Preview of docs changes: https://kibana_74151.docs-preview.app.elstc.co/guide/en/kibana/master/development-security.html
Relates: #72659
Resolves #54793