Skip to content
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

[Security Solutions] Create all users tab on user page #128375

Merged
merged 4 commits into from
Mar 28, 2022

Conversation

machadoum
Copy link
Member

@machadoum machadoum commented Mar 23, 2022

Summary

Create 'All Users' tab on the User page. It also renames the authentication tab which was previously called 'All users'.

Screenshot 2022-03-24 at 15 15 42

Mar-23-2022 14-48-11

Checklist

@machadoum machadoum changed the title Siem explore issue 128156 [Security Solutions] Create all users tab on user page Mar 23, 2022
@machadoum machadoum self-assigned this Mar 24, 2022
@machadoum machadoum added v8.2.0 Team:Threat Hunting Security Solution Threat Hunting Team Team:Threat Hunting:Explore release_note:enhancement enhancement New value added to drive a business result auto-backport Deprecated - use backport:version if exact versions are needed labels Mar 24, 2022
@machadoum machadoum marked this pull request as ready for review March 24, 2022 14:24
@machadoum machadoum requested a review from a team as a code owner March 24, 2022 14:24
Comment on lines -110 to +114
skip?: boolean;
/**
* When the flag switches from `false` to `true`, it will abort any ongoing request.
*/
abort?: boolean;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stephmilovic I renamed it because it doesn't skip the request, but instead, it aborts any ongoing request.

Comment on lines -125 to +129
if (error != null) {
if (error != null && !(error instanceof AbortError)) {
Copy link
Member Author

@machadoum machadoum Mar 24, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It avoids showing annoying popups with errors when the request is aborted.

@YulNaumenko YulNaumenko self-requested a review March 24, 2022 15:09
Copy link
Contributor

@stephmilovic stephmilovic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code reviewed ✅ manual testing ✅ LGTM!

@machadoum
Copy link
Member Author

@elasticmachine merge upstream

@machadoum machadoum enabled auto-merge (squash) March 28, 2022 09:09
@semd semd self-requested a review March 28, 2022 10:14

export const UsersTable = React.memo(UsersTableComponent);

const getUsersColumns = (): UsersTableColumns => [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't we place this const before the component definition, with the rowItems?

@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
securitySolution 2986 2991 +5

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 4.8MB 4.8MB +4.5KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
securitySolution 247.3KB 247.4KB +141.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @machadoum

@machadoum machadoum merged commit c1b7448 into elastic:main Mar 28, 2022
@kibanamachine
Copy link
Contributor

⚪ Backport skipped

The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.

Manual backport

To create the backport manually run:

node scripts/backport --pr 128375

Questions ?

Please refer to the Backport tool documentation

},
];

const agg = { user_count: { cardinality: { field: 'user.name' } } };
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this aggregation stored in a const, but the other user_data agg is hardcoded?

Copy link
Contributor

@semd semd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a couple of minor comments. tested locally and everything working as expected, data is displayed properly, useSearchStrategy with abort and query toggle is working well, and the code looks solid. LGTM! ✅

machadoum added a commit to machadoum/kibana that referenced this pull request Mar 29, 2022
machadoum added a commit that referenced this pull request Mar 29, 2022
* Update user page deep links

* Fix a couple of code style issues introduced on #128375

 #128375
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 30, 2022
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 128375 or prevent reminders by adding the backport:skip label.

@spalger spalger added the backport:skip This commit does not require backporting label Mar 30, 2022
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed backport:skip This commit does not require backporting enhancement New value added to drive a business result release_note:enhancement Team:Threat Hunting:Explore Team:Threat Hunting Security Solution Threat Hunting Team v8.2.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants