Merge branch '7.16' into infra-ui-add-missing-deprecation-levels

.buildkite/scripts/common/env.sh

@@ -42,7 +42,11 @@ if is_pr; then
     export ELASTIC_APM_ACTIVE=false
   fi
 
-  export CHECKS_REPORTER_ACTIVE=true
+  if [[ "${GITHUB_STEP_COMMIT_STATUS_ENABLED:-}" != "true" ]]; then
+    export CHECKS_REPORTER_ACTIVE=true
+  else
+    export CHECKS_REPORTER_ACTIVE=false
+  fi
 
   # These can be removed once we're not supporting Jenkins and Buildkite at the same time
   # These are primarily used by github checks reporter and can be configured via /github_checks_api.json

.buildkite/scripts/lifecycle/post_build.sh

@@ -5,7 +5,9 @@ set -euo pipefail
 BUILD_SUCCESSFUL=$(node "$(dirname "${0}")/build_status.js")
 export BUILD_SUCCESSFUL
 
-"$(dirname "${0}")/commit_status_complete.sh"
+if [[ "${GITHUB_BUILD_COMMIT_STATUS_ENABLED:-}" != "true" ]]; then
+  "$(dirname "${0}")/commit_status_complete.sh"
+fi
 
 node "$(dirname "${0}")/ci_stats_complete.js"
 

.buildkite/scripts/lifecycle/pre_build.sh

@@ -4,7 +4,9 @@ set -euo pipefail
 
 source .buildkite/scripts/common/util.sh
 
-"$(dirname "${0}")/commit_status_start.sh"
+if [[ "${GITHUB_BUILD_COMMIT_STATUS_ENABLED:-}" != "true" ]]; then
+  "$(dirname "${0}")/commit_status_start.sh"
+fi
 
 export CI_STATS_TOKEN="$(retry 5 5 vault read -field=api_token secret/kibana-issues/dev/kibana_ci_stats)"
 export CI_STATS_HOST="$(retry 5 5 vault read -field=api_host secret/kibana-issues/dev/kibana_ci_stats)"

api_docs/fleet.json

@@ -19589,16 +19589,6 @@
             "path": "x-pack/plugins/fleet/common/constants/routes.ts",
             "deprecated": false
           },
-          {
-            "parentPluginId": "fleet",
-            "id": "def-common.AGENT_API_ROUTES.ENROLL_PATTERN",
-            "type": "string",
-            "tags": [],
-            "label": "ENROLL_PATTERN",
-            "description": [],
-            "path": "x-pack/plugins/fleet/common/constants/routes.ts",
-            "deprecated": false
-          },
           {
             "parentPluginId": "fleet",
             "id": "def-common.AGENT_API_ROUTES.UNENROLL_PATTERN",
@@ -21782,4 +21772,4 @@
       }
     ]
   }
-}
+}

docs/discover/save-search.asciidoc

@@ -24,12 +24,8 @@ image::discover/images/read-only-badge.png[Example of Discover's read only acces
 [float]
 === Save a search
 
-. Once you've created a search worth saving, click *Save* in the toolbar.
+. Once you've created a search worth saving in *Discover*, click *Save* in the toolbar.
 . Enter a name for the search and click *Save*.
-+
-[role="screenshot"]
-image:images/discover-save-saved-search.png[Save saved search in Discover, width=50%]
-
 . To reload your search results in *Discover*, click *Open* in the toolbar, and select the saved search.
 +
 If the saved search is associated with a different index pattern than is currently

docs/discover/search-sessions.asciidoc

@@ -1,20 +1,19 @@
 [[search-sessions]]
 == Run a search session in the background
 
-Sometimes you might need to search through large amounts of data no matter
-how long the search takes. While this might not happen often,
-there are times that long-running queries are required.
+Sometimes you might need to search through large amounts of data, no matter
+how long the search takes.
 Consider a threat hunting scenario, where you need to search through years of data.
+You can save a long-running search, so {kib} processes your request in the
+background, and you can continue your work.
 
-If your query is running long, you can save your search session, which
-allows {kib} to continue processing your request in the
-background.  Save your search session from *Discover* or *Dashboard*,
+Save your search session from *Discover* or *Dashboard*,
 and when your session is complete, view and manage it in *Stack Management*.
+Search sessions are <<search-session-settings-kb,enabled by default>>.
 
 [role="screenshot"]
 image::images/search-session.png[Search Session indicator displaying the current state of the search, which you can click to stop or save a running Search Session ]
 
-Search sessions are <<search-session-settings-kb,enabled by default>>.
 
 [float]
 ==== Requirements
@@ -37,19 +36,24 @@ open your browser and pick up where you left off.
 
 . Load your dashboard.
 +
-Your search session begins automatically. The icon after the dashboard title
-displays the current state of the search session. A clock indicates the search session is in progress.
+Your search session begins automatically.
+The icon after the dashboard title displays the current state of the search session.
+A clock icon indicates the search session is in progress.
 A checkmark indicates that the search session is complete.
 
 . To instruct {kib} to continue a search in the background, click the clock icon,
-and then click *Save session*. Once you save a search session, you can start a new search,
-navigate to a different application, or close the browser.
+and then click *Save session*.
 +
 [role="screenshot"]
 image::images/search-session-awhile.png[Search Session indicator displaying the current state of the search, which you can click to stop or save a running Search Session, width=75% ]
++
+Once you save a search session, you can start a new search,
+navigate to a different application, or close the browser.
 
 . To view your saved searches, open the main menu, and then click
-*Stack Management > Search Sessions*.  You can also open this view from the search sessions popup for a saved or completed session.
+*Stack Management > Search Sessions*.
+For a saved or completed session, you can also open this view from the search sessions popup.
+
 +
 [role="screenshot"]
 image::images/search-sessions-menu.png[Search Sessions management view with actions for inspecting, extending, and deleting a session. ]
@@ -72,12 +76,11 @@ behaves differently:
 [float]
 ==== Limitations
 
-Certain visualization features do not fully support background search sessions. If a dashboard
-using these features is restored,
-all panels using unsupported features won't load immediately, but instead send out additional
+Some visualization features do not fully support background search sessions. When
+you restore a dashboard, panels with unsupported features won't load immediately, but instead
+send out additional
 data requests, which can take a while to complete.
-The warning *Your search session is still running* is shown.
-
+The warning *Your search session is still running* appears.
 You can either wait for these additional requests to complete or come back to the dashboard later
 when all data requests have finished.
 
@@ -89,7 +92,7 @@ A panel on a dashboard can behave like this if one of the following features is
 This is configurable in the *Advanced* section of the dimension.
 * An *intervals* dimension.
 
-**Aggregation based** visualizations
+**Aggregation-based** visualizations
 
 * A *terms* aggregation with an enabled *Group other values in separate bucket* setting.
 * A *histogram* aggregation.

docs/user/alerting/rule-types.asciidoc

@@ -26,6 +26,9 @@ see {subscriptions}[the subscription page].
 | <<rule-type-es-query>>
 | Run a user-configured {es} query, compare the number of matches to a configured threshold, and schedule actions to run when the threshold condition is met.
 
+| {ref}/transform-alerts.html[{transform-cap} rules] beta:[]
+| beta:[] Run scheduled checks on a {ctransform} to check its health. If a {ctransform} meets the conditions, an alert is created and the associated action is triggered.
+
 |===
 
 [float]
@@ -47,7 +50,7 @@ Domain rules are registered by *Observability*, *Security*, <<maps, Maps>> and <
 | Run an {es} query to determine if any documents are currently contained in any boundaries from a specified boundary index and generate alerts when a rule's conditions are met.
 
 | {ml-docs}/ml-configuring-alerts.html[{ml-cap} rules] beta:[]
-| Run scheduled checks on an anomaly detection job to detect anomalies with certain conditions. If an anomaly meets the conditions, an alert is created and the associated action is triggered.
+| beta:[] Run scheduled checks on an {anomaly-job} to detect anomalies with certain conditions. If an anomaly meets the conditions, an alert is created and the associated action is triggered.
 
 |===