Merge branch 'main' into kbn-158918-fix-saved-object-api-integration

docs/CHANGELOG.asciidoc

@@ -49,6 +49,36 @@ Review important information about the {kib} 8.x releases.
 
 Review the following information about the {kib} 8.8.2 release.
 
+[float]
+[[known-issues-8.8.2]]
+=== Known issues
+
+// tag::known-issue-161249[]
+[discrete]
+.Kibana can run out of memory during an upgrade when there are many {fleet} agent policies.
+[%collapsible]
+====
+*Details* +
+Due to a schema version update, during {fleet} setup in 8.8.x, all agent policies are being queried and deployed. 
+This action triggers a lot of queries to the Elastic Package Registry (EPR) to fetch integration packages.  As a result,
+there is an increase in Kibana's resident memory usage (RSS). 
+
+*Impact* +
+Because the default batch size of `100` for schema version upgrade of {fleet} agent policies is too high, this can 
+cause Kibana to run out of memory during an upgrade.  For example, we have observed 1GB Kibana instances run
+out of memory during an upgrade when there were 20 agent policies with 5 integrations in each. 
+
+*Workaround* +
+Two workaround options are available:
+
+* Increase the Kibana instance size to 2GB. So far, we are not able to reproduce the issue with 2GB instances.
+* Set `xpack.fleet.setup.agentPolicySchemaUpgradeBatchSize` to `2` in the `kibana.yml` and restart the Kibana instance(s).
+
+In 8.9.0, we are addressing this by changing the default batch size to `2`.
+
+====
+// end::known-issue-161249[]
+
 [float]
 [[fixes-v8.8.2]]
 === Bug Fixes
@@ -106,6 +136,32 @@ Review the following information about the {kib} 8.8.1 release.
 [[known-issues-8.8.1]]
 === Known issues
 
+// tag::known-issue-161249[]
+[discrete]
+.Kibana can run out of memory during an upgrade when there are many {fleet} agent policies.
+[%collapsible]
+====
+*Details* +
+Due to a schema version update, during {fleet} setup in 8.8.x, all agent policies are being queried and deployed. 
+This action triggers a lot of queries to the Elastic Package Registry (EPR) to fetch integration packages.  As a result,
+there is an increase in Kibana's resident memory usage (RSS). 
+
+*Impact* +
+Because the default batch size of `100` for schema version upgrade of {fleet} agent policies is too high, this can 
+cause Kibana to run out of memory during an upgrade.  For example, we have observed 1GB Kibana instances run
+out of memory during an upgrade when there were 20 agent policies with 5 integrations in each. 
+
+*Workaround* +
+Two workaround options are available:
+
+* Increase the Kibana instance size to 2GB. So far, we are not able to reproduce the issue with 2GB instances.
+* Set `xpack.fleet.setup.agentPolicySchemaUpgradeBatchSize` to `2` in the `kibana.yml` and restart the Kibana instance(s).
+
+In 8.9.0, we are addressing this by changing the default batch size to `2`.
+
+====
+// end::known-issue-161249[]
+
 // tag::known-issue-159807[]
 [discrete]
 .Memory leak in {fleet} audit logging.
@@ -198,6 +254,32 @@ Review the following information about the {kib} 8.8.0 release.
 [[known-issues-8.8.0]]
 === Known issues
 
+// tag::known-issue-161249[]
+[discrete]
+.Kibana can run out of memory during an upgrade when there are many {fleet} agent policies.
+[%collapsible]
+====
+*Details* +
+Due to a schema version update, during {fleet} setup in 8.8.x, all agent policies are being queried and deployed. 
+This action triggers a lot of queries to the Elastic Package Registry (EPR) to fetch integration packages.  As a result,
+there is an increase in Kibana's resident memory usage (RSS). 
+
+*Impact* +
+Because the default batch size of `100` for schema version upgrade of {fleet} agent policies is too high, this can 
+cause Kibana to run out of memory during an upgrade.  For example, we have observed 1GB Kibana instances run
+out of memory during an upgrade when there were 20 agent policies with 5 integrations in each. 
+
+*Workaround* +
+Two workaround options are available:
+
+* Increase the Kibana instance size to 2GB. So far, we are not able to reproduce the issue with 2GB instances.
+* Set `xpack.fleet.setup.agentPolicySchemaUpgradeBatchSize` to `2` in the `kibana.yml` and restart the Kibana instance(s).
+
+In 8.9.0, we are addressing this by changing the default batch size to `2`.
+
+====
+// end::known-issue-161249[]
+
 // tag::known-issue-158940[]
 [discrete]
 .Failed upgrades to 8.8.0 can cause bootlooping and data loss
@@ -221,6 +303,7 @@ The 8.8.1 release includes in {kibana-pull}158940[a fix] for this problem. Custo
 *Details* +
 {fleet} introduced audit logging for various CRUD (create, read, update, and delete) operations in version 8.8.0.
 While audit logging is not enabled by default, we have identified an off-heap memory leak in the implementation of {fleet} audit logging that can result in poor {kib} performance, and in some cases {kib} instances being terminated by the OS kernel's oom-killer. This memory leak can occur even when {kib} audit logging is not explicitly enabled (regardless of whether `xpack.security.audit.enabled` is set in the `kibana.yml` settings file).
+
 *Impact* +
 The version 8.8.2 release includes in {kibana-pull}159807[a fix] for this problem. If you are using {fleet} integrations
 and {kib} audit logging in version 8.8.0 or 8.8.1, you should upgrade to 8.8.2 or above to obtain the fix.

docs/management/cases/manage-cases.asciidoc

@@ -1,6 +1,11 @@
 [[manage-cases]]
 == Open and manage cases
 
+:frontmatter-description: Create a case then add files, visualizations, and user notifications.
+:frontmatter-tags-products: [kibana] 
+:frontmatter-tags-content-type: [how-to] 
+:frontmatter-tags-user-goals: [analyze]
+
 preview::[]
 
 [[open-case]]
@@ -72,8 +77,9 @@ go back to your case.
 
 . Click *Add Comment* to add the visualization to your case.
 
-After a visualization has been added to a case, you can modify or interact with
-it by clicking the *Open Visualization* option in the comment menu.
+Alternatively, while viewing a <<dashboard,dashboard>> you can open a panel's menu then click *More > Add to existing case* or *More > Add to new case*.
+
+After a visualization has been added to a case, you can modify or interact with it by clicking the *Open Visualization* option in the case's comment menu.
 
 [[add-case-notifications]]
 === Add email notifications

docs/management/connectors/action-types/email.asciidoc

@@ -8,11 +8,8 @@
 :frontmatter-tags-content-type: [how-to] 
 :frontmatter-tags-user-goals: [configure]
 
-The email connector uses the SMTP protocol to send mail messages, using an 
-integration of https://nodemailer.com/[Nodemailer]. An exception is Microsoft 
-Exchange, which uses HTTP protocol for sending emails, 
-https://docs.microsoft.com/en-us/graph/api/user-sendmail[Send mail]. Email 
-message text is sent as both plain text and html text.
+The email connector uses the SMTP protocol to send mail messages.
+Email message text is sent as both plain text and html text.
 
 [NOTE]
 ====
@@ -214,11 +211,10 @@ settings. You can set configurations that apply to all your connectors or use
 [[configuring-email]]
 === Configure email accounts for well-known services
 
-The email connector can send email using many popular SMTP email services and 
-the Microsoft Exchange Graph API.
+The email connector uses an integration of https://nodemailer.com/[Nodemailer] to send email from many popular SMTP email services.
+For Microsoft Exchange email, it uses the Microsoft Graph API.
 
-For more information about configuring the email connector to work with 
-different email systems, refer to:
+To configure the email connector to work with common email systems, refer to:
 
 * <<elasticcloud>>
 * <<gmail>>
@@ -337,7 +333,7 @@ at AWS.
 [[exchange-basic-auth]]
 ==== Sending email from Microsoft Exchange with Basic Authentication
 
-deprecated:[This Microsoft Exchange configuration is deprecated in 7.16.0, and will be removed later, because Microsoft is deprecating https://docs.microsoft.com/en-us/lifecycle/announcements/exchange-online-basic-auth-deprecated [Basic Authentication]:
+deprecated:[7.16.0,"This Microsoft Exchange configuration is deprecated and will be removed later because Microsoft is deprecating basic authentication."]
 
 [source,text]
 --------------------------------------------------
@@ -365,6 +361,8 @@ https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-client
 [[exchange]]
 ==== Sending email from Microsoft Exchange with OAuth 2.0
 
+NOTE: The email connector uses Microsoft Graph REST API v1.0, in particular the https://docs.microsoft.com/en-us/graph/api/user-sendmail[sendMail] endpoint. It supports only the https://learn.microsoft.com/en-us/graph/deployments#microsoft-graph-and-graph-explorer-service-root-endpoints[Microsoft Graph global service] root endpoint (`https://graph.microsoft.com`).
+
 Before you create an email connector for Microsoft Exchange, you must create and 
 register the client integration application on the 
 https://go.microsoft.com/fwlink/?linkid=2083908[Azure portal]:

docs/user/alerting/alerting-troubleshooting.asciidoc

@@ -189,12 +189,30 @@ In addition to the above methods, refer to the following approaches and common i
 * <<event-log-index,Querying event log index>>
 * <<testing-connectors,Testing connectors using {connectors-ui} UI and the `kbn-action` tool>>
 
+[discrete]
+[[alerting-kibana-throttle]]
+==== Temporarily throttle all tasks
+
+If cluster performance becomes degraded from excessive or expensive rules and {kib} is sluggish or unresponsive, you can temporarily reduce load to the Task Manager by updating its <<task-manager-settings-kb,settings>>:
+
+[source,txt]
+--------------------------------------------------
+xpack.task_manager.max_workers: 1
+xpack.task_manager.poll_interval: 1h
+--------------------------------------------------
+
+[WARNING]
+====
+This approach should be used only temporarily as a last resort to restore function to {kib} when it is unresponsive and attempts to identify and <<controlling-rules,snooze or disable>> slow-running rules have not fixed the situation.
+It severely throttles all background tasks, not just those relating to {alert-features}. The task manager will run only one task at a time and will look for more work each hour.
+====
+
 [discrete]
 [[alerting-limitations]]
 === Limitations
 
 The following limitations and known problems apply to the {version} release of
-the {kib} {alert-features}. 
+the {kib} {alert-features}:
 
 [discrete]
 ==== Alert visibility
@@ -208,3 +226,4 @@ the `consumer` property.
 include::troubleshooting/alerting-common-issues.asciidoc[]
 include::troubleshooting/event-log-index.asciidoc[]
 include::troubleshooting/testing-connectors.asciidoc[]
+

package.json

@@ -114,7 +114,7 @@
     "@emotion/serialize": "^1.1.2",
     "@emotion/server": "^11.11.0",
     "@emotion/styled": "^11.11.0",
-    "@grpc/grpc-js": "^1.6.7",
+    "@grpc/grpc-js": "^1.6.8",
     "@hapi/accept": "^5.0.2",
     "@hapi/boom": "^9.1.4",
     "@hapi/cookie": "^11.0.2",
@@ -756,13 +756,14 @@
     "@mapbox/geojson-rewind": "^0.5.0",
     "@mapbox/mapbox-gl-draw": "1.3.0",
     "@mapbox/mapbox-gl-rtl-text": "0.2.3",
+    "@mapbox/mapbox-gl-supported": "2.0.1",
     "@mapbox/vector-tile": "1.3.1",
     "@opentelemetry/api": "^1.1.0",
-    "@opentelemetry/api-metrics": "^0.30.0",
-    "@opentelemetry/exporter-metrics-otlp-grpc": "^0.30.0",
-    "@opentelemetry/exporter-prometheus": "^0.30.0",
+    "@opentelemetry/api-metrics": "^0.31.0",
+    "@opentelemetry/exporter-metrics-otlp-grpc": "^0.34.0",
+    "@opentelemetry/exporter-prometheus": "^0.31.0",
     "@opentelemetry/resources": "^1.4.0",
-    "@opentelemetry/sdk-metrics-base": "^0.30.0",
+    "@opentelemetry/sdk-metrics-base": "^0.31.0",
     "@opentelemetry/semantic-conventions": "^1.4.0",
     "@reduxjs/toolkit": "1.7.2",
     "@slack/webhook": "^5.0.4",
@@ -878,7 +879,7 @@
     "luxon": "^2.5.2",
     "lz-string": "^1.4.4",
     "mapbox-gl-draw-rectangle-mode": "1.0.4",
-    "maplibre-gl": "2.1.9",
+    "maplibre-gl": "3.1.0",
     "markdown-it": "^12.3.2",
     "md5": "^2.1.0",
     "mdast-util-to-hast": "10.0.1",

packages/core/rendering/core-rendering-server-internal/src/views/template.tsx

@@ -54,8 +54,8 @@ export const Template: FunctionComponent<Props> = ({
         <meta name="color-scheme" content="light dark" />
         {/* Inject EUI reset and global styles before all other component styles */}
         <meta name={EUI_STYLES_GLOBAL} />
-        <Styles darkMode={darkMode} stylesheetPaths={stylesheetPaths} />
         <meta name="emotion" />
+        <Styles darkMode={darkMode} stylesheetPaths={stylesheetPaths} />
         {/* Inject stylesheets into the <head> before scripts so that KP plugins with bundled styles will override them */}
         <meta name="add-styles-here" />
         <meta name="add-scripts-here" />

packages/kbn-storybook/templates/index.ejs

@@ -15,6 +15,7 @@
     <meta name="viewport" content="width=device-width, initial-scale=1" />
 
     <meta name="eui-global" />
+    <meta name="emotion" />
 
     <!-- Added for Kibana shared dependencies -->
     <script>
@@ -26,8 +27,6 @@
     <link id="eui-theme-css" href="kbn-ui-shared-deps-npm.v8.light.css" rel="stylesheet" />
     <!--                                      -->
 
-    <meta name="emotion" />
-
     <% if (typeof headHtmlSnippet !== 'undefined') { %> <%= headHtmlSnippet %> <% } %> <%
     htmlWebpackPlugin.files.css.forEach(file => { %>
     <link href="<%= file %>" rel="stylesheet" />

packages/shared-ux/chrome/navigation/src/ui/components/navigation_section_ui.tsx

@@ -124,6 +124,7 @@ export const NavigationSectionUI: FC<Props> = ({ navNode, items = [] }) => {
       id={id}
       title={title}
       iconType={icon}
+      iconSize={'m'}
       isCollapsible={true}
       initialIsOpen={isActive}
       onToggle={(isOpen) => {