* Added ability to fire actions when an alert instance is resolved
* Fixed due to comments
* Fixed merge issue
* Fixed tests and added skip for muted resolve
* added test for muted alert
* Fixed due to comments
* Fixed registry error message
* Fixed jest test
* [ML] Adds functional tests for the index data visualizer card contents
* [ML] Fix translations
* [ML] Fix type errors in permissions tests
* [ML] Address comments from review
* Adds framework for replacing API schemas
* Update integration tests with new schema
* Fix response type on createRule helper
* Add unit tests for new rule schema, add defaults for some array fields, clean up API schema definitions
* Naming updates and linting fixes
* Replace create_rules_bulk_schema and refactor route
* Convert update_rules_route to new schema
* Fix missing name error
* Fix more tests
* Fix import
* Update patch route with internal schema validation
* Reorganize new schema as drop-in replacement for create_rules_schema
* Replace updateRulesSchema with new version
* Cleanup - remove references to specific files within request folder
* Fix imports
* Fix tests
* Allow a few more fields to be undefined in internal schema
* Add static types back to test payloads, add more tests, add NonEmptyArray type builder
* Pull defaults into reusable function
* Add basic Loading component
- for pages with shifting layouts or where skeletal loading doesn't make sense
* Move Loading to shared components
* Update WS to use new shared Loading component
* Fix for non-Layout WS Overview page
* Update x-pack/plugins/enterprise_search/public/applications/app_search/components/engine/engine_router.tsx
Co-authored-by: Scotty Bollinger <scotty.bollinger@elastic.co>
Co-authored-by: Scotty Bollinger <scotty.bollinger@elastic.co>
Jest tests are currently organized into main configuration files (src/dev/jest/config.js and x-pack/dev-tools/jest/create_jest_config.js). Both of these are similar, but very slightly due to previously being in separate repositories. This change consolidates the scripts referenced in those configs and moves them to the `@kbn/test` project.
OSS contained an alias for `test_utils`. Those aliases have been removed in favor of importing these utilities from `@kbn/test/jest`
Blocker to #72569
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
- Make APM and UX headers size medium instead of large
- Remove margin around APM main container
- Make APM tabs condensed
- Switch environment filter and date picker positions
- Move search bar (kuery + date picker) below the tabs
- Wrap pages in `EuiPage` components
- Set a minimum width on the enironment selector so it doesn't collapse when loading
- Don't show search bar on service map
Fixes#81954.
* add analytics map endpoint and server model
* add map action to job and models list
* wip:fetch models for jobs. Use url generator
* get models when extending node. deduplicate elements
* add job type icons. disable map action if job not finished.
* move shared const to common dir
* persist map tab. handle indexPattern from visualizer
* use url generator in models list
* temporarily disable delete action in flyout
* update legend style. make map horizontal
* update dfa model to use spaces changes
* format creation time
* update from indexPattern to index.remove refresh button
* handle index patterns with wildcard
* Expose `registerExtension()` interface on `Plugin#start`
* Refactor use of `CustomConfigurePackagePolicy` to the new registerExtension approach
* Refactor to always show registered ui extension (even if Integration has configuration options)
This PR includes the following refactors:
1. Moves the Index Pattern Api from _Stack Alerts_ to the _Server_ plugin of _Trigger Actions UI_. This fixes a potential bug where a user could disable the _Stack Alerts_ plugin and inadvertently break the UI of the _ES Index _ action type.
2. Extracts the UI components for _Index Threshold_ and _Geo Threshold_ from the _Trigger Actions UI_ plugin and moves them into _Stack Alerts_.
## Summary
* Move stream utility functions from `server/services/epm/registry/streams.ts` to `server/services/epm/streams.ts`
* They're only used in registry at the moment but aren't specific to registry
* Move archive extraction functions from `server/services/epm/registry/extract.ts` to `server/services/epm/archive.ts`
* The Registry isn't the only service/code which needs to extract packages. Continue consolidating archive-related code under archive vs registry
* Fix CURRENT_MAJOR_VERSION for use in Elastic docs links
- Was previously just sending (e.g.) "7". instead of "7.9"
* Add App Search DOCS_PREFIX constant
- follow WS's example
* Update all App Search doc links to use prefixed URLs
- except for Enterprise Search setup guide, which should be updated to use a shared URL at some point in any case
* Moved out type for OperatingSystem and moved OS translations one level higher.
* Changed the translation to be consistent between trusted apps and policy.
* Unified translations of OS types between trusted apps and policy.
* Removed unused types.
* Added registered AV form section.
* Changed the property structure to match the format expected by endpoint.
* Fixed the visual alignment of titles in the form and added responsiveness.
* Updated snapshots.
* Moved out type for OperatingSystem and moved OS translations one level higher.
* Added config form heading component.
* Cleaned up translations.
* Fixed type error with initialization.
* Fixed error in trusted app creation form test.
* Removed the guard for now in favour of better initialization.
* Fixed the store test.
* Fixing functional test data.
* Added functional test config option to account for a custom header within security app.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
resolves https://github.com/elastic/kibana/issues/79785
Until now, the execution status was available in the the event
log document for the execute action. In this PR we add it.
The event log is extended to add the following fields:
- `kibana.alerting.status` - from executionStatus.status
- `event.reason` - from executionStatus.error.reason
The date from the executionStatus and start date in the event
log will be set to the same value.
Previously, errors encountered while trying to execute an
alert executor, eg decrypting the alert, would not end up
with an event doc generated. Now they will.
In addition, there were a few places where events that could
have had the action group in them did not, and one where the
instance id was undefined - those were fixed up.
* [ML] table config in the URL state
* [ML] fix job list on the management page
* [ML] store query filter in the URL
* [ML] fix context for the management page
* [ML] update module_list_card.tsx in Logs UI
* [ML] fix unit tests
* [ML] fix unit tests
* [ML] fix unit tests
* [ML] move utils functions
* [ML] url generator to support both job and group ids
* Add index template link to data stream details
* Fixed ILM policy link and added a check for index template name after navigation
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Packages/Archives aren't limited to the registry any longer. Continue moving file- & cache-related functions from services/registry to services/archive.
Move `getAsset` and `pathParts` to archive/index. The behavior is the same for now, but it's more accurate to separate these from registry namespace.
Registry has `fetch*` and other functions for dealing with the online service.
