Merge branch 'main' into alerting/es-recovery-context

elastic · Jun 4, 2022 · 7e11ebc · 7e11ebc
2 parents 46f4c6f + eadedd1
commit 7e11ebc
Show file tree

Hide file tree

Showing 502 changed files with 14,566 additions and 4,993 deletions.
diff --git a/.buildkite/ftr_configs.yml b/.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

diff --git a/.buildkite/scripts/steps/storybooks/build_and_upload.js b/.buildkite/scripts/steps/storybooks/build_and_upload.js
@@ -16,6 +16,7 @@ const STORYBOOKS = [
   'canvas',
   'ci_composite',
   'cloud',
+  'coloring',
   'controls',
   'custom_integrations',
   'dashboard_enhanced',

diff --git a/.github/CODEOWNERS b/.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

diff --git a/dev_docs/contributing/how_we_use_github.mdx b/dev_docs/contributing/how_we_use_github.mdx
@@ -131,7 +131,7 @@ would be useful to all teams, talk to your team or tech lead about getting it ad
 
 ### Team labels
 
-Examples: `Team:Security`, `Team:Operations`.
+Examples: `Team:Security`, `Team:Operations`, `Team:Docs`.
 
 These labels map the issue to the team that owns the particular area. Part of the responsibilities of
 (todo) is to ensure every issue has at least a team or a project
@@ -178,3 +178,36 @@ it might mean the version the team is tentatively planning to merge a fix.
 
 Consult the owning team if you have a question about how a version label is meant
 to be used on an issue.
+
+### Issue type and workflow labels
+
+These labels categorize the type of work. For example:
+
+- `blocked`: Indicates the issue is currently blocked
+- `blocker`: Indicates that we should not release the product at the next
+   proposed version without the issue being resolved
+- `bug`: Indicates an unexpected problem or unintended behavior
+- `discuss`: Indicates that an issue is a discussion topic
+- `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.
+
+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:
+
+- `release_note:breaking`: Specifies a breaking change and adds the PR to the Breaking changes section in the release notes
+- `release_note:deprecation`: Specifies a deprecated feature and adds the PR to the Deprecations section in the release notes
+- `release_note:enhancement`: Specifies a feature enhancement and adds the PR to the Enhancements section in the release notes
+- `release_note:feature`: Specifies a new feature and adds the PR to the  Features section in the release notes
+- `release_note:fix`: Specifies a bug fix and adds the PR to the Bug fixes section in the release notes
+- `release_node:plugin_api_changes`: Specifies a changes to the plugin API and adds the PR to the Plugin API changes page in the Developer Guide
+- `release_note:skip`: Omits the PR from release notes
+
+These labels related to backporting PRs:
+
+- `auto-backport`: Automatically backport this PR (to the branches related to
+   version labels) after it's merged
+- `backport`: This PR was backported
+- `backport:skip`: This PR does not require backporting
+
diff --git a/dev_docs/operations/operations_landing.mdx b/dev_docs/operations/operations_landing.mdx
@@ -50,6 +50,7 @@ layout: landing
     { pageId: "kibDevDocsOpsAmbientUiTypes" },
     { pageId: "kibDevDocsOpsTestSubjSelector" },
     { pageId: "kibDevDocsOpsBazelRunner" },
-    { pageId: "kibDevDocsOpsCliDevMode" }
+    { pageId: "kibDevDocsOpsCliDevMode" },
+    { pageId: "kibDevDocsOpsEs" },
   ]}
 />
diff --git a/docs/api/cases/cases-api-get-cases-by-alert.asciidoc b/docs/api/cases/cases-api-get-cases-by-alert.asciidoc
@@ -61,12 +61,8 @@ For example:
 --------------------------------------------------
 [
     {
-        "id": "8af6ac20-74f6-11ea-b83a-553aecdb28b6",
-        "title": "Case 1"
-    },
-    {
-        "id": "a18b38a0-71b0-11ea-a0b2-c51ea50a58e2",
-        "title": "Case 2"
+        "id": "06116b80-e1c3-11ec-be9b-9b1838238ee6",
+        "title":"security_case"
     }
 ]
 --------------------------------------------------
diff --git a/docs/api/cases/cases-api-get-configuration.asciidoc b/docs/api/cases/cases-api-get-configuration.asciidoc
@@ -44,7 +44,7 @@ read.
 
 [source,sh]
 --------------------------------------------------
-GET api/cases/configure?owner=securitySolution
+GET api/cases/configure?owner=cases
 --------------------------------------------------
 // KIBANA
 
@@ -54,19 +54,19 @@ The API returns the following type of information:
 --------------------------------------------------
 [
   {
-    "owner": "securitySolution",
     "closure_type": "close-by-user",
-    "created_at": "2020-03-30T13:31:38.083Z",
+    "owner": "cases",
+    "created_at": "2022-06-01T17:07:17.767Z",
     "created_by": {
-      "email": "admin@hms.gov.uk",
-      "full_name": "Mr Admin",
-      "username": "admin"
+      "email": "null",
+      "full_name": "null",
+      "username": "elastic"
     },
     "updated_at": null,
     "updated_by": null,
     "connector": {
       "id": "131d4448-abe0-4789-939d-8ef60680b498",
-      "name": "my-jira",
+      "name": "my-jira-connector",
       "type": ".jira",
       "fields": null
     },

diff --git a/docs/api/cases/cases-api-set-configuration.asciidoc b/docs/api/cases/cases-api-set-configuration.asciidoc
@@ -109,9 +109,9 @@ POST api/cases/configure
 {
   "owner": "cases",
   "connector": {
-    "id": "131d4448-abe0-4789-939d-8ef60680b498",
-    "name": "my-serviceNow",
-    "type": ".servicenow",
+    "id": "5e656730-e1ca-11ec-be9b-9b1838238ee6",
+    "name": "my-jira-connector",
+    "type": ".jira",
     "fields": null,
   },
   "closure_type": "close-by-user"
@@ -123,41 +123,41 @@ The API returns the following response:
 [source,json]
 --------------------------------------------------
 {
-  "owner": "cases",
   "closure_type": "close-by-user",
-  "created_at": "2022-04-02T01:09:02.303Z",
+  "owner": "cases",
+  "created_at": "2022-06-01T17:07:17.767Z",
   "created_by": {
-    "email": "moneypenny@hms.gov.uk",
-    "full_name": "Ms Moneypenny",
-    "username": "moneypenny"
+    "username": "elastic",
+    "email": null,
+    "full_name": null
   },
   "updated_at": null,
   "updated_by": null,
   "connector": {
-    "id": "131d4448-abe0-4789-939d-8ef60680b498",
-    "name": "my-serviceNow",
-    "type": ".servicenow",
-    "fields": null,
+    "id": "5e656730-e1ca-11ec-be9b-9b1838238ee6",
+    "name": "my-jira-connector",
+    "type": ".jira",
+    "fields": null
   },
   "mappings": [
     {
-      "source": "title", 
-      "target": "short_description",
+      "source": "title",
+      "target": "summary",
       "action_type": "overwrite"
     },
     {
-      "source":"description",
-      "target":"description",
-      "action_type":"overwrite"
+      "source": "description",
+      "target": "description",
+      "action_type": "overwrite"
     },
     {
-      "source":"comments",
-      "target":"work_notes",
-      "action_type":"append"
+      "source": "comments",
+      "target": "comments",
+      "action_type": "append"
     }
   ],
-  "version": "WzE3NywxXQ==",
+  "version": "WzIwNzMsMV0=",
   "error": null,
-  "id": "7349772f-421a-4de3-b8bb-2d9b22ccee30",
+  "id": "4a97a440-e1cd-11ec-be9b-9b1838238ee6"
 }
 --------------------------------------------------
diff --git a/docs/api/cases/cases-api-update-configuration.asciidoc b/docs/api/cases/cases-api-update-configuration.asciidoc
@@ -101,19 +101,19 @@ The API returns the following:
 [source,json]
 --------------------------------------------------
 {
-  "closure_type": "close-by-user",
+  "closure_type": "close-by-pushing",
   "owner": "cases",
-  "created_at": "2022-04-06T20:57:40.746Z",
+  "created_at": "2022-06-01T17:07:17.767Z",
   "created_by": {
-    "email": "admin@hms.gov.uk",
-    "full_name": "Ms Admin",
-    "username": "admin"
+    "email": "null",
+    "full_name": "null",
+    "username": "elastic"
   },
-  "updated_at": "2022-04-12T22:41:09.262Z",
+  "updated_at": "2022-06-01T19:58:48.169Z",
   "updated_by": {
-    "email": "admin@hms.gov.uk",
-    "full_name": "Ms Admin",
-    "username": "admin"
+    "email": "null",
+    "full_name": "null",
+    "username": "elastic"
   },
   "connector": {
     "id": "none",

diff --git a/docs/api/data-views.asciidoc b/docs/api/data-views.asciidoc
@@ -11,6 +11,7 @@ WARNING: Use the data views APIs for managing data views instead of lower-level
 The following data views APIs are available: 
 
 * Data views
+    ** <<data-views-api-get-all, Get all data views API>> to retrieve a list of data views
     ** <<data-views-api-get, Get data view API>> to retrieve a single data view
     ** <<data-views-api-create, Create data view API>> to create data view
     ** <<data-views-api-update, Update data view API>> to partially updated data view
@@ -27,6 +28,7 @@ The following data views APIs are available:
     ** <<data-views-runtime-field-api-update, Update runtime field API>> to partially update an existing runtime field
     ** <<data-views-runtime-field-api-delete, Delete runtime field API>> to delete a runtime field
 
+include::data-views/get-all.asciidoc[]
 include::data-views/get.asciidoc[]
 include::data-views/create.asciidoc[]
 include::data-views/update.asciidoc[]

diff --git a/docs/api/data-views/get-all.asciidoc b/docs/api/data-views/get-all.asciidoc
@@ -0,0 +1,60 @@
+[[data-views-api-get-all]]
+=== Get all data views API
+++++
+<titleabbrev>Get all data views</titleabbrev>
+++++
+
+experimental[] Retrieve a list of all data views.
+
+
+[[data-views-api-get-all-request]]
+==== Request
+
+`GET <kibana host>:<port>/api/data_views`
+
+`GET <kibana host>:<port>/s/<space_id>/api/data_views`
+
+
+[[data-views-api-get-all-codes]]
+==== Response code
+
+`200`::
+Indicates a successful call.
+
+
+[[data-views-api-get-all-example]]
+==== Example
+
+Retrieve the list of data views:
+
+[source,sh]
+--------------------------------------------------
+$ curl -X GET api/data_views
+--------------------------------------------------
+// KIBANA
+
+The API returns a list of data views:
+
+[source,sh]
+--------------------------------------------------
+{
+    "data_view": [
+        {
+            "id": "e9e024f0-d098-11ec-bbe9-c753adcb34bc",
+            "namespaces": [
+                "default"
+            ],
+            "title": "tmp*",
+            "type": "rollup",
+            "typeMeta": {}
+        },
+        {
+            "id": "90943e30-9a47-11e8-b64d-95841ca0b247",
+            "namespaces": [
+                "default"
+            ],
+            "title": "kibana_sample_data_logs"
+        }
+    ]
+}
+--------------------------------------------------