## Summary
Updated the title for the `enterprise_search` Integration category from
`Enterprise Search` to `Search`
### Screenshots
<img width="1676" alt="image"
src="4f882c01-570c-4117-8689-5caddb7a7de1">
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
- [x] Fixes sticky bottom bar to go behind the side nav in policy
details
- [x] Adds functional test to ensure bug does not get reopened
##
BEFORE
AFTER
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
We're updating the looks of the existing pipeline selection dropdown's
items in preparation for streamlining the UX of field configuration:
- Listing all source fields that are configured in the pipeline
- "Destination field" is dropped as it's visible in the next screens
- If a pipeline cannot be selected due to the index missing some
configured fields, the missing fields are listed in the reason
- Updated text and style
Example - selectable pipelines
Example - some disabled pipelines
### Checklist
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [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
- [x] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [x] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Closes #160653
## Summary
This PR enabled Anomalies, Osquery tabs, removes Uptime link and adds
open as page link.
## Testing
- Before going to host view go to inventory click on Anomaly detection
and and set up ML jobs for hosts (it will be enable instead of recreate
in case it's not enabled:
<img width="200" alt="image"
src="29eb5112-7292-474a-86f3-7e9a765ac307">
)
- Go to the hosts view and open the flyout
- the Anomalies Tab should be visible (find a host with detected anomaly
and open it):
<img width="1728" alt="Screenshot 2023-07-06 at 14 49 08"
src="e2d72725-ee3d-4f20-a7f3-c8bed104ce8b">
- Osquery tab should be visible:
<img width="1728" alt="Screenshot 2023-07-06 at 14 41 30"
src="114d6e94-0792-4af6-8755-1c0d0d96176d">
- Click on open as page - should navigate to node details page
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
fixes [#161553](https://github.com/elastic/kibana/issues/161553)
## Summary
Fixes click event on the tooltip content
13c8fde1-7dfe-4fb0-92f2-b3e45bd36972
### How to test
- Start a local Kibana instance
- Navigate to `Infrastructure` > `Hosts`
- Click on the `?` icon in the table column headers and then click on
the content. It must not sort the table
Relates to #160371
## Summary
This PR adds an option to hide the chart when using the
`AlertSummaryWidgetFullSize` component - when the prop
`shouldHideCharts` is set to `true` the charts won't be visible
## Storybook
- Added `Full Size Without Chart`
<img width="1804" alt="image"
src="e0ee3360-2212-4c0c-943c-b1b9ece66a68">
## Testing
Set `shouldHideCharts` to `true` when using the alert summary component
and the charts should not be visible. If it's not set the chart should
be visible.
## Risc score management page - Part I
For testing enable: `riskScoringRoutesEnabled`
This PR include:
- Entity analytics as a separate folder and lazy sub plugin - in the
future should include all entity analytics related frontend code
- Adding item to Security -> Manage page
- Layout for Entity Analytics management page
- Integrating with preview API
Not include:
- Integration with enable/disable risk score API
4499f3fb-ca19-46a8-8d4d-33fd7080738d
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Rebranding the Enterprise Search home card and page left nav from
"Enterprise Search" to "Search"
We were initially going to change the Icon, but have since decided to
stick with the Enterprise Search logo and just change the title.
### Screenshots
<img width="1676" alt="image"
src="df5ec636-fa66-44b5-b22d-88de573c100f">
<img width="1676" alt="image"
src="4ffc10d4-39c1-476b-90cd-2d590a2eb1df">
(Note: Overview page and breadcrumbs will be updated in another PR)
## Summary
Removes the following from `management` redux store
- `endpointDetails` and child keys (`hostInfo`, `hostInfoError` and
`isHostInfoLoading`)
- `policyResponse`, `policyResponseLoading` and `policyResponseError`
- `hostStatus`
- rearranged/refactored a huge chunk of endpoint list component to make
it more manageable for later when we remove endpoint list data out of
redux
- endpoint list nav link component:
0e281f1191
- back to policy link component:
9e3c771eb7
- extracted table columns out of the component:
3728ca604e
- rearranged variables: 09bb01a1d2
- transform callout component: 808fa81373
### Checklist
- [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
EPIC: https://github.com/elastic/kibana/issues/144943
## Summary
Update Events/alerts table to provide `CellActions` with a complete
`FieldSpec`object from DataView
### Affected pages:
* Alerts page
* Security Dashboards
* Rule preview
* Host events
* Users events
### How to test it
Use CellActions on one of the affected pages.
### Checklist
- [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>
relates to [#160381](https://github.com/elastic/kibana/issues/160381)
closes [#161432](https://github.com/elastic/kibana/issues/161432)
## Summary
This pull request aims to enhance the usage of Lens Embeddable by
introducing abstractions that simplify the creation of the necessary
data structures for rendering charts. The goal is to improve the DX by
providing clearer and more intuitive interfaces.
More details in the
[README.md](62a9ef70e6/x-pack/plugins/infra/public/common/visualizations/lens/README.md)
### For reviewers
- The majority of the changes are concentrated in the
`common/visualizations` directory. The `formulas/host` files have been
modified to only contain the formula itself. The formulas are now
designed to be independent of specific chart styles.
- The `use_lens_attributes` hook has been modified to receive the
essential information. Previously, it had knowledge of host formulas,
but now it accepts an abstracted chart representation and returns the
JSON object accordingly.
- Chart-specific style configurations have been moved to the chart usage
component in the `tile` and `metric_chart` components.
### How to test
- Start a local Kibana instance
- Navigate to `Infrastructure` > `Hosts`
- Check all charts and navigate to Lens.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Sets up unit testing for react components.
Unit testing of server-side components already implemented.
### Checklist
- [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
Closes https://github.com/elastic/kibana/issues/159558
### What was done
Added feature flag in deep linking to hide Storage Explorer from the
global search in serverless
### Before
<img width="1113" alt="Screenshot 2023-07-04 at 09 25 11"
src="6f4ecfad-8067-4c40-8478-15550463f3d0">
### After
<img width="1113" alt="Screenshot 2023-07-04 at 09 26 13"
src="2d33214b-4d30-4836-a6b2-c6878ef1ba29">
Adds checks to avoid unnecessary initial rerenders and refetches of data
when loading the transform wizard. This reduces rerenders from 14 to 11
and more importantly the request to fetch index data is triggered only
once instead of three times. One of the requests even triggered an error
which could briefly trigger a callout on slower connections.
## Summary
This PR adds UI validation for comments maximum length.
It shows error message and disables save button when the comment exceeds
30k characters while
- **Adding a new comment**
- **Updating an existing comment**
### 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
### For maintainers
- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
This PR fixes few issues occurring while running FTR API tests against
actual serverless project.
How to run:
```
TEST_CLOUD=1 ES_SECURITY_ENABLED=1 NODE_TLS_REJECT_UNAUTHORIZED=0 TEST_ES_URL=<your_es_url_with_credentials> TEST_KIBANA_URL=<your_es_url_with_credentials> node --no-warnings scripts/functional_test_runner --es-version=8.9.0 --config x-pack/test_serverless/api_integration/test_suites/search/config.ts --bail
```
The first error is faced during Elasticsearch version validation
```
ERROR Error: attempted to use the "es" service to fetch Elasticsearch version info but the request failed: ResponseError: {"ok":false,"message":"Unknown resource."}
at SniffingTransport.request (/Users/dmle/github/kibana/node_modules/@elastic/transport/src/Transport.ts:535:17)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Client.InfoApi [as info] (/Users/dmle/github/kibana/node_modules/@elastic/elasticsearch/src/api/api/info.ts:60:10)
at FunctionalTestRunner.validateEsVersion (functional_test_runner.ts:129:16)
at functional_test_runner.ts:64:11
at FunctionalTestRunner.runHarness (functional_test_runner.ts:251:14)
at FunctionalTestRunner.run (functional_test_runner.ts:48:12)
at log.defaultLevel (cli.ts:112:32)
at run.ts:70:7
at withProcRunner (with_proc_runner.ts:29:5)
at run (run.ts:69:5)
at FunctionalTestRunner.validateEsVersion (functional_test_runner.ts:131:13)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at functional_test_runner.ts:64:11
at FunctionalTestRunner.runHarness (functional_test_runner.ts:251:14)
at FunctionalTestRunner.run (functional_test_runner.ts:48:12)
at log.defaultLevel (cli.ts:112:32)
at run.ts:70:7
at withProcRunner (with_proc_runner.ts:29:5)
at run (run.ts:69:5)
```
Since there is no version term in case of serverless, we can skip
version check by using newly added to FTR schema `serverless` property
(`false` by default). It is set to `true` in root FTR config
`/shared/config.base`.
The next error is related to ESArchiver relying on `ES` FTR service to
provide ESClient.
```
ResponseError: security_exception
│ Root causes:
│ security_exception: unable to authenticate user [system_indices_superuser] for REST request [/kibana_sample_data_flights]
```
It is fixed by using the default user (from host url) instead of
`system_indices_superuser` we use in stateful run.
## Summary
Attaching ELSER pipelines to an index was disabled when ELSER pipelines
were introduced. This PR enables this feature with the following logic:
- An ELSER pipeline is selectable if all the source fields in its
`fieldMapping` configuration are present in the index. Otherwise it's
disabled in the dropdown with a message indicating which fields are
missing.
- When an ELSER pipeline is selected for attachment to an index, the
field configuration screen shows a read-only version of the field
mappings. The modification widgets (field selector dropdown, Add button,
delete button in the list) are hidden in this mode.
ELSER pipeline is selectable:
ELSER pipeline is not selectable if source fields are missing from the
index mapping:
Field configuration panel in read-only mode:
### Checklist
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [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
- [x] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [x] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
This PR:
- Adds the ability to create system action types
- Creates system connectors on Kibana `start` from the system action
types
- Prevents system action to be created/updated/deleted
- Return system actions from the get/getAll endpoints
### 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
### For maintainers
- [x] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Some refactor broke our labels, added a test case to make sure it's part
of e2e tests.
### After
<img width="1456" alt="image"
src="23f8cd56-ad4b-4c9d-97e7-2681c963406d">
### Before
<img width="1495" alt="image"
src="f835742b-d506-4beb-b68f-1d51d164ad96">
## Summary
This PR removes `onClose` prop from the expandable flyout as it is not
necessary anymore
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Closes
#155723,#155846,#156045,#156041,#156074,#156130,#156151,#156739,#157673,#156422,#156998,#156922,#156921,#157452,#158366,#158586,#158711
## Summary
Issue was resolved by PR #160584. This PR unskips saved object tests
documented as skipped in #158918.
### Testing
Flaky test runner:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2543
Closes #160376
## Summary
This PR adds the initial version of the Overview tab including KPI tiles
and metadata summary.
<img width="865" alt="image"
src="36b62899-64e8-4359-a7f5-e09a2a300bba">
The storybook is not showing the lens charts as it will be hard because
of the dependencies (we should consider if it is worth the effort to add
them there in the future) The other parts look Ok:
<img width="2550" alt="image"
src="348b868b-9ed9-4b59-b02c-cb1e91eecb5a">
## Next steps 👣
There are still some parts that can be addressed separately when other
parts are ready:
- The date is currently relying on the host date picker (passed as an
override) which can be fixed once the date picker is added to the page
## Testing
- Go to host view and open the flyout - the default tab is now overview
tab
- Hint: to see the chart movements better pick a wider time range (5
days for example)
<img width="1468" alt="image"
src="d31faf71-5beb-48f2-b20a-7dfcacd52325">
- Show all button in the metadata section should open the metadata tab
- Storybook: Use `yarn storybook infra` to run the storybook and check
both `Page` and `Flyout`
## Summary
Addresses root cause of https://github.com/elastic/kibana/issues/158918
Underlying cause is that _esArchiver_ is messing up with the SO indices
whilst Kibana is already running.
This can cause some asynchronous calls made by Kibana (e.g. `GET
/.kibana_8.8.0/telemetry:telemetry`) to hit ES at the exact time where
the underlying SO indices are **just** recreated, causing the error
described in the related issue.
The idea of the fix is to delete `mappings.json`, used by _esArchiver_
to create the SO indices. This way, _esArchiver_ will use existing SO
indices instead (aka the "official" ones, created by Kibana at startup),
thus avoiding the problem altogether.
As a side effect:
- Documents in `data.json` must be updated so that they are correctly
inserted.
- The different FTR tests must make sure the SO indices are empty before
inserting those documents (done in the `before(), beforeEach()`
statements).
Connected to https://github.com/elastic/kibana/issues/146945
## Summary
| Description | Limit | Done? | Documented?
| ------------- | ---- | :---: | ---- |
| Total number of attachments that can be created using the bulk create
API | 100 | ✅ | No |
### 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
@gchaps and I met to review text on some APM UI pages. Outcomes:
1. Service **m**ap or Service **M**ap — there is inconsistency in the
APM UI with how we refer to Service maps. In some cases, we use title
case (Service Map). In others, we use sentence case (Service map). As
per the [EUI writing
guidelines](https://eui.elastic.co/#/guidelines/writing/guidelines#capitalization),
we should use title case for product features.
2. Storage **e**xplorer or Storage **E**xplorer — same story here. We
use title case sometimes and sentence case others. We should use title
case as this is a product feature.
3. Various text enhancements and changes.
Fixes: https://github.com/elastic/kibana/issues/161305
## Summary
- Passes a new `immutable` params to the `upgradeRule` method that is
used when upgrading rules.
- Looks like we had a longstanding bug here in which rule updates of
rule types that changed the type of the rule were overwriting the
`immutable` prop to `false`. (Actually, those rules were deleted and
recreated with `immutable: false`)
- This was causing the `fetchAllInstalledRules` method of our
`ruleObjectsClient` NOT to retrieve these rules when they were already
installed.
- Since our installation `_review` and `_perform` endpoint depends on
this client, these rules that had had their types updated were being
incorrectly listed as available for installation.
## Testing
Repeat testing steps laid out in:
https://github.com/elastic/kibana/issues/161305
Rules shouldn't be duplicated.
### For maintainers
- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
