* Changed the text for the description text in the antivirus registration form. Moved the form component to components folder and extracted translations into constants to make code more readable.
* Extracted EventsForm to reduce duplication among events forms.
* Fixed auto follow actions
* Created a provider for all follower index table actions to fix modal auto-closing
* Moved i18n texts into a const to avoid duplication
* Removed unnecessary imports and added index.js file for follower_index_actions_provider imports
* Fixed wrong imports deletion
* Fixed wrong imports deletion
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Add react-motion package
This is needed to animate the loading progress bar in the Enterprise Search schema views
* Add shared interface
* Migrate IndexingStatusContent component
This is a straight copy/paste with only linting changes and tests added
* Migrate IndexingStatusErrors component
This is a copy/paste with linting changes and tests added. Also changed out the Link component to our EuiLinkTo component for internal routing
* Migrate IndexingStatus component
This is a straight copy/paste with only linting changes and tests added
* Migrate IndexingStatusFetcher component
This is a copy/paste with some modifications. The http/axios code has been removed in favor of the HTTPLogic in Kibana.
This is a WIP that I am merging to master until I can get it working in the UI. Without either Schema component in the UIs for App Search or Workplace Search this is only a POC. Will not backport until this is verified working and have written tests.
* Add i18n
* Revert "Add react-motion package"
This reverts commit 92db929d2a.
* Remove motion dependency
* Update copy
Co-authored-by: Constance <constancecchen@users.noreply.github.com>
* Refactor per code review
- Remove stui classes
- Inline status
Co-authored-by: Constance <constancecchen@users.noreply.github.com>
Reapplies the #84123 PR:
This PR changes the default term from “Resolved” to “Recovered”, as it fits most use cases and we feel users are most likely to understand its meaning across domains.
Passing in an empty string '' to useResolver() would trigger a wild card search across all indices and fields, potentially causing a timeout and the page would fail to load. The following pages were affected: Single Metric Viewer, Data frame analytics models list, Data frame analytics jobs list, Data frame analytics exploration page, File Data Visualizer (Data visualizer - Import data from a log file). This PR fixes it by passing undefined instead of '' to useResolver to avoid calling _fields_for_wildcard with an empty pattern. Jest tests were added to cover the two parameter scenarios empty string/undefined.
The url templates provided for call of the API with space information was missing the /api/ section in it.
(cherry picked from commit 35f1cc16eaa29666d7212402f57ab17858ebc96d)
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
This PR changes the behavior of severity and risk score overrides in two ways:
- adds support for arrays in the mapped event fields (so a rule can be triggered by an event where e.g. `event.custom_severity` has a value like `[45, 70, 90]`)
- makes the logic of overrides more flexible, resilient to the incoming values (filters out junk, extracts meaningful values, does its best to find a value that would fit the mapping)
This PR changes the default term from “Resolved” to “Recovered”, as it fits most use cases and we feel users are most likely to understand its meaning across domains.
