Merge remote-tracking branch 'upstream/master' into ml-transform-runtime-tests

Author: qn895

.bazeliskversion

@@ -1 +1 @@
-1.7.3
+1.7.5

.gitignore

@@ -1,5 +1,6 @@
 .aws-config.json
 .signing-config.json
+/api_docs
 .ackrc
 /.es
 /.chromium

docs/canvas/canvas-function-reference.asciidoc

@@ -1697,6 +1697,16 @@ Aliases: `column`, `name`
 Aliases: `exp`, `fn`, `function`
 |`boolean`, `number`, `string`, `null`
 |A Canvas expression that is passed to each row as a single row `datatable`.
+
+|`id`
+
+|`string`, `null`
+|An optional id of the resulting column. When not specified or `null` the name argument is used as id.
+
+|`copyMetaFrom`
+
+|`string`, `null`
+|If set, the meta object from the specified column id is copied over to the specified target column. Throws an exception if the column doesn't exist
 |===
 
 *Returns:* `datatable`
@@ -1755,9 +1765,16 @@ Interprets a `TinyMath` math expression using a `number` or `datatable` as _cont
 Alias: `expression`
 |`string`
 |An evaluated `TinyMath` expression. See https://www.elastic.co/guide/en/kibana/current/canvas-tinymath-functions.html.
+
+|`onError` 
+
+|`string`
+|In case the `TinyMath` evaluation fails or returns NaN, the return value is specified by onError. For example, `"null"`, `"zero"`, `"false"`, `"throw"`. When `"throw"`, it will throw an exception, terminating expression execution.
+
+Default: `"throw"`
 |===
 
-*Returns:* `number`
+*Returns:* `number` | `boolean` | `null`
 
 
 [float]

docs/development/core/server/kibana-plugin-core-server.pluginmanifest.md

@@ -28,6 +28,7 @@ Should never be used in code outside of Core but is exported for documentation p
 |  [requiredBundles](./kibana-plugin-core-server.pluginmanifest.requiredbundles.md) | <code>readonly string[]</code> | List of plugin ids that this plugin's UI code imports modules from that are not in <code>requiredPlugins</code>. |
 |  [requiredPlugins](./kibana-plugin-core-server.pluginmanifest.requiredplugins.md) | <code>readonly PluginName[]</code> | An optional list of the other plugins that \*\*must be\*\* installed and enabled for this plugin to function properly. |
 |  [server](./kibana-plugin-core-server.pluginmanifest.server.md) | <code>boolean</code> | Specifies whether plugin includes some server-side specific functionality. |
+|  [serviceFolders](./kibana-plugin-core-server.pluginmanifest.servicefolders.md) | <code>readonly string[]</code> | Only used for the automatically generated API documentation. Specifying service folders will cause your plugin API reference to be broken up into sub sections. |
 |  [ui](./kibana-plugin-core-server.pluginmanifest.ui.md) | <code>boolean</code> | Specifies whether plugin includes some client/browser specific functionality that should be included into client bundle via <code>public/ui_plugin.js</code> file. |
 |  [version](./kibana-plugin-core-server.pluginmanifest.version.md) | <code>string</code> | Version of the plugin. |
 

docs/development/core/server/kibana-plugin-core-server.pluginmanifest.servicefolders.md

@@ -0,0 +1,13 @@
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [kibana-plugin-core-server](./kibana-plugin-core-server.md) &gt; [PluginManifest](./kibana-plugin-core-server.pluginmanifest.md) &gt; [serviceFolders](./kibana-plugin-core-server.pluginmanifest.servicefolders.md)
+
+## PluginManifest.serviceFolders property
+
+Only used for the automatically generated API documentation. Specifying service folders will cause your plugin API reference to be broken up into sub sections.
+
+<b>Signature:</b>
+
+```typescript
+readonly serviceFolders?: readonly string[];
+```

docs/discover/images/discover-search-for-relevance.png

@@ -0,0 +1,24 @@
+[[discover-search-for-relevance]]
+== Search for relevance
+Sometimes you might be unsure which documents best match your question. 
+{es} assigns a relevancy, or score to each document, so you can
+can narrow your search to the documents with the most relevant results.
+The higher the score, the better it matches your query.
+
+For example, suppose you have the <<gs-get-data-into-kibana, sample flights data set>>, and you're a searching for
+a flight that arrived or departed from `Warsaw` or `Venice` when the weather was clear.
+
+.  In *Discover*, open the index pattern dropdown, and select `kibana_sample_data_flight`.
+.  In the query bar, click  *KQL*, and switch to the <<lucene-query, Lucene query syntax>>.
+. Search for `Warsaw OR Venice OR Clear`.
+.  If you don't see any results, open the time filter and select a time range that contains data.
+.  From the list of *Available fields*, add `_score` to the document table.
+. In the document table, click the header for the `_score` column, and then sort the column by descending scores.
++
+The results are currently sorted by first `Time`, and then by `_score`.
+. To sort only by `_score`, remove the `Time` field.
++
+Your table now shows documents with the best matches, from most to least relevant.
++
+[role="screenshot"]
+image::images/discover-search-for-relevance.png["Example of a search for relevance"]

docs/discover/search-for-relevance.asciidoc

@@ -105,7 +105,7 @@ See <<pagerduty-in-pagerduty, In PagerDuty>> for how to obtain the endpoint and
 +
 * The action’s type: Trigger, Resolve, or Acknowledge.
 * The event’s severity: Info, warning, error, or critical.
-* An array of different fields, including the timestamp, group, class, component, and your dedup key.
+* An array of different fields, including the timestamp, group, class, component, and your dedup key. By default, the dedup is configured to create a new PagerDuty incident for each alert instance and reuse the incident when a recovered alert instance reactivates.
 Depending on your custom needs, assign them variables from the alerting context.
 To see the available context variables, click on the *Add alert variable* icon next
 to each corresponding field. For more details on these parameters, see the
@@ -179,7 +179,7 @@ PagerDuty actions have the following properties:
 
 Severity::      The perceived severity of on the affected system. This can be one of `Critical`, `Error`, `Warning` or `Info`(default).
 Event action::  One of `Trigger` (default), `Resolve`, or `Acknowledge`. See https://v2.developer.pagerduty.com/docs/events-api-v2#event-action[event action] for more details.
-Dedup Key::     All actions sharing this key will be associated with the same PagerDuty alert. This value is used to correlate trigger and resolution. This value is *optional*, and if unset defaults to `action:<action saved object id>`. The maximum length is *255* characters. See https://v2.developer.pagerduty.com/docs/events-api-v2#alert-de-duplication[alert deduplication] for details.
+Dedup Key::     All actions sharing this key will be associated with the same PagerDuty alert. This value is used to correlate trigger and resolution. This value is *optional*, and if not set, defaults to `<alert ID>:<alert instance ID>`. The maximum length is *255* characters. See https://v2.developer.pagerduty.com/docs/events-api-v2#alert-de-duplication[alert deduplication] for details. 
 Timestamp::     An *optional* https://v2.developer.pagerduty.com/v2/docs/types#datetime[ISO-8601 format date-time], indicating the time the event was detected or generated.
 Component::     An *optional* value indicating the component of the source machine that is responsible for the event, for example `mysql` or `eth0`.
 Group::         An *optional* value indicating the logical grouping of components of a service, for example `app-stack`.

docs/user/alerting/action-types/pagerduty.asciidoc

@@ -30,6 +30,14 @@ For domain-specific alerts, refer to the documentation for that app.
 * <<geo-alerting, Maps alerts>>
 * <<xpack-ml, ML alerts>>
 
+[NOTE]
+==============================================
+Some alert types are subscription features, while others are free features.
+For a comparison of the Elastic subscription levels,
+see {subscriptions}[the subscription page].
+==============================================
+
+
 include::stack-alerts/index-threshold.asciidoc[]
 include::stack-alerts/es-query.asciidoc[]
 include::maps-alerts/geo-alert-types.asciidoc[]

docs/user/alerting/alert-types.asciidoc

@@ -36,7 +36,7 @@ that shows a single data center or server.
 [[url-drilldowns]]
 ==== URL drilldowns
 
-beta[] URL drilldowns enable you to navigate from a dashboard to internal or external URLs.
+URL drilldowns enable you to navigate from a dashboard to internal or external URLs.
 Destination URLs can be dynamic, depending on the dashboard context or user interaction with a panel.
 For example, if you have a dashboard that shows data from a Github repository, you can create a URL drilldown
 that opens Github from the dashboard.
@@ -226,7 +226,7 @@ and date range are carried over.
 [[create-a-url-drilldown]]
 === Try it: Create a URL drilldown
 
-beta[] To create URL drilldowns, you add <<variables,variables>> to a URL template, which configures the bahavior of the drilldown.
+To create URL drilldowns, you add <<variables,variables>> to a URL template, which configures the behavior of the drilldown.
 
 image:images/url_drilldown_go_to_github.gif[Drilldown on pie chart that navigates to Github]