-
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
[Security Solution] Add Host/User flyout in One Discover. #199279
[Security Solution] Add Host/User flyout in One Discover. #199279
Conversation
incremental change incremental save entity flyout working [CI] Auto-commit changed files from 'node scripts/notice' [CI] Auto-commit changed files from 'node scripts/lint_ts_projects --fix' fix: quick checks Merge discover getRenderAppWrapper fix: incremental change fix: merge mistakes fix: types and tests fix: undo unnecessary changes tests: cell renderer fix: small quirks fix: types fix: getCellRenderers fix: test comment fix: formatting
2a300b9
to
ac84386
Compare
/ci |
/ci |
/ci |
string, | ||
(props: DataGridCellValueElementProps) => ReactElement | ||
>; | ||
export type CustomCellRenderer = Record<string, FunctionComponent<DataGridCellValueElementProps>>; |
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.
@elastic/kibana-data-discovery
Changed this to FunctionComponent
because previous type does not accept memoized components. FunctionComponent
is more inclusive.
Please let me know if you would keep this a function instead.
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.
I don't really see an issue with this, although we do already memoize cell renderers here, so it's likely not necessary to memoize again:
: memo(UnifiedDataTableRenderCellValue); |
If we make this change, it might even make sense to go all the way and just accept ComponentType
, but not really a strong opinion.
Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations) |
...scover/public/context_awareness/profile_providers/security/security_root_profile/profile.tsx
Outdated
Show resolved
Hide resolved
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.
kibana.jsonc LGTM
...scover/public/context_awareness/profile_providers/security/security_root_profile/profile.tsx
Outdated
Show resolved
Hide resolved
src/plugins/discover_shared/public/services/discover_features/types.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/security_solution/public/one_discover/app_wrapper/index.tsx
Show resolved
Hide resolved
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! Thanks Jatin for doing this and taking the time to discuss and address each comment.
Great work! 💯
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.
@logeekal It looks like discoverShared
might have been partially removed from Discover and now there are some related type errors. Other than that this LGTM from the Data Discovery side and will be good to go once fixed.
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.
Thanks for fixing the types, and this now LGTM on the Data Discovery side 👍 Congrats on merging the first Security extension point implementations @logeekal!
Thanks. Finally :D . But this is also experimental 🤣 |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
async chunk count
History
|
Starting backport for target branches: 8.17, 8.x https://github.com/elastic/kibana/actions/runs/12085265704 |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
…199818) ## Summary Fixes elastic/security-team#11112 Follow up to - #199279 Adds functional test for Security Profiles in One Discover. ### Checklist Delete any items that are not applicable to this PR. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
…9279) ## Summary Handles elastic#191998 Follow up work: - elastic/security-team#11112 - elastic#196667 This PR add below entity flyouts for below entities in One Discover: - host.name - user.name - source.ip - destination.ip In this PR we re-use the security solution code by making use of below model based on `discover-shared` plugin. ```mermaid flowchart TD discoverShared["Discover Shared"] securitySolution["Security Solution"] discover["Discover"] securitySolution -- "registers Features" --> discoverShared discover -- "consume Features" --> discoverShared ``` ## How to Test >[!Note] >This PR adds `security-root-profile` in One discover which is currently in `experimental mode`. All changes below can only be tested when profile is activated. Profile can activated by adding below lines in `config/kibana.dev.yml` > ```yaml > discover.experimental.enabledProfiles: > - security-root-profile > ``` > 1. As mentioned above, adding above experimental flag in `kibana.dev.yml`. 2. Spin up Security Serverless project and add some alert Data. 3. Navigate to Discover and add columns `host.name` and `user.name` in table. Now `host` and `user` flyouts should be available on clicking `host.name`, `user.name`, `source.ip` & `destination.ip`. 4. Flyout should work without any error. 5. Below things are not working and will be tackled in followup PR : - Security Hover actions - Actions such as `Add to Timeline` or `Add to Case` ### Checklist Delete any items that are not applicable to this PR. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
…lastic#199818) ## Summary Fixes elastic/security-team#11112 Follow up to - elastic#199279 Adds functional test for Security Profiles in One Discover. ### Checklist Delete any items that are not applicable to this PR. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Summary
Handles #191998
Follow up work:
This PR add below entity flyouts for below entities in One Discover:
In this PR we re-use the security solution code by making use of below model based on
discover-shared
plugin.How to Test
Note
This PR adds
security-root-profile
in One discover which is currently inexperimental mode
. All changes below can only be tested when profile is activated. Profile can activated by adding below lines inconfig/kibana.dev.yml
kibana.dev.yml
.host.name
anduser.name
in table. Nowhost
anduser
flyouts should be available on clickinghost.name
,user.name
,source.ip
&destination.ip
.Add to Timeline
orAdd to Case
Checklist
Delete any items that are not applicable to this PR.