* popover padding size unified
* remove panels from all context menus
* action items order changed
* cases menu items test fixed
* translations and small changes
* remove components not used anywhere
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Angela Chuang <yi-chun.chuang@elastic.co>
* fix: HostInput error placement onChange
* fix: check for duplicates in hosts
* fix: validate all sections
* fix: error swapping
* fix: yaml placeholder position and styling
* test: add unit tests for delete behaviour
* tidy: use generic for reduce typing
* Make count table field and alert table event renderer undraggable
* Remove tooltip from alert count table
* Remove DefaultDraggable wrapper from reason field
* Fix unit test and remove unused props
I am not 100% sure, but apparently, the test was broken due to a long import chain loop.
I cut the import chain by extracting some constants to a file.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
- Show the same empty state in the correlations table
- Add "Correlations" title above the table
- Add EuiSpacer between the sections before and after progress
- Update the copy within the beta badge title=Failed transaction correlations description=Failed transaction correlations is not GA...
- Remove s size from the beta badge
- Move the help popover to the top of the panel (similar to the Latency correlations tab)
- Move the Cancel/Refresh option to the right of the progress bar (similar to the Latency correlations tab)
- When the correlation job is running the correlations tab should show a loading state similar to the latency correlations table
- Indicate in the table headers Score is sorted by default
- Add sortability to both Latency and failed transactions correlations table
- Refactor to prevent duplicate code/components like Log, progress bar
- Fix alignments of the tab content header (previously navigating from one Trace samples tab to Latency correlation tabs will cause a minor jump in the header, or the titles within the same tab were not the same size )
- Remove the event.outcome as a field candidate (because event.outcome: failure would always be significant in this case)
- Shrink the column width for impact (previously it was at 116px)
- Added badge for High, medium, low [APM] Correlations: Show impact levels (high, medium, low) as colored badges indicating their severity
- Fix license prompt text
- Functional tests for the new tab
- Make the p value & error rate columns visible only when esInspect mode is enabled
## Summary
I’ve been re-running CI for my PR multiple times, getting failed Cypress tests every time:
https://github.com/elastic/kibana/pull/109276/checks?check_run_id=3382731658
The test is `detection_alerts/acknowledged.spec.ts` "Mark one alert as acknowledged when more than one open alerts are selected".
I’m getting the same failure also on a fresh master branch locally, so it seems like the test is broken there as well.
Skipping for now as it's blocking a critical fix for 7.15: https://github.com/elastic/kibana/pull/109276
* [ILM] Fixed the bug with built-in policies not saving because of the _meta field
* [ILM] Added PR review suggestions
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Pretty sure the rules only get created in the current kibana space, but the message is plural. Switching to singular.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Fixes `acknowledged.spec.ts` test that is currently failing on some ci builds
### 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
* get back index names in o11y
* testing and integration
* fix types
* Avoid using the rule data client for field list
* Remove left-over index argument
* no needs of alert consumer anymore
Co-authored-by: Felix Stürmer <stuermer@weltenwort.de>
- Fix, clean up and unit tests for the log log charts x axis duration based ticks. This extends existing duration utilities to support a custom threshold to be able to fine tune the formatting for either single values with more detail or chart axis ticks where less detail is required. This is useful for log axis that cover a wider range of units. As can be seen in the screenshot, axis ticks will be formatted as full seconds from 1s onwards instead of 1,000 ms already up to 10 seconds. Because the threshold parameter is optional and defaults to 10, other uses of getDurationFormatter don't need to be changed.
- Fixes the formatting of the selection badge.
