-
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
Custom Highlighted Fields Implentation in Kibana Security #152871
Conversation
💚 CLA has been signed |
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
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.
AO Changes LGTM
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
buildkite test this |
Hey @RubixSolver99, thanks for posting this PR 🎉 |
@xcrzx Definitely! Are all of these build errors from my commit? |
I haven't checked all the errors, but from what I saw, yes. |
I will get to work! I'll be sure to let you know if there are any struggles. |
I apologize for the late response, I have joined the Slack and would love to talk more. Thank you for everything thus far! |
@@ -8,6 +8,158 @@ | |||
import React from 'react'; | |||
import { screen } from '@testing-library/react'; | |||
|
|||
import { useKibana } from '../../utils/kibana_react'; |
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.
These changes seemed to be duplicated by accident, would you please revert them?
@RubixSolver99 I've sent you a message over on Slack! We can set up a time to sync there. |
* Added framework for custom highlighted fields * Added temporary json support Still looking to develop further for yml config file * Added Custom Highlighted Fields Created the ability to define customized highlighted fields * Fixed plural function name * Added docstring for config.ts file * Fixed naming convention in ui_settings * Added newline * Deleted not-needed json file * Added newline * Removed requires reload for ui_settings * UI update * Finished event details to display * Updated mock to include test fields * Fixed docstring on ln 208 * Fixed translation * Fixed metric mocks * Fixed metric mocks * Removed alerts conflict * Resolved es_results conflict * Resolved types conflict * Resolved utils conflict * Custom rule highlighted fields (#1) * Added framework for custom highlighted fields * Added temporary json support Still looking to develop further for yml config file * Added Custom Highlighted Fields Created the ability to define customized highlighted fields * Fixed plural function name * Added docstring for config.ts file * Fixed naming convention in ui_settings * Added newline * Deleted not-needed json file * Added newline * Removed requires reload for ui_settings * UI update * Finished event details to display * Updated mock to include test fields * Fixed docstring on ln 208 * Fixed translation * Fixed metric mocks * Fixed metric mocks * Removed alerts conflict * Resolved es_results conflict * Resolved types conflict * Resolved utils conflict * Removed usage in kbn-rule-data-utils * Custom Highlighted Fields Implementation (#2) * Added framework for custom highlighted fields * Added temporary json support Still looking to develop further for yml config file * Added Custom Highlighted Fields Created the ability to define customized highlighted fields * Fixed plural function name * Added docstring for config.ts file * Fixed naming convention in ui_settings * Added newline * Deleted not-needed json file * Added newline * Removed requires reload for ui_settings * UI update * Finished event details to display * Updated mock to include test fields * Fixed docstring on ln 208 * Fixed translation * Fixed metric mocks * Fixed metric mocks * Removed alerts conflict * Resolved es_results conflict * Resolved types conflict * Resolved utils conflict * Removed usage in kbn-rule-data-utils * Fixed build for helpers.test.ts * Fixed formatting * Fixed build for config.mock.ts * Fixed build es_results.ts * Fixed build schedule_notification_actions.tests.ts * Fixed build schedule_thtrottle_notification_actions.test.ts * Fixed build duplicate_rule.test.ts * Fixed build get_export_by_object_ids.test.ts * Fixed build validate.test.ts * Fixed build alerts.ts * Attempt to fixed build - Build API Docs * Attempt to fix build - Build API Docs * Attempt to fix build - Jest #1 * Attempt to fix build - Jest #7 * Attempt to fix build - Jest #13 * Attempted to fix remaining build errors * Attempt to resolve all build errors for custom highlighted fields implementation
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'm so confused why you are deleting so many files? Did you have a bad commit or something? 8019 files changed, most of those being deleted. Please don't delete 8,000+ files
Hey @stephmilovic ! @RubixSolver99 was trying to update with main after falling pretty far behind. We're working to clean this up and may suggest opening up a new PR. |
Getting Can you please put this PR back into draft mode and clean it up? |
Opened new PR for this - #163235 |
Summary
These changes allow for the ability to customize the "highlighted fields" that appear in the "Overview" tab of the event details pane for any given Kibana Security alert:
These highlighted fields can be customized using one of two methods: the UI Setting Method and the Rule Setting Method
UI Setting Method
Using this method allows for a "global" configuration that is applied to all alerts and will simply disregard any field that is not specified in the given index. This configuration can be accessed via:
Main Hamburger Menu -> Management -> Stack Management -> Kibana -> Advanced Settings -> Security Solution -> Custom Highlighted Fields
Rule Settings Method
Using this method allows for a configuration that is specific to a rule and is applied only to alerts that match the specifc rule being used. This method will also disregard any field that is not specified in the given index. This configuration can be accessed when creating a new rule or editing a pre-existing one.
If creating a new rule, the configuration can be found in:
Main Hamburger Menu -> Security -> Alerts -> Manage rules -> Create new rule -> About rule -> Advanced settings -> Custom highlighted fields
If editing a pre-existing rule, the configuration can be found in:
Main Hamburger Menu -> Security -> Alerts -> Manage rules -> [RULE NAME] -> Edit rule settings -> About -> Advanced settings -> Custom highlighted fields
This pull request resolves #131778.
Checklist
Delete any items that are not applicable to this PR.
For maintainers