Merge remote-tracking branch 'upstream' into 151489-support-inline-lo…

…g-views

.ci/Dockerfile

@@ -1,7 +1,7 @@
 # NOTE: This Dockerfile is ONLY used to run certain tasks in CI. It is not used to run Kibana or as a distributable.
 # If you're looking for the Kibana Docker image distributable, please see: src/dev/build/tasks/os_packages/docker_generator/templates/dockerfile.template.ts
 
-ARG NODE_VERSION=16.19.0
+ARG NODE_VERSION=16.19.1
 
 FROM node:${NODE_VERSION} AS base
 

.github/CODEOWNERS

@@ -461,7 +461,7 @@ src/plugins/newsfeed @elastic/kibana-core
 test/common/plugins/newsfeed @elastic/kibana-core
 x-pack/plugins/notifications @elastic/appex-sharedux
 x-pack/test/cases_api_integration/common/plugins/observability @elastic/response-ops
-x-pack/plugins/observability @elastic/observability-ui
+x-pack/plugins/observability @elastic/actionable-observability
 x-pack/test/security_api_integration/plugins/oidc_provider @elastic/kibana-security
 test/common/plugins/otel_metrics @elastic/infra-monitoring-ui
 packages/kbn-optimizer @elastic/kibana-operations
@@ -759,20 +759,11 @@ packages/kbn-yarn-lock-validator @elastic/kibana-operations
 # /x-pack/test/observability_functional @elastic/unified-observability
 
 # Home/Overview/Landing Pages
-/x-pack/plugins/observability/public/pages/home @elastic/observability-design
-/x-pack/plugins/observability/public/pages/landing @elastic/observability-design
-/x-pack/plugins/observability/public/pages/overview @elastic/observability-design @elastic/actionable-observability
+/x-pack/plugins/observability/public/pages/home @elastic/observability-design @elastic/observability-ui
+/x-pack/plugins/observability/public/pages/landing @elastic/observability-design @elastic/observability-ui
+/x-pack/plugins/observability/public/pages/overview @elastic/observability-design @elastic/observability-ui
 
 # Actionable Observability
-/x-pack/plugins/observability/common/rules @elastic/actionable-observability
-/x-pack/plugins/observability/public/rules @elastic/actionable-observability
-/x-pack/plugins/observability/public/pages/alerts @elastic/actionable-observability
-/x-pack/plugins/observability/public/pages/cases  @elastic/actionable-observability
-/x-pack/plugins/observability/public/pages/rules  @elastic/actionable-observability
-/x-pack/plugins/observability/public/pages/rule_details  @elastic/actionable-observability
-/x-pack/plugins/observability/public/pages/slos  @elastic/actionable-observability
-/x-pack/plugins/observability/public/pages/slo_edit  @elastic/actionable-observability
-/x-pack/plugins/observability/public/pages/slo_details  @elastic/actionable-observability
 /x-pack/test/observability_functional @elastic/actionable-observability
 
 # Infra Monitoring

.node-version

@@ -1 +1 @@
-16.19.0
+16.19.1

.nvmrc

@@ -1 +1 @@
-16.19.0
+16.19.1

WORKSPACE.bazel

@@ -22,13 +22,13 @@ load("@build_bazel_rules_nodejs//:index.bzl", "node_repositories", "yarn_install
 # Setup the Node.js toolchain for the architectures we want to support
 node_repositories(
   node_repositories = {
-    "16.19.0-darwin_amd64": ("node-v16.19.0-darwin-x64.tar.gz", "node-v16.19.0-darwin-x64", "491e5a5592eca1961dcbb1fae28567428ce56ce9cc7977b04041e163e0c1670c"),
-    "16.19.0-darwin_arm64": ("node-v16.19.0-darwin-arm64.tar.gz", "node-v16.19.0-darwin-arm64", "5c9434fbb0f323fecf3d261b23a2e544919380c5043d0046d9745682fefd9cde"),
-    "16.19.0-linux_arm64": ("node-v16.19.0-linux-arm64.tar.xz", "node-v16.19.0-linux-arm64", "9072c995052f832678fe8fab18e960bd9853f30e481787e53f8dd1ec8aaa3bb6"),
-    "16.19.0-linux_amd64": ("node-v16.19.0-linux-x64.tar.xz", "node-v16.19.0-linux-x64", "c88b52497ab38a3ddf526e5b46a41270320409109c3f74171b241132984fd08f"),
-    "16.19.0-windows_amd64": ("node-v16.19.0-win-x64.zip", "node-v16.19.0-win-x64", "534ca7a24e999c81cec847a498cc43d47e2bb158f6edf639e5297f2718350e96"),
+    "16.19.1-darwin_amd64": ("node-v16.19.1-darwin-x64.tar.gz", "node-v16.19.1-darwin-x64", "d7f683b2a8f78db8a28235a175e130c760f0d3cd335404e02f223e3a9adc30c7"),
+    "16.19.1-darwin_arm64": ("node-v16.19.1-darwin-arm64.tar.gz", "node-v16.19.1-darwin-arm64", "168f787f457bf645f3fc41e7419b62071db7d42519ce461b1d7ebfc0acbdbfb1"),
+    "16.19.1-linux_arm64": ("node-v16.19.1-linux-arm64.tar.xz", "node-v16.19.1-linux-arm64", "042b3ae7e994a77bfdb0e366d0389c1b7602bb744830da15f9325f404f979ce2"),
+    "16.19.1-linux_amd64": ("node-v16.19.1-linux-x64.tar.xz", "node-v16.19.1-linux-x64", "fa796a23837dc5c22914b1349b6117df4d497e2001a4cd7b28b0767e22f3bb51"),
+    "16.19.1-windows_amd64": ("node-v16.19.1-win-x64.zip", "node-v16.19.1-win-x64", "77e0198497fee24552d6a6f1737eed595b619af1b749ee0bee4b938026e55f73"),
   },
-  node_version = "16.19.0",
+  node_version = "16.19.1",
   node_urls = [
     "https://nodejs.org/dist/v{version}/{filename}",
   ],

docs/action-type-template.asciidoc

@@ -1,16 +1,25 @@
 [[<ACTION-TYPE>-action-type]]
-=== <ACTION-TYPE> connector and action
+== <ACTION-TYPE> connector and action
 ++++
 <titleabbrev><ACTION-TYPE></titleabbrev>
 ++++
 
 Include a short description of the connector type.
 
+[float]
+[[define-<ACTION-TYPE>-ui]]
+=== Create connectors in {kib}
+
+You can create connectors in *{stack-manage-app} > {connectors-ui}*
+or as needed when you're creating a rule.
+
+// Optionally add a screenshot
+
 [float]
 [[<ACTION-TYPE>-connector-configuration]]
 ==== Connector configuration
 
-<ACTION-TYPE> connectors have the following configuration properties.
+<ACTION-TYPE> connectors have the following configuration properties:
 
 ////
 List of user-facing connector configurations. This should align with the fields available in the Create connector flyout form for this connector type.
@@ -20,23 +29,28 @@ Property1:: A short description of this property.
 Property2:: A short description of this property with format hints. This can be specified in `this specific format`.
 
 [float]
-[[Preconfigured-<ACTION-TYPE>-configuration]]
-==== Preconfigured connector type
+[[preconfigured-<ACTION-TYPE>-configuration]]
+=== Create preconfigured connectors
+
+If you are running {kib} on-prem, you can define connectors by
+adding `xpack.actions.preconfigured` settings to your `kibana.yml` file.
+For example:
 
 ////
 Example preconfigured format for this connector type
 ////
 
 [source,text]
 --
- my-<ACTION-TYPE>:
-   name: preconfigured-<ACTION-TYPE>-connector-type
-   actionTypeId: .<ACTION-TYPE>
-   config:
-     property1: value1
-     property2: value2
-   secrets:
-     property3: value3
+xpack.actions.preconfigured:
+  my-<ACTION-TYPE>:
+    name: preconfigured-<ACTION-TYPE>-connector-type
+    actionTypeId: .<ACTION-TYPE>
+    config:
+      property1: value1
+      property2: value2
+    secrets:
+      property3: value3
 --
 
 ////
@@ -53,7 +67,10 @@ Secrets defines sensitive information for the connector type.
 
 [float]
 [[<ACTION-TYPE>-action-configuration]]
-==== Action configuration
+=== Test connectors
+
+You can test connectors with the <<execute-connector-api,run connector API>> or
+as you're creating or editing the connector in {kib}.
 
 <ACTION-TYPE> actions have the following properties.
 

docs/developer/advanced/upgrading-nodejs.asciidoc

@@ -17,7 +17,7 @@ These files must be updated when upgrading Node.js:
   - {kib-repo}blob/{branch}/WORKSPACE.bazel[`WORKSPACE.bazel`] - The version is specified in the `node_version` property.
     Besides this property, the list of files under `node_repositories` must be updated along with their respective SHA256 hashes.
     These can be found on the https://nodejs.org[nodejs.org] website.
-    Example for Node.js v16.19.0: https://nodejs.org/dist/v16.19.0/SHASUMS256.txt.asc
+    Example for Node.js v16.19.1: https://nodejs.org/dist/v16.19.1/SHASUMS256.txt.asc
 
 See PR {kib-repo}pull/128123[#128123] for an example of how the Node.js version has been upgraded previously.
 

docs/management/connectors/action-types/cases-webhook.asciidoc

@@ -7,9 +7,19 @@
 
 The {webhook-cm} connector uses https://github.com/axios/axios[axios] to send POST, PUT, and GET requests to a case management RESTful API web service.
 
+[float]
+[[define-cases-webhook-ui]]
+=== Create connectors in {kib}
+
+You can create connectors in *{stack-manage-app} > {connectors-ui}*
+or as needed when you're creating a rule. For example:
+
+[role="screenshot"]
+image::management/connectors/images/cases-webhook-connector.gif[{webhook-cm} connector]
+
 [float]
 [[cases-webhook-connector-configuration]]
-=== Connector configuration
+==== Connector configuration
 
 {webhook-cm} connectors have the following configuration properties:
 
@@ -96,39 +106,38 @@ Create comment object:: (Optional) A JSON payload sent to the create comment URL
 NOTE: Due to Mustache template variables (the text enclosed in triple braces, for example, `{{{case.title}}}`), the JSON is not validated in this step. The JSON is validated once the mustache variables have been placed and when REST method runs. We recommend manually ensuring that the JSON is valid, disregarding the Mustache variables, so the later validation will pass.
 
 [float]
-[[cases-webhook-connector-networking-configuration]]
-=== Connector networking configuration
+[[preconfigured-cases-webhook-configuration]]
+=== Create preconfigured connectors
 
-Use the <<action-settings,action configuration settings>> to customize connector networking configurations, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use `xpack.actions.customHostSettings` to set per-host configurations.
-
-[float]
-[[Preconfigured-cases-webhook-configuration]]
-=== Preconfigured connector type
+If you are running {kib} on-prem, you can define connectors by
+adding `xpack.actions.preconfigured` settings to your `kibana.yml` file.
+For example:
 
 [source,text]
 --
- my-case-management-webhook:
-   name: Case Management Webhook Connector
-   actionTypeId: .cases-webhook
-   config:
-     hasAuth: true
-     headers:
-       'content-type': 'application/json'
-     createIncidentUrl: 'https://testing-jira.atlassian.net/rest/api/2/issue'
-     createIncidentMethod: 'post'
-     createIncidentJson: '{"fields":{"summary":{{{case.title}}},"description":{{{case.description}}},"labels":{{{case.tags}}}'
-     getIncidentUrl: 'https://testing-jira.atlassian.net/rest/api/2/issue/{{{external.system.id}}}'
-     getIncidentResponseExternalTitleKey: 'key'
-     viewIncidentUrl: 'https://testing-jira.atlassian.net/browse/{{{external.system.title}}}'
-     updateIncidentUrl: 'https://testing-jira.atlassian.net/rest/api/2/issue/{{{external.system.id}}}'
-     updateIncidentMethod: 'put'
-     updateIncidentJson: '{"fields":{"summary":{{{case.title}}},"description":{{{case.description}}},"labels":{{{case.tags}}}'
-     createCommentMethod: 'post',
-     createCommentUrl: 'https://testing-jira.atlassian.net/rest/api/2/issue/{{{external.system.id}}}/comment',
-     createCommentJson: '{"body": {{{case.comment}}}}',
-   secrets:
-     user: testuser
-     password: passwordvalue
+xpack.actions.preconfigured:
+  my-case-management-webhook:
+    name: Case Management Webhook Connector
+    actionTypeId: .cases-webhook
+    config:
+      hasAuth: true
+      headers:
+        'content-type': 'application/json'
+      createIncidentUrl: 'https://testing-jira.atlassian.net/rest/api/2/issue'
+      createIncidentMethod: 'post'
+      createIncidentJson: '{"fields":{"summary":{{{case.title}}},"description":{{{case.description}}},"labels":{{{case.tags}}}'
+      getIncidentUrl: 'https://testing-jira.atlassian.net/rest/api/2/issue/{{{external.system.id}}}'
+      getIncidentResponseExternalTitleKey: 'key'
+      viewIncidentUrl: 'https://testing-jira.atlassian.net/browse/{{{external.system.title}}}'
+      updateIncidentUrl: 'https://testing-jira.atlassian.net/rest/api/2/issue/{{{external.system.id}}}'
+      updateIncidentMethod: 'put'
+      updateIncidentJson: '{"fields":{"summary":{{{case.title}}},"description":{{{case.description}}},"labels":{{{case.tags}}}'
+      createCommentMethod: 'post',
+      createCommentUrl: 'https://testing-jira.atlassian.net/rest/api/2/issue/{{{external.system.id}}}/comment',
+      createCommentJson: '{"body": {{{case.comment}}}}',
+    secrets:
+      user: testuser
+      password: passwordvalue
 --
 
 `config`:: Defines information for the connector type.
@@ -153,30 +162,28 @@ Use the <<action-settings,action configuration settings>> to customize connector
 `password`::: A string that corresponds to *Password*. Required if `hasAuth` is set to `true`.
 
 [float]
-[[define-cases-webhook-ui]]
-=== Define connector in {stack-manage-app}
-
-Define {webhook-cm} connector properties:
-
-[role="screenshot"]
-image::management/connectors/images/cases-webhook-connector.gif[{webhook-cm} connector]
+[[cases-webhook-action-configuration]]
+=== Test connectors
 
-Test {webhook-cm} action parameters:
+You can test connectors with the <<execute-connector-api,run connector API>> or
+as you're creating or editing the connector in {kib}. For example:
 
 [role="screenshot"]
 image::management/connectors/images/cases-webhook-test.gif[{webhook-cm} params test]
 
-[float]
-[[cases-webhook-action-configuration]]
-=== Action configuration
-
 {webhook-cm} actions have the following configuration properties:
 
 Title:: A title for the issue, which is used for searching the contents of the knowledge base.
 Description:: The details about the incident.
 Labels:: The labels for the incident.
 Additional comments:: Additional information for the client, such as how to troubleshoot the issue.
 
+[float]
+[[cases-webhook-connector-networking-configuration]]
+=== Connector networking configuration
+
+Use the <<action-settings,action configuration settings>> to customize connector networking configurations, such as proxies, certificates, or TLS settings. You can set configurations that apply to all your connectors or use `xpack.actions.customHostSettings` to set per-host configurations.
+
 ////
 [float]
 [[cases-webhook-connector-full-example]]