Merge branch 'main' into 126386-add-last-seen-reporting

.buildkite/ftr_configs.yml

@@ -146,6 +146,7 @@ enabled:
   - x-pack/test/functional/apps/cross_cluster_replication/config.ts
   - x-pack/test/functional/apps/dashboard/group1/config.ts
   - x-pack/test/functional/apps/dashboard/group2/config.ts
+  - x-pack/test/functional/apps/dashboard/group3/config.ts
   - x-pack/test/functional/apps/data_views/config.ts
   - x-pack/test/functional/apps/dev_tools/config.ts
   - x-pack/test/functional/apps/discover/config.ts
@@ -245,3 +246,9 @@ enabled:
   - x-pack/test/ui_capabilities/spaces_only/config.ts
   - x-pack/test/upgrade_assistant_integration/config.js
   - x-pack/test/usage_collection/config.ts
+  - x-pack/test/performance/journeys/ecommerce_dashboard/config.ts
+  - x-pack/test/performance/journeys/flight_dashboard/config.ts
+  - x-pack/test/performance/journeys/login/config.ts
+  - x-pack/test/performance/journeys/many_fields_discover/config.ts
+  - x-pack/test/performance/journeys/promotion_tracking_dashboard/config.ts
+  - x-pack/test/performance/journeys/web_logs_dashboard/config.ts

.buildkite/scripts/steps/functional/performance_playwright.sh

@@ -24,24 +24,20 @@ for i in "${journeys[@]}"; do
     echo "JOURNEY[${i}] is running"
 
     export TEST_PERFORMANCE_PHASE=WARMUP
-    export ELASTIC_APM_ACTIVE=false
     export JOURNEY_NAME="${i}"
 
     checks-reporter-with-killswitch "Run Performance Tests with Playwright Config (Journey:${i},Phase: WARMUP)" \
       node scripts/functional_tests \
-      --config x-pack/test/performance/config.playwright.ts \
-      --include "x-pack/test/performance/tests/playwright/${i}.ts" \
+      --config "x-pack/test/performance/journeys/${i}/config.ts" \
       --kibana-install-dir "$KIBANA_BUILD_LOCATION" \
       --debug \
       --bail
 
     export TEST_PERFORMANCE_PHASE=TEST
-    export ELASTIC_APM_ACTIVE=true
 
     checks-reporter-with-killswitch "Run Performance Tests with Playwright Config (Journey:${i},Phase: TEST)" \
       node scripts/functional_tests \
-      --config x-pack/test/performance/config.playwright.ts \
-      --include "x-pack/test/performance/tests/playwright/${i}.ts" \
+      --config "x-pack/test/performance/journeys/${i}/config.ts" \
       --kibana-install-dir "$KIBANA_BUILD_LOCATION" \
       --debug \
       --bail

.buildkite/scripts/steps/storybooks/build_and_upload.js

@@ -16,6 +16,7 @@ const STORYBOOKS = [
   'canvas',
   'ci_composite',
   'cloud',
+  'coloring',
   'controls',
   'custom_integrations',
   'dashboard_enhanced',

.eslintrc.js

@@ -657,6 +657,7 @@ module.exports = {
         'x-pack/test/*/*config.*ts',
         'x-pack/test/saved_object_api_integration/*/apis/**/*',
         'x-pack/test/ui_capabilities/*/tests/**/*',
+        'x-pack/test/performance/**/*.ts',
       ],
       rules: {
         'import/no-default-export': 'off',

.github/CODEOWNERS

@@ -141,6 +141,8 @@
 /x-pack/test/functional/es_archives/uptime @elastic/uptime
 /x-pack/test/functional/services/uptime @elastic/uptime
 /x-pack/test/api_integration/apis/uptime @elastic/uptime
+/x-pack/plugins/observability/public/components/shared/exploratory_view @elastic/uptime
+
 
 # Client Side Monitoring / Uptime (lives in APM directories but owned by Uptime)
 /x-pack/plugins/apm/public/application/uxApp.tsx @elastic/uptime

dev_docs/contributing/how_we_use_github.mdx

@@ -191,7 +191,8 @@ These labels categorize the type of work. For example:
 - `docs`/`documentation`: Indicates improvements or additions to documentation
 - `enhancement`: Indicates new feature or enhancement requests
 - `meta`: Indicates that the issue tracks tasks related to a project
-- `needs_triage`: Indicates that someone from the area team needs to investigate.
+- `triage-needed`: Indicates that someone from the area team needs to investigate.
+- `needs_team`: Indicates that issue is missing area team label. All issues should be assigned to one or more area teams for follow up. This label is assigned automatically and removed automatically once a team label is added.
 
 These labels affect whether your PR appears in the release notes (that is to say,
 it's notable and affects our users) and which section it appears in. For example:

dev_docs/getting_started/troubleshooting.mdx

@@ -40,3 +40,12 @@ it means you are using a new Elasticsearch feature that will not work in a CCS e
 We added this test coverage in version `8.1` because we accidentally broke core Kibana features (for example, when Discover started using the new fields parameter) for our CCS users. CCS is not a corner case and (excluding certain experimental features) Kibana should always work for our CCS users. This setting is our way of ensuring test coverage.
 
 Please reach out to the [Kibana Operations team](https://github.com/orgs/elastic/teams/kibana-operations) if you have further questions.
+
+### Minified React errors
+
+If you experience minified React errors and want to expand them to their full error messages you will currently need to rebuild the `@kbn/ui-shared-deps-npm` package using "development" mode instead of "production", which can be done by modifying the corresponding line in `packages/kbn-ui-shared-deps-npm/webpack.config.js` and make sure to run `yarn kbn bootstrap` afterwards:
+
+```diff
+-    mode: 'production',
++    mode: 'development',
+```

docs/api/actions-and-connectors/create.asciidoc

@@ -6,57 +6,100 @@
 
 Creates a connector.
 
-[discrete]
 [[create-connector-api-request]]
 === {api-request-title}
 
 `POST <kibana host>:<port>/api/actions/connector`
 
 `POST <kibana host>:<port>/s/<space_id>/api/actions/connector`
 
-[discrete]
 === {api-prereq-title}
 
 You must have `all` privileges for the *Actions and Connectors* feature in the
 *Management* section of the
 <<kibana-feature-privileges,{kib} feature privileges>>.
 
-[discrete]
 [[create-connector-api-path-params]]
 === {api-path-parms-title}
 
 `space_id`::
   (Optional, string) An identifier for the space. If `space_id` is not provided
   in the URL, the default space is used.
 
-[discrete]
+[role="child_attributes"]
 [[create-connector-api-request-body]]
 === {api-request-body-title}
 
-`name`::
-  (Required, string) The display name for the connector.
+`config`::
+(Required, object) The configuration for the connector. Configuration properties
+vary depending on the connector type. For example:
++
+.Index connectors
+[%collapsible%open]
+====
+`executionTimeField`::
+(Optional, string) Specifies a field that will contain the time the alert
+condition was detected. The default value is `null`.
+
+`index`::
+(Required, string) The {es} index to be written to.
+
+`refresh`::
+(Optional, boolean) The {ref}/docs-refresh.html[refresh] policy for the write
+request. The default value is `false`.
+
+For more information, refer to
+{kibana-ref}/index-action-type.html[Index connector and action].
+====
++
+.{jira} connectors
+[%collapsible%open]
+====
+
+`apiUrl`::
+(Required, string) The {jira} instance URL.
+
+`projectKey`::
+(Required, string) The {jira} project key.
+
+For more information, refer to
+{kibana-ref}/jira-action-type.html[{jira} connector and action].
+====
++
+For more configuration properties, refer to <<action-types>>.
 
 `connector_type_id`::
-  (Required, string) The connector type ID for the connector.
+(Required, string) The connector type ID for the connector.
 
-`config`::
-  (Required, object) The configuration for the connector. Configuration properties vary depending on
-  the connector type. For information about the configuration properties, refer to <<action-types,Action and connector types>>.
+`name`::
+(Required, string) The display name for the connector.
 
 `secrets`::
-  (Required, object) The secrets configuration for the connector. Secrets configuration properties vary
-  depending on the connector type. For information about the secrets configuration properties, refer to <<action-types,Action and connector types>>.
+(Required, object) The secrets configuration for the connector. Secrets
+configuration properties vary depending on the connector type. For information
+about the secrets configuration properties, refer to <<action-types>>.
 +
+--
 WARNING: Remember these values. You must provide them each time you call the <<update-connector-api, update>> API.
+--
++
+.{jira} connectors
+[%collapsible%open]
+====
+`apiToken`::
+(Required, string) The {jira} API authentication token for HTTP basic
+authentication.
+
+`email`::
+(Required, string) The account email for HTTP Basic authentication.
+====
 
-[discrete]
 [[create-connector-api-request-codes]]
 === {api-response-codes-title}
 
 `200`::
     Indicates a successful call.
 
-[discrete]
 [[create-connector-api-example]]
 === {api-examples-title}
 

docs/api/cases/cases-api-create.asciidoc

@@ -162,13 +162,9 @@ categorize cases. It can be an empty array.
 --------------------------------------------------
 POST api/cases
 {
-  "description": "James Bond clicked on a highly suspicious email
-  banner advertising cheap holidays for underpaid civil servants.",
-  "title": "This case will self-destruct in 5 seconds",
-  "tags": [
-    "phishing",
-    "social engineering"
-  ],
+  "description": "A case description.",
+  "title": "Case title 1",
+  "tags": [ "tag 1" ],
   "connector": {
     "id": "131d4448-abe0-4789-939d-8ef60680b498",
     "name": "My connector",
@@ -182,7 +178,7 @@ POST api/cases
   "settings": {
     "syncAlerts": true
   },
-  "owner": "securitySolution"
+  "owner": "cases"
 }
 --------------------------------------------------
 // KIBANA
@@ -198,26 +194,22 @@ the case identifier, version, and creation time. For example:
   "comments": [],
   "totalComment": 0,
   "totalAlerts": 0,
-  "title": "This case will self-destruct in 5 seconds",
-  "tags": [
-    "phishing",
-    "social engineering",
-    "bubblegum"
-  ],
+  "title": "Case title 1",
+  "tags": [ "tag 1" ],
   "settings": {
     "syncAlerts": true
   },
-  "owner": "securitySolution",
-  "description": "James Bond clicked on a highly suspicious email banner advertising cheap holidays for underpaid civil servants. Operation bubblegum is active. Repeat - operation bubblegum is now active",
+  "owner": "cases",
+  "description": "A case description.",
   "duration": null,
   "severity": "low",
   "closed_at": null,
   "closed_by": null,
   "created_at": "2022-05-13T09:16:17.416Z",
   "created_by": {
-    "email": "ahunley@imf.usa.gov",
-    "full_name": "Alan Hunley",
-    "username": "ahunley"
+    "email": null,
+    "full_name": null,
+    "username": "elastic"
   },
   "status": "open",
   "updated_at": null,

docs/api/cases/cases-api-find-cases.asciidoc

@@ -95,12 +95,12 @@ Defaults to `desc`.
 
 === {api-examples-title}
 
-Retrieve the first five cases with the `phishing` tag, in ascending order by
+Retrieve the first five cases with the `tag-1` tag, in ascending order by
 last update time:
 
 [source,sh]
 --------------------------------------------------
-GET api/cases/_find?page=1&perPage=5&sortField=updatedAt&sortOrder=asc&tags=phishing
+GET api/cases/_find?page=1&perPage=5&sortField=updatedAt&sortOrder=asc&tags=tag-1
 --------------------------------------------------
 // KIBANA
 
@@ -120,11 +120,11 @@ The API returns a JSON object listing the retrieved cases. For example:
       "totalComment": 1,
       "totalAlerts": 0,
       "title": "Case title",
-      "tags": [ "phishing" ],
+      "tags": [ "tag-1" ],
       "description": "Case description",
       "settings": { "syncAlerts": true },
       "owner": "securitySolution",
-      "duration": null,
+      "duration": null, <1>
       "severity": "low",
       "closed_at": null,
       "closed_by": null,
@@ -155,3 +155,7 @@ The API returns a JSON object listing the retrieved cases. For example:
   "count_closed_cases": 0
 }
 --------------------------------------------------
+<1> Duration represents the elapsed time from the creation of the case to its
+closure (in seconds). If the case has not been closed, the duration is set to
+`null`. If the case was closed after less than half a second, the duration is
+rounded down to zero.

docs/api/cases/cases-api-get-case.asciidoc

@@ -92,11 +92,15 @@ The API returns a JSON object with the retrieved case. For example:
   },
   "owner": "securitySolution",
   "severity": "low",
-  "duration": null,
+  "duration": null, <1>
   "tags": [
     "phishing",
     "social engineering",
     "bubblegum"
   ]
 }
---------------------------------------------------
+--------------------------------------------------
+<1> Duration represents the elapsed time from the creation of the case to its
+closure (in seconds). If the case has not been closed, the duration is set to
+`null`. If the case was closed after less than half a second, the duration is
+rounded down to zero.