Merge branch '8.16' into 8.16-eui-backport

docs/user/ml/index.asciidoc

@@ -51,7 +51,8 @@ information, refer to {ml-docs}/ml-limitations.html[{ml-cap}].
 
 preview::[]
 
-You can find the data drift view in **{ml-app}** > *{data-viz}* in {kib}. 
+You can find the data drift view in **{ml-app}** > *{data-viz}* in {kib} or by using
+the <<kibana-navigation-search,global search field>>. 
 The data drift view shows you the differences in each field for two 
 different time ranges in a given {data-source}. The view helps you to visualize 
 the changes in your data over time and enables you to understand its behavior 
@@ -167,7 +168,7 @@ It makes it easy to find and investigate causes of unusual spikes or drops by us
 Examine the histogram chart of the log rates for a given {data-source}, and find the reason behind a particular change possibly in millions of log events across multiple fields and values.
 
 You can find log rate analysis embedded in multiple applications.
-In {kib}, you can find it under **{ml-app}** > **AIOps Labs** where you can select the {data-source} or saved search that you want to analyze.
+In {kib}, you can find it under **{ml-app}** > **AIOps Labs** or by using the <<kibana-navigation-search,global search field>>. Here, you can select the {data-source} or saved search that you want to analyze.
 
 [role="screenshot"]
 image::user/ml/images/ml-log-rate-analysis-before.png[Log event histogram chart]
@@ -201,8 +202,8 @@ displays them together with a chart that shows the distribution of each category
 and an example document that matches the category.
 //end::log-pattern-analysis-intro[]
 
-You can find log pattern analysis under **{ml-app}** > **AIOps Labs** where you 
-can select the {data-source} or saved search that you want to analyze, or in 
+You can find log pattern analysis under **{ml-app}** > **AIOps Labs** or by using the <<kibana-navigation-search,global search field>>. 
+Here, you can select the {data-source} or saved search that you want to analyze, or in 
 **Discover** as an available action for any text field.
 
 [role="screenshot"]
@@ -226,8 +227,8 @@ Change point detection uses the
 to detect distribution changes, trend changes, and other statistically 
 significant change points in a metric of your time series data.
 
-You can find change point detection under **{ml-app}** > **AIOps Labs** where 
-you can select the {data-source} or saved search that you want to analyze.
+You can find change point detection under **{ml-app}** > **AIOps Labs** or by using the <<kibana-navigation-search,global search field>>. 
+Here, you can select the {data-source} or saved search that you want to analyze.
 
 [role="screenshot"]
 image::user/ml/images/ml-change-point-detection.png[Change point detection UI]

packages/content-management/table_list_view_table/src/table_list_view.test.tsx

@@ -242,8 +242,8 @@ describe('TableListView', () => {
       const updatedAtValues: Moment[] = [];
 
       const updatedHits = hits.map(({ id, attributes, references }, i) => {
-        const updatedAt = new Date(new Date().setDate(new Date().getDate() - (7 + i)));
-        updatedAtValues.push(moment(updatedAt));
+        const updatedAt = moment().subtract(7 + i, 'days');
+        updatedAtValues.push(updatedAt);
 
         return {
           id,

x-pack/plugins/cloud_security_posture/public/common/constants.ts

@@ -263,9 +263,7 @@ The runtime mappings are used to prevent filtering out the data when any of thes
 TODO: Remove the fields below once they are mapped as Keyword in the Third Party integrations, or remove
 the fields from the runtime mappings if they are removed from the Data Table.
 */
-export const CDR_VULNERABILITY_DATA_TABLE_RUNTIME_MAPPING_FIELDS: string[] = [
-  VULNERABILITY_FIELDS.VENDOR,
-];
+export const CDR_VULNERABILITY_DATA_TABLE_RUNTIME_MAPPING_FIELDS: string[] = [];
 export const CDR_MISCONFIGURATION_DATA_TABLE_RUNTIME_MAPPING_FIELDS: string[] = [
   'rule.benchmark.rule_number',
   'rule.section',
@@ -279,9 +277,7 @@ to prevent filtering out the data when grouping by the key field.
 TODO: Remove the fields below once they are mapped as Keyword in the Third Party integrations, or remove
 the fields from the runtime mappings if they are removed from the Data Table.
 */
-export const CDR_VULNERABILITY_GROUPING_RUNTIME_MAPPING_FIELDS: Record<string, string[]> = {
-  [VULNERABILITY_GROUPING_OPTIONS.CLOUD_ACCOUNT_NAME]: [VULNERABILITY_FIELDS.CLOUD_PROVIDER],
-};
+export const CDR_VULNERABILITY_GROUPING_RUNTIME_MAPPING_FIELDS: Record<string, string[]> = {};
 export const CDR_MISCONFIGURATION_GROUPING_RUNTIME_MAPPING_FIELDS: Record<string, string[]> = {
   [FINDINGS_GROUPING_OPTIONS.ORCHESTRATOR_CLUSTER_NAME]: ['orchestrator.cluster.name'],
   [FINDINGS_GROUPING_OPTIONS.CLOUD_ACCOUNT_NAME]: ['cloud.account.name'],

x-pack/plugins/security_solution/public/entity_analytics/components/entity_store/components/dashboard_panels.tsx

@@ -55,7 +55,7 @@ const EntityStoreDashboardPanelsComponent = () => {
 
   const { mutate: initRiskEngine } = useInitRiskEngineMutation();
 
-  const callouts = entityStore.errors.map((err, i) => (
+  const callouts = entityStore.errors.map((err) => (
     <EuiCallOut
       title={
         <FormattedMessage

x-pack/plugins/security_solution/public/entity_analytics/pages/entity_store_management_page.tsx

@@ -252,6 +252,21 @@ export const EntityStoreManagementPage = () => {
     stopEntityEngineMutation.isLoading ||
     deleteEntityEngineMutation.isLoading;
 
+  const callouts = entityStoreStatus.errors.map((error) => (
+    <EuiCallOut
+      title={
+        <FormattedMessage
+          id="xpack.securitySolution.entityAnalytics.entityStoreManagementPage.errors.title"
+          defaultMessage={'An error occurred during entity store resource initialization'}
+        />
+      }
+      color="danger"
+      iconType="alert"
+    >
+      <p>{error.message}</p>
+    </EuiCallOut>
+  ));
+
   return (
     <>
       <EuiPageHeader
@@ -300,6 +315,39 @@ export const EntityStoreManagementPage = () => {
         <FileUploadSection />
         <EuiFlexItem grow={2}>
           <EuiFlexGroup direction="column">
+            {initEntityEngineMutation.isError && (
+              <EuiCallOut
+                title={
+                  <FormattedMessage
+                    id="xpack.securitySolution.entityAnalytics.entityStoreManagementPage.errors.initErrorTitle"
+                    defaultMessage={'There was a problem initializing the entity store'}
+                  />
+                }
+                color="danger"
+                iconType="alert"
+              >
+                <p>
+                  {(initEntityEngineMutation.error as { body: { message: string } }).body.message}
+                </p>
+              </EuiCallOut>
+            )}
+            {deleteEntityEngineMutation.isError && (
+              <EuiCallOut
+                title={
+                  <FormattedMessage
+                    id="xpack.securitySolution.entityAnalytics.entityStoreManagementPage.errors.deleteErrorTitle"
+                    defaultMessage={'There was a problem deleting the entity store'}
+                  />
+                }
+                color="danger"
+                iconType="alert"
+              >
+                <p>
+                  {(deleteEntityEngineMutation.error as { body: { message: string } }).body.message}
+                </p>
+              </EuiCallOut>
+            )}
+            {callouts}
             <WhatIsAssetCriticalityPanel />
             {!isEntityStoreFeatureFlagDisabled && canDeleteEntityEngine && <ClearEntityDataPanel />}
           </EuiFlexGroup>