Generated by
https://buildkite.com/elastic/kibana-api-docs-daily/builds/320

## Summary

Fix elastic#155792

Bump `moment-timezone` from `0.5.34` to `0.5.43` (latest version) to
include latest timezone changes

## Release Note

Fix a bug causing the latest timezone changes to not be taken into
account for date formatting (e.g Mexico 2023)

…lorerViewsClient (elastic#155878)

## 📓 Summary

Depends on elastic#154900
Closes elastic#155112  

This PR implements the `InventoryViewsService` and
`InventoryViewsClient`, injecting an instance of the client in the
KibanaContextForPlugin and exposing so a set of utilities to
retrieve/update inventory views:
- `findMetricsExplorerViews`
- `getMetricsExplorerView`
- `createMetricsExplorerView`
- `updateMetricsExplorerView`
- `deleteMetricsExplorerView`

## 👣 Next steps
- Implement elastic#154725 to consume the service

---------

Co-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani@elastic.co>
Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>

…155866)

## Summary

This PR wraps rendering of FieldPopover with additional try/catch and
error boundary so we can look into exceptions if they happen.

…ic#155519)

This PR adds e2e test run on real endpoint for coverage of isolate,
processes, kill-process and suspend-process commands from respond
console.

Depends on elastic#155360

elastic#155113)

## Summary

Part of elastic#147646

It passes the custom timerange to the converted Lens panel for both by
ref and by value legacy visualizations.
It works for all paths:
- Edit visualization--> Edit in Lens--> Replace in dashboard
- Convert to Lens --> Replace in dashboard


![2](https://user-images.githubusercontent.com/17003240/233287641-82fe190d-5b92-4368-ace8-0b576a46d32a.gif)

### 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: Marco Liberati <dej611@users.noreply.github.com>

Fixes the error 
```
"script_stack": [
            "org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues.throwIfEmpty(ScriptDocValues.java:92)",
            "org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues$Longs.get(ScriptDocValues.java:110)",
            "org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues$Longs.getValue(ScriptDocValues.java:105)",
            """total = useCgroupLimit ? doc[limitKey].value : doc['system.memory.total'].value;

    double """,
            "                                                                         ^---- HERE"


```

connected elastic/sdh-apm#765 (internal)

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>

## Summary

Closes elastic#155369


### 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 adds a technical control to prevent incompatible mappings
changes. These include:

1. Removing mapped fields. For the foreseeable future we require that
teams only introduce new fields - in short: this avoids the "reindex"
step in our migrations.
2. Changing the type of a field. We leverage ES to determine whether a
given set of mappings can be applied "on top" of another. Similarly,
this avoids the "reindex" step in migrations.

The above checks depend on a snapshot of the mappings from `main`, these
are the "current" mappings and are extracted from plugin code. This PR
will bootstrap `main` with an initial set of mappings extracted from
plugins (bulk of new lines added).

## The new CLI

See the added `README.md` for details on how the CLI works.

## How will it work?

Any new PR that introduces compatible mappings changes will result in a
new snapshot being captured, then merged to main for other PRs to merge
and run the same checks against (currently committing new snapshots
happens in the CI check so there is no manual step of maintaining the
snapshot).

## Additional

We should consider combining this CI check with the existing check in
`src/core/server/integration_tests/saved_objects/migrations/check_registered_types.test.ts`.
Hopefully we can automate the check such that no manual review is needed
from Core, not sure how we might cover the hash of the non-mappings
related fields. We could consider narrowing the Jest test to exclude
mappings.

### 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>
Co-authored-by: spalger <spencer@elastic.co>

…es should return to the documents view (elastic#152572)

Closes elastic#152485
~Would be better to override this somewhere in app state management
logic but I could not find a right place for it.~ Done

Current changes make sure that for text-based queries only grid view is
possible (both on Discover and as embeddable) and the app state will be
updated accordingly.

…eported issue (elastic#155938)

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Automated by
https://internal-ci.elastic.co/job/package_storage/job/sync-bundled-packages-job/job/main/3366/

Co-authored-by: apmmachine <infra-root+apmmachine@elastic.co>

…l Analytics (elastic#156012)

…ic#155942)

This PR fixes a few integration tests that were failing because the
ordering of the bulk creation of attachments isn't guaranteed. The
solution is to compare the results ignoring ordering within the arrays.

Fixes: elastic#154640

Flaky test runner results:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2178
🟢

## Summary

This PR adds a panel with 3 stages of ELSER trained model deployment:
- Model is not deployed (with button to initiate deployment)
- Model is deploying (polling status every 5 seconds)
- Model has deployed

Note that deploying the model does not start it; this will be
implemented in a follow-up PR.

The panel is discardable in the Pipelines screen but not discardable in
the pipeline configuration flyout.

…abstraction (elastic#155342)

## Summary

Abstract schema definitions for using Saved Objects with the content
management api. For most schema types, this will reduce creation to only
the attributes specific to a saved object. For Option types (create
options, update options, search options) the saved object api is more
complex and its likely that most SO types will only need to use a
portion of it. In these cases we recommend using the provided schema
definitions as a pattern for creating simpler schemas.

Follow up to - elastic#154985 - expresses
types in schema form

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

…nt_agent.js` CLI tool (elastic#155730)

## Summary

As a follow up to PR elastic#155455 : 

- `run_endpoint_agent` CLI: Removed internal code that handles the
creation of a VM and the enrollment of the agent with fleet and replaced
it with use of methods now found in `endpoint_host_services`
- created new service for managing agent download cache on local system
- enhanced `run_endpoint_agent` to use cached version of agent download,
and thus increase the performance of this tool

Closes elastic#154841

## Summary

This PR removes legacy field stats which were shown in field popover
before. They were based on loaded hits and were less precise than the
current default field stats (they are based now on 5000 documents per
shard sample).

Before (opt-in option):
<img width="500" alt="Screenshot 2023-04-21 at 14 26 57"
src="https://user-images.githubusercontent.com/1415710/233635136-ebc4017e-71c3-499d-96ac-544e26ea4b49.png">

After:
<img width="500" alt="Screenshot 2023-04-21 at 14 26 20"
src="https://user-images.githubusercontent.com/1415710/233635194-8c60fd05-5db6-40e0-abcd-672689932a83.png">

## Summary

When deleting a file user action the message displayed should be "<user>
removed file".

before
<img width="1059" alt="Screenshot 2023-04-27 at 17 08 14"
src="https://user-images.githubusercontent.com/1533137/234906123-48452699-a1ee-4452-b2ed-2ec3d4422ac3.png">


after
<img width="1063" alt="Screenshot 2023-04-27 at 17 07 56"
src="https://user-images.githubusercontent.com/1533137/234906310-4cc9c752-da76-441e-b3de-3d6194e821cb.png">

…lock alerts (elastic#155903)

## Summary

This PR accomplishes a few things:

1. Make sure eql building block alerts show up when redirecting directly
to the alerts page (demo of this fix below)
2. Bumps up the time window from 1 ms to 5 min, to make it easier to see
other alerts when clearing out the filters
3. Add unit tests for the `alert_details_redirect.tsx` component
4. Adds a cypress test to test the presence of `kibana.alert.url` in an
alert document and updates the config with the `publicBaseUrl` field
which is needed for the field to be present.

**Before the eql fix:**



https://user-images.githubusercontent.com/17211684/234636355-507b33fc-5211-4b02-9818-d1ba78fee115.mov



**After the eql fix:**


https://user-images.githubusercontent.com/17211684/234635657-bdbdc2cf-8a3e-4e5c-a14e-04f878f09e7b.mov

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

…te fields (elastic#155765)

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…ER API Endpoints (elastic#156020)

## Summary

Small PR to add the production model name to the `acceptableModelNames`
list that the Enteprise Search 1-Click deploy API endpoints use to check
to ensure we have a known, valid model name.

### Checklist
- [ ] [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

…stic#155853)

## Summary

This adds the ability to convert a native connector to a customized
connector.

---------

Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>

## Summary

Adds more info to key rotation API response in case of errors.
Follow up of elastic/pull/155252

### 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>

…ointer when actions deleted in yaml editor. (elastic#155952)

## Summary

Fixes an issue where the user could deselect all actions in a response
(which should not be allowed).

Also fixes an issue in the yaml editor if you delete all actions
(causing a null pointer exception).

### Checklist

Delete any items that are not applicable to this PR.

- [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]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [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] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [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))
- [x] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)

## Summary

Enables maintenance windows by setting the feature flag to `true`

…v item to "Search preview" (elastic#155795)

## Summary
* Rename nav item from "Preview" to "Search Preview"
* Update page Header to grey


### Screenshots

<img width="1728" alt="Search preview"
src="https://user-images.githubusercontent.com/55930906/234397633-003e4e99-680d-4531-8d94-528152fa2799.png">

<img width="1728" alt="Content"
src="https://user-images.githubusercontent.com/55930906/234397654-fb678a29-2c55-47d7-8d96-d8ce9f5164a2.png">

<img width="1728" alt="Connect"
src="https://user-images.githubusercontent.com/55930906/234397677-57823b14-16bf-44eb-9f01-eb6adca2a3fa.png">

…maller groups (elastic#155860)

## Summary


Re-grouping lens functional tests into 6 groups since 2 groups often
cross the 35+ min runtime. Also, we have retry in place so pipeline
might have +40 minutes run if any of test fails.

<img width="1354" alt="image"
src="https://user-images.githubusercontent.com/10977896/234843379-aec47a81-22dc-4ecf-aee5-b1d489b3b31f.png">

x-pack/test/functional/apps/lens/group1/config.ts 18m 42s
x-pack/test/functional/apps/lens/group2/config.ts 19m 26s
x-pack/test/functional/apps/lens/group3/config.ts 18m 26s
x-pack/test/functional/apps/lens/group4/config.ts 18m 40s
x-pack/test/functional/apps/lens/group5/config.ts 17m 55s
x-pack/test/functional/apps/lens/group6/config.ts 19m 24s

---------

Co-authored-by: Jon <jon@budzenski.me>

Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

## Summary

Fixes elastic#95657.

Updates the logic for `nodeBuilder` when passing an empty array to
`nodeBuilder.and`/`nodeBuilder.or` to actually return a `KueryNode`
instead of `undefined`.

### Checklist

- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [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

…155811)

## Summary

Resolves elastic#94356.

Fixes an issue with the _fields_for_wildcard API when the value for
`metaFields` advanced setting is set to a single value (e.g. `_source`).

### Checklist

- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [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

### Release note

Fixes an issue where having a single value for the advanced setting
`metaFields` would prevent refreshing a data view.

elastic#156003)

## Summary

issue: elastic#155995

Clean the deprecated SO client in the UI used in the
`useDashboardButtonHref` hook.
This is part of Serverless improvements.

This PR also changes the button to open the integrated Security
Dashboard viewer page, instead of the external Dashboards app.

### Changes:

- Changed SavedObject client direct query by the
`findDashboardsService`.
- Changed the link to the external Dashboards app by the Security
Dashboards page (including urlState parameters to preserve the time
range).
- Added "open in new tab" icon to the button
- Refactoring names to stay consistent

### Demo:



https://user-images.githubusercontent.com/17747913/234864463-75d08cf6-58d2-4a0d-b5fb-aae4e642b534.mov

## Summary

Moves a series of Lens components to an independent plugin for reuse in
the annotations library.


### 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
- [ ] remove mentions of Lens

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

…ude (elastic#156122)

## Summary

Defend for containers (policy UI) fix:
- Fix to unused selector badge showing when selector used as exclude

…lastic#155816)

## Summary

Unskip and fix flaky partial results test in search examples plugin.

Flaky test runner x100:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2172.

Fixes elastic#116038.

### Checklist

- [ ] ~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)~
- [ ]
~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials~
- [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
- [ ] ~Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard
accessibility](https://webaim.org/techniques/keyboard/))~
- [ ] ~Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))~
- [ ] ~If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~
- [ ] ~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))~
- [ ] ~This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)~

### 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)

**The API for the link definition is subject to change.** This PR
provides linking functionality and structure that will give solution
devs a starting point for side nav in their projects. The API uses
simple hrefs for now, because it's the easiest thing to start with.
Planning forward, we are thinking of a different navigation model that
separates nav structure from presentation of each nav item - this will
allow reuse of the structure without reusing the presentation.

## Isolated dependencies
In order for this component to be usable in `main`, a bit further work
is currently required in the ChromeStart service and the Serverless
plugin. These links are examples of a usable implementation that link to
a POC branch:
* Light mode for the side nav container:
tsullivan@0a32333cdf0
* Extensions to Serverless plugin and the ChromeStart service:
tsullivan@16b0aad610f

## Summary

Introduces a component to host the side navigation in Kibana. Solution
teams can insert their own content, and have other small options to
customize the presentation: see the storybook demos for more.

Closes elastic#154479
Closes elastic#154484
Closes elastic#154485
~~Closes elastic#154489
Closes elastic#154481
Closes elastic#154480
Closes elastic#154486
Closes elastic#154487

<img width="1462" alt="image"
src="https://user-images.githubusercontent.com/908371/233739506-7b88646e-3c19-44f0-afbf-ca1a23d32c57.png">

## Developer documentation

See the Storybook demos:
* run: `yarn storybook shared_ux`
* Find the `Chrome > Navigation` section in the Storybook app

### Checklist

Delete any items that are not applicable to this PR.
- [x] Home icon links to Project's "home" - or the customer user setting
- [x] Home icon shows loading indicator
- [x] All the Platform links navigate to the correct place
- ~~Platform links are not shown if the underlying plugin is disabled~~
- [x] Nav items define their links using `href` only
- [x] All href links work
- [x] Nav menu item to link to Cloud deployment
- [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] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] 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))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

Generated by
https://buildkite.com/elastic/kibana-api-docs-daily/builds/321

…astic#155521)

## Summary

Fixes elastic#152719

This PR cleans up the incomplete state for the specific referenced
column on sub function change.


### Checklist

Delete any items that are not applicable to this PR.

- [ ] 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)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] 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))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.

When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:

| Risk | Probability | Severity | Mitigation/Notes |

|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces—unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes—Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |


### 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)

---------

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

)

## Summary

As described in elastic#152318, we
noticed that building block alerts were not highlighted anymore after
the migration to the new alerts table.

A preferred implementation of building block alert highlighting would
follow the [`EUIDataGrid` approach of row
highlighting](https://eui.elastic.co/#/tabular-content/data-grid-style-display#grid-row-classes).
The `DataGrid` allows you to pass custom CSS class names for each row
(`gridStyle.rowClasses`). That would allow us to highlight table rows
with building block alerts.

However, without access to the underlying data, we would not be able
generate the correct `rowClasses` for rows with building block alerts.
So simply passing `gridStyle.rowClasses` to the `AlertsStateTable` was
not an option.

Therefore in this PR we're introducing a new prop on the `AlertsTable`,
the `highlightedRowMapper`. It's a callback function that receives the
alert data and when it returns true, that row will be highlighted.

This allows for highlighting of rows from the outside without exposing
too many details about the underlying data structures.

**Screenshot of the alerts table with a highlightedRowMapper that
highlights building block alerts**

<img width="1259" alt="Screenshot 2023-04-21 at 13 03 54"
src="https://user-images.githubusercontent.com/68591/233620704-a56204c0-e285-4289-897a-58481f440446.png">

### Additional notes

- Since the alerts table has default grid styles, it allows to pass
`gridStyle` and it computes its own `rowClasses` for "active row"
highlighting, the logic for merging all those styles looks intimidating.
I tried my best to comment that part of code to make it clear why the
merges are necessary and how they work.
- While working on the issue, I noticed that active rows are not
highlighted anymore (related bug:
elastic#155487). The changes in this PR
fix that behaviour as well as you can see in the screenshot below:

<img width="936" alt="Screenshot 2023-04-21 at 13 04 15"
src="https://user-images.githubusercontent.com/68591/233620752-d752dada-9c97-4f00-933a-5425e19a5793.png">

### 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: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

…928' into logs-onboarding-select-logs-154941

## Summary

Add automated tests via Cypress for MongoDB and Web Crawler happy paths.

Tests are quite basic and covers only adding simple one time sync paths.
Fill in the `cypress.env.json` with the credentials before running.
Mongo specs will run only against a local environment (via `./cypress.sh
dev`) as connector has to be running locally as well.


### 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: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

When splitting the query to mobile transactions main statistics, the
sessions were left in the errors query and should have been retrieved in
the transactions events. This PR fix this issue

…lastic#156146)

## Summary

Fixes elastic#155937

For viewer user tooltip will be displayed and button is disabled.

Also fixed loading position for manual test run loader.

<img width="1770" alt="image"
src="https://user-images.githubusercontent.com/3505601/235106034-7e758a5d-7291-47a2-8a46-2327b367e4a8.png">

Exposes a `/related` endpoint that can be called to retrieve any
supported asset relationship (`ancestors|descendants|references`).

Note that this is a first draft to get a functioning endpoint available.
Further optimizations (performances, typing..) will be implemented as
follow ups or when we get feedback from actual use cases.

Follow ups:
- We're currently doing two sequential requests to retrieve the related
assets, one for the _directly_ referenced of the primary (in
`assets.children|parents..`) and another for _indirectly_ referenced
that lists the primary in `asset.children|parents...`. These two
predicates can be packed in a single query
- The size is difficult to enforce at the query level if a `type` filter
is provided. If we're looking at a `depth > 1` and we apply the size
limit to the queries at `depth < maxDistance` we may miss edges to the
requested type. Similarly the `type` filter can't be enforced at `depth
< maxDistance`

To do:

- [x] Add filtering by type
- [ ] ~Limit by size~
- [x] Add sample assets which use references
- [x] Add integration tests that validate each type of relation query
- [x] Add documentation and sample requests/responses for each relation
type
- [x] Handle circular references. In what situations can that happens,
references ?

Closes elastic#153471
Closes elastic#153473
Closes elastic#153482

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: klacabane <kevin.lacabane@elastic.co>
Co-authored-by: Kevin Lacabane <klacabane@gmail.com>
Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>

…55974)

This PR fixes elastic#150249, an occasional flaky test of Discover's saved search tagging
Flaky test runner: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2179

…typing (elastic#156002)

Fixes some misc bugs with the new configurable fields inputs

- `EuiFieldNumber` inputs could not be `null`, but we sometimes want
`null`. I switched these back to `EuiFieldText` and added integer
validations.
- Fields were still being saved as strings even if they should be
integers, so enforced a type check to make sure the expected type is
saved.

The new function `validateConnectorConfiguration` can also easily be
expanded to use the new validations.

…55961)

…ect-logs-154941

This PR separates the persisted SO attributes from the fields received
in the HTTP API requests.

This is to address step 2 in preparing our HTTP routes as versioned.

Issue: elastic#153726

This PR encompasses a few PRs here which have been reviewed individually
by the cases team members:

elastic#155325 - User actions
elastic#155440 - Attachments
elastic#155444 - Configure, Connector
Mappings
elastic#155277 - Cases

The large number of files is because of renaming some types throughout
the frontend code. There shouldn't be many functionality changes, mostly
just type changes.

---------

Co-authored-by: Christos Nasikas <christos.nasikas@elastic.co>
Co-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com>

## Summary

Fix a bug found by @markov00 

When a cell value contains the csvSeparator char (by default `,`) the
text was not escaped correctly. This PR fixes this by wrapping the value
in quotes (if enabled).


### Checklist

Delete any items that are not applicable to this PR.

- [ ] 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)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] 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))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.

When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:

| Risk | Probability | Severity | Mitigation/Notes |

|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces—unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes—Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) |


### 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)

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

Automated by
https://internal-ci.elastic.co/job/package_storage/job/sync-bundled-packages-job/job/main/3387/

Co-authored-by: apmmachine <infra-root+apmmachine@elastic.co>

Closes elastic#155777

## Summary

The `"replaces panel with incoming embeddable if id matches existing
panel"` test was **not** the flaky one, even though it was the one that
showed the failure; it was actually one of the previous `"pulls state
<...>"` tests that was failing, which was pretty confusing to catch 🤦

Basically, because we are [running the unsaved changes check on load
now](elastic#155648), depending on the
timing of the `debounce` on the `checkForUnsavedChangesSubject$`
subscription it would sometimes run for the `"pulls state <...>"` tests
(but not always) - so whenever it **would** run, because the mocked
`loadDashboardStateFromSavedObject` was only returning a partial
Dashboard input, this would result in trying to get the property of
`undefined` when checking for filter changes, panel changes, etc.

This is fixed by ensuring that the `loadDashboardStateFromSavedObject`
returns a complete Dashboard input, with all the required keys, for all
of the relevant tests. Note that, since you can't test Jest unit tests
using the flaky test runner, I was able to run it multiple times by
surrounding all the tests with the following in order to ensure that it
was no longer flaky:

```typescript
for (const i of Array(x)
  .fill(null)
  .map((_, i) => i)) {
  describe(`test run ${i}`, () => {
    <...> // all the tests go here
  });
};
```

I did this with `x = 200`, and the entire test suite passed 200 times in
a row 👍

### 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


### 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)

…y pair fails (elastic#156144)

## Summary

Responds with a generic error message for the rotate key pair API,
instead of a trace message of where the error was generated.

We log the detailed errors and this is to avoid a chance of any
sensitive data (key generation details) being exposed through the API
response.

follow up of elastic/pull/155864

### 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

…lastic#155897)

## Summary

This PR fixes issues with lens visualization in case view page for
comment and description.

Fixes: elastic#155631

**Description:**


https://user-images.githubusercontent.com/117571355/234856964-52bc479e-73bb-48d1-9b23-9e78e3452f00.mov

**Comment:**


https://user-images.githubusercontent.com/117571355/234858215-feaac6c7-5579-4a00-bb97-00e0b23f5cfe.mov

### 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

**Flakey Test runner:**
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2182

Next one after update:
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2183

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

## Summary

A minor copy edit to the Create Search Application flyout, as requested
[here](https://github.com/elastic/kibana/pull/155649/files#r1177950465).

Per the thread in the request, the popover is changed but the callout
remains the same.
<img width="457" alt="image"
src="https://user-images.githubusercontent.com/63422879/235157710-6463ca4c-fa92-4d1a-af22-9e2a507f3176.png">
<img width="631" alt="Screenshot 2023-04-28 at 8 53 55 AM"
src="https://user-images.githubusercontent.com/63422879/235153128-e49933a8-91a5-4365-bbd5-f0a1d4b52579.png">

## Summary

PR elastic#154436 changed the memoization
function (my fault 🙂) and that caused the attachments to rerender each
time a user does an action in cases. This PR fixes this issue.

**Before:**



https://user-images.githubusercontent.com/7871006/235171360-62be773f-8317-4762-9f14-0310d3825a1e.mov

**After:**



https://user-images.githubusercontent.com/7871006/235171429-5e06f9c4-9c0a-4148-8580-bde2360169af.mov



### 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)

…category (elastic#155935)

## Summary

Summarize your PR. If it involves visual changes include a screenshot or
gif.

Add `Advanced Analytics (UEBA)` subcategory under Security

* elastic/package-spec#499

### Checklist

Delete any items that are not applicable to this PR.

- [ ] 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)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] 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))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)


### Risk Matrix

Delete this section if it is not applicable to this PR.

(This PR doesn't add new features, thus deleting the table in the
boilerplate)


### 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)

…t. (elastic#156186)

## Summary

Changes the default trial offset used to display the Drift chat
integration from 60 to 90 days.


### Checklist
N/A

### Risk Matrix
N/A

### For maintainers
N/A

Generated by
https://buildkite.com/elastic/kibana-api-docs-daily/builds/322

Generated by
https://buildkite.com/elastic/kibana-api-docs-daily/builds/323

…tting Unified Histogram state (elastic#155967)

## Summary

This PR fixes an issue where resetting a saved search would not fully
reset the Unified Histogram state. The issue was caused by multiple
state values changing in quick succession which resulted in some state
getting overwritten, so I've updated `use_discover_state` to batch state
updates and improve diffing when state changes.

Fixes elastic#151395.

### Checklist

- [ ] ~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)~
- [ ]
~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials~
- [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
- [ ] ~Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard
accessibility](https://webaim.org/techniques/keyboard/))~
- [ ] ~Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))~
- [ ] ~If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)~
- [ ] ~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))~
- [ ] ~This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)~

### 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)

Generated by
https://buildkite.com/elastic/kibana-api-docs-daily/builds/324

> Derived from elastic#153274
> Builds upon elastic#155582

## Summary

This PR creates the Serverless Observability plugin, based on the work
from elastic#153274:

- creates the plugin,
- adds API to hide the solution navigation from Enterprise Search,
- calls that API if the chrome style is `project`.

<img width="1610" alt="Screenshot 2023-04-27 at 5 03 44 PM"
src="https://user-images.githubusercontent.com/297604/234990765-d6770650-41b3-4e94-ad7f-c6a22778d39a.png">

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

…ens and In Browsers with High Zoom (elastic#155817)

Fixes elastic/eui#6702

Pinging @elastic/eui-team for visibility

## Summary

### ✨ What's the problem?
A user submitted an issue where they were unable to use the main
collapsible nav when their browser was zoomed in at 400% for
accessibility. The nav items weren't visible and could not be interacted
with at this level.

<img width="400" alt="image"
src="https://user-images.githubusercontent.com/40739624/234444373-b9539160-a069-4e4f-9bdc-c01a9405f11c.png">

### ✨ What changed?
When the container for the collapsible nav has a `max-height` of `15em`,
overflow and additional flex properties are used to allow the nav groups
to be traversed.


https://user-images.githubusercontent.com/40739624/234444539-72e2d499-94b3-4b0b-ba08-d17b12afa15c.mov


### ✨ QA
View the Kibana homepage and set the Zoom on your browser to 400%. This
will need to be done in a relatively small window (like the one on your
computer itself, not an external monitor). Open the main navigation menu
on the left. You should be able to navigate all links in menu with both
keyboard and by scrolling the sections.

### Checklist

Delete any items that are not applicable to this PR.

- [x] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/))
- [x] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))
- [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))


### 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)

---------

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Cee Chen <549407+cee-chen@users.noreply.github.com>

…ate (elastic#155706)

## Summary

* Generate Azure integration URL instead of hardcoding it 

![Apr-26-2023
14-32-40](https://user-images.githubusercontent.com/1490444/234575705-6ff288c3-5691-4b66-af6c-cf1383f3399b.gif)

* Fix flyout showing callout when loading

![Apr-26-2023
14-25-10](https://user-images.githubusercontent.com/1490444/234574219-ed25f37b-0206-49d6-bc81-8d75cf023e64.gif)


### 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

…tic#156080)

## Summary

We're adding action buttons to the ELSER model deployment panel,
specifically to the state where the trained model has been downloaded
but not started yet. The user has two options here:
- Start the model (synchronously) with a basic configuration using the
"Start single-threaded" button
- Navigate to the Trained Models page and fine-tune the model deployment
with the "Fine-tune performance" button

In addition a 4th state of the panel is being introduced: the ELSER
model has started.


![ELSER_start](https://user-images.githubusercontent.com/14224983/234971172-a99917dd-ec55-4df3-acd1-a6b390262104.gif)


### 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>