Merge branch 'master' into alerting/consumer-based-rbac

* master: (37 commits)
  [DOCS] Adds documentation for drilldowns (elastic#68122)
  [Telemetry] telemetry.sendUsageFrom: "server" by default (elastic#68071)
  [ML] Transforms: Support sub-aggregations (elastic#68306)
  Fixed pre-configured docs link points to the wrong page and functional tests configs (elastic#68606)
  [Ingest Manager] Update queries from `stream.*` to `dataset.*` (elastic#68322)
  Enable Watcher by default to fix bug in which Watcher doesn't render in the side nav (elastic#68602)
  Convert Index Templates API routes to snakecase. (elastic#68463)
  [SECURITY SOLUTION] [Detections] Add / Update e2e tests to ensure initial rule runs are successful (elastic#68441)
  [Ingest] OpenAPI spec file (elastic#68323)
  chore(NA): skip apis Endpoint plugin Endpoint policy api (elastic#68638)
  bumping makelogs version to v6.0.0 (elastic#66163)
  [SIEM] Add create template button (elastic#66613)
  Bump websocket-extensions from 0.1.3 to 0.1.4 (elastic#68414)
  [ML] Sample data modules - use event.dataset instead of index name (elastic#68538)
  [ML] Functional tests - fix job validation API test with maxModelMemoryLimit (elastic#68501)
  [ML] Functional tests - stabilize DFA job creation (elastic#68495)
  [TSVB] Allows the user to change the tooltip mode (elastic#67775)
  chore(NA): skip apis Endpoint plugin Endpoint alert API when data is in elasticsearch (elastic#68613)
  chore(NA): skip endpoint Endpoint Alert Page: when es has data and user has navigated to the page (elastic#68596)
  [SIEM][Detection Engine] Converts from joi to use io-ts and moves the types to common  (elastic#68127)
  ...

docs/dev-tools/console/console.asciidoc

@@ -44,7 +44,7 @@ curl -XGET "http://localhost:9200/_search" -d'
 ----------------------------------
 
 When you paste the command into Console, {kib} automatically converts it
-to Console syntax.  Alternatively, if you want to want to see Console syntax in cURL, 
+to Console syntax.  Alternatively, if you want to see Console syntax in cURL, 
 click the action icon (image:dev-tools/console/images/wrench.png[]) and select *Copy as cURL*.
 
 [float]

docs/development/core/public/kibana-plugin-core-public.md

@@ -132,6 +132,12 @@ The plugin integrates with the core system via lifecycle events: `setup`<!-- -->
 |  [URLMeaningfulParts](./kibana-plugin-core-public.urlmeaningfulparts.md) | We define our own typings because the current version of @<!-- -->types/node declares properties to be optional "hostname?: string". Although, parse call returns "hostname: null \| string". |
 |  [UserProvidedValues](./kibana-plugin-core-public.userprovidedvalues.md) | Describes the values explicitly set by user. |
 
+## Variables
+
+|  Variable | Description |
+|  --- | --- |
+|  [URL\_MAX\_LENGTH](./kibana-plugin-core-public.url_max_length.md) | The max URL length allowed by the current browser. Should be used to display warnings to users when query parameters cause URL to exceed this limit. |
+
 ## Type Aliases
 
 |  Type Alias | Description |

docs/development/core/public/kibana-plugin-core-public.url_max_length.md

@@ -0,0 +1,13 @@
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [kibana-plugin-core-public](./kibana-plugin-core-public.md) &gt; [URL\_MAX\_LENGTH](./kibana-plugin-core-public.url_max_length.md)
+
+## URL\_MAX\_LENGTH variable
+
+The max URL length allowed by the current browser. Should be used to display warnings to users when query parameters cause URL to exceed this limit.
+
+<b>Signature:</b>
+
+```typescript
+URL_MAX_LENGTH: number
+```

docs/development/plugins/data/public/kibana-plugin-plugins-data-public.md

@@ -67,7 +67,6 @@
 |  [IndexPatternTypeMeta](./kibana-plugin-plugins-data-public.indexpatterntypemeta.md) |  |
 |  [IRequestTypesMap](./kibana-plugin-plugins-data-public.irequesttypesmap.md) |  |
 |  [IResponseTypesMap](./kibana-plugin-plugins-data-public.iresponsetypesmap.md) |  |
-|  [ISearchContext](./kibana-plugin-plugins-data-public.isearchcontext.md) |  |
 |  [ISearchOptions](./kibana-plugin-plugins-data-public.isearchoptions.md) |  |
 |  [ISearchStrategy](./kibana-plugin-plugins-data-public.isearchstrategy.md) | Search strategy interface contains a search method that takes in a request and returns a promise that resolves to a response. |
 |  [ISyncSearchRequest](./kibana-plugin-plugins-data-public.isyncsearchrequest.md) |  |
@@ -157,5 +156,4 @@
 |  [TabbedAggRow](./kibana-plugin-plugins-data-public.tabbedaggrow.md) | \* |
 |  [TimefilterContract](./kibana-plugin-plugins-data-public.timefiltercontract.md) |  |
 |  [TimeHistoryContract](./kibana-plugin-plugins-data-public.timehistorycontract.md) |  |
-|  [TSearchStrategyProvider](./kibana-plugin-plugins-data-public.tsearchstrategyprovider.md) | Search strategy provider creates an instance of a search strategy with the request handler context bound to it. This way every search strategy can use whatever information they require from the request context. |
 

docs/drilldowns/drilldowns.asciidoc

@@ -0,0 +1,108 @@
+[[drilldowns]]
+== Use drilldowns for dashboard actions
+
+Drilldowns, also known as custom actions, allow you to configure a
+workflow for analyzing and troubleshooting your data.
+Using a drilldown, you can navigate from one dashboard to another,
+taking the current time range, filters, and other parameters with you,
+so the context remains the same. You can continue your analysis from a new perspective.
+
+For example, you might have a dashboard that shows the overall status of multiple data centers.
+You can create a drilldown that navigates from this dashboard to a dashboard
+that shows a single data center or server.
+
+[float]
+[[how-drilldowns-work]]
+=== How drilldowns work
+
+Drilldowns are {kib} actions that you configure and store
+in the dashboard saved object. Drilldowns are specific to the dashboard panel
+for which you create them—they are not shared across panels.
+A panel can have multiple drilldowns.
+
+This example shows a dashboard panel that contains a pie chart.
+Typically, clicking a pie slice applies the current filter.
+When a panel has a drilldown, clicking a pie slice opens a menu with
+the default action and your drilldowns. Refer to the <<drilldowns-example, Try it section>>
+for instructions on how to create this drilldown.
+
+[role="screenshot"]
+image::images/drilldown_on_piechart.gif[Drilldown on pie chart that navigates to another dashboard]
+
+Third-party developers can create drilldowns.
+Refer to https://github.com/elastic/kibana/tree/master/x-pack/examples/ui_actions_enhanced_examples[this example plugin]
+to learn how to code drilldowns.
+
+[float]
+[[create-manage-drilldowns]]
+=== Create and manage drilldowns
+
+Your dashboard must be in *Edit* mode to create a drilldown.
+Once a panel has at least one drilldown, the menu also includes a *Manage drilldowns* action
+for editing and deleting drilldowns.
+
+[role="screenshot"]
+image::images/drilldown_menu.png[Panel menu with Create drilldown and Manage drilldown actions]
+
+[float]
+[[drilldowns-example]]
+=== Try it: Create a drilldown
+
+This example shows how to create the *Host Overview* drilldown shown earlier in this doc.
+
+[float]
+==== Set up the dashboards
+
+. Add the <<get-data-in, sample web logs>> data set.
+
+. Create a new dashboard, called `Host Overview`, and include these visualizations
+from the sample data set:
++
+[%hardbreaks]
+*[Logs] Heatmap*
+*[Logs] Visitors by OS*
+*[Logs] Host, Visits, and Bytes Table*
+*[Logs] Total Requests and Bytes*
++
+TIP: If you don’t see data for a panel, try changing the time range.
+
+. Open the *[Logs] Web traffic* dashboard.
+
+. Set a search and filter.
++
+[%hardbreaks]
+Search: `extension.keyword:( “gz” or “css” or “deb”)`
+Filter: `geo.src : CN`
+
+[float]
+==== Create the drilldown
+
+
+. In the dashboard menu bar, click *Edit*.
+
+. In *[Logs] Visitors by OS*, open the panel menu, and then select *Create drilldown*.
+
+. Give the drilldown a name.
+
+. Select *Host Overview* as the destination dashboard.
+
+. Keep both filters enabled so that the drilldown carries over the global filters and date range.
++
+Your input should look similar to this:
++
+[role="screenshot"]
+image::images/drilldown_create.png[Create drilldown with entries for drilldown name and destination]
+
+. Click *Create drilldown.*
+
+. Save the dashboard.
++
+If you don’t save the drilldown, and then navigate away, the drilldown is lost.
+
+. In *[Logs] Visitors by OS*, click the `win 8` slice of the pie, and then select the name of your drilldown.
++
+[role="screenshot"]
+image::images/drilldown_on_panel.png[Drilldown on pie chart that navigates to another dashboard]
++
+You are navigated to your destination dashboard. Verify that the search query, filters,
+and time range are carried over.

docs/settings/alert-action-settings.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[alert-action-settings-kb]]
-=== Alerting and action settings in Kibana
+=== Alerting and action settings in {kib}
 ++++
 <titleabbrev>Alerting and action settings</titleabbrev>
 ++++

docs/settings/apm-settings.asciidoc

@@ -12,7 +12,7 @@ It is enabled by default.
 
 [float]
 [[apm-indices-settings-kb]]
-==== APM Indices
+==== APM indices
 
 // This content is reused in the APM app documentation.
 // Any changes made in this file will be seen there as well.

docs/settings/dev-settings.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[dev-settings-kb]]
-=== Development tools settings in Kibana
+=== Development tools settings in {kib}
 ++++
 <titleabbrev>Development tools settings</titleabbrev>
 ++++
@@ -21,7 +21,7 @@ They are enabled by default.
 
 [float]
 [[profiler-settings]]
-==== {searchprofiler} Settings
+==== {searchprofiler} settings
 
 [cols="2*<"]
 |===

docs/settings/graph-settings.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[graph-settings-kb]]
-=== Graph settings in Kibana
+=== Graph settings in {kib}
 ++++
 <titleabbrev>Graph settings</titleabbrev>
 ++++

docs/settings/i18n-settings.asciidoc

@@ -1,12 +1,15 @@
 [role="xpack"]
 [[i18n-settings-kb]]
-=== i18n settings in Kibana
+=== i18n settings in {kib}
+++++
+<titleabbrev>i18n settings</titleabbrev>
+++++
 
 You do not need to configure any settings to run Kibana in English.
 
 [float]
 [[general-i18n-settings-kb]]
-==== General i18n Settings
+==== General i18n settings
 
 `i18n.locale`::
   {kib} supports the following locales:

docs/settings/infrastructure-ui-settings.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[infrastructure-ui-settings-kb]]
-=== Metrics settings in Kibana
+=== Metrics settings in {kib}
 ++++
 <titleabbrev>Metrics settings</titleabbrev>
 ++++
@@ -11,4 +11,4 @@ You do not need to configure any settings to use the Metrics app in {kib}. It is
 [[general-infra-ui-settings-kb]]
 ==== General Metrics settings
 
-include::general-infra-logs-ui-settings.asciidoc[]
+include::general-infra-logs-ui-settings.asciidoc[]

docs/settings/logs-ui-settings.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[logs-ui-settings-kb]]
-=== Logs app settings in Kibana
+=== Logs settings in {kib}
 ++++
 <titleabbrev>Logs settings</titleabbrev>
 ++++

docs/settings/ml-settings.asciidoc

@@ -1,12 +1,12 @@
 [role="xpack"]
 [[ml-settings-kb]]
-=== Machine learning settings in Kibana
+=== Machine learning settings in {kib}
 ++++
 <titleabbrev>Machine learning settings</titleabbrev>
 ++++
 
 You do not need to configure any settings to use {kib} {ml-features}. They are
-enabled by default. 
+enabled by default.
 
 [[general-ml-settings-kb]]
 ==== General {ml} settings
@@ -26,4 +26,4 @@ enabled by default.
 [[advanced-ml-settings-kb]]
 ==== Advanced {ml} settings
 
-Refer to <<kibana-ml-settings,Advanced {ml} settings in {kib}>>.
+Refer to <<kibana-ml-settings,Advanced {ml} settings in {kib}>>.

docs/settings/monitoring-settings.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[monitoring-settings-kb]]
-=== Monitoring settings in Kibana
+=== Monitoring settings in {kib}
 ++++
 <titleabbrev>Monitoring settings</titleabbrev>
 ++++

docs/settings/reporting-settings.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[reporting-settings-kb]]
-=== Reporting settings in Kibana
+=== Reporting settings in {kib}
 ++++
 <titleabbrev>Reporting settings</titleabbrev>
 ++++

docs/settings/security-settings.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[security-settings-kb]]
-=== Security settings in Kibana
+=== Security settings in {kib}
 ++++
 <titleabbrev>Security settings</titleabbrev>
 ++++

docs/settings/settings-xkb.asciidoc

@@ -1,9 +1,9 @@
 [role="xpack"]
 [[settings-xpack-kb]]
-== {xpack} Settings in {kib}
+== {xpack} settings in {kib}
 [subs="attributes"]
 ++++
-<titleabbrev>{xpack} Settings</titleabbrev>
+<titleabbrev>{xpack} settings</titleabbrev>
 ++++
 
 include::{asciidoc-dir}/../../shared/settings.asciidoc[]

docs/settings/telemetry-settings.asciidoc

@@ -1,5 +1,5 @@
 [[telemetry-settings-kbn]]
-=== Telemetry settings in Kibana
+=== Telemetry settings in {kib}
 ++++
 <titleabbrev>Telemetry settings</titleabbrev>
 ++++
@@ -29,7 +29,7 @@ See our https://www.elastic.co/legal/privacy-statement[Privacy Statement] to lea
   | Set to `'server'` to report the cluster statistics from the {kib} server.
   If the server fails to connect to our endpoint at https://telemetry.elastic.co/, it assumes
   it is behind a firewall and falls back to `'browser'` to send it from users' browsers
-  when they are navigating through {kib}. Defaults to 'browser'.
+  when they are navigating through {kib}. Defaults to `'server'`.
 
 | `telemetry.optIn`
   | Set to `true` to automatically opt into reporting cluster statistics. You can also opt out through

docs/setup/access.asciidoc

@@ -1,5 +1,5 @@
 [[access]]
-== Accessing Kibana
+== Access {kib}
 
 Kibana is a web application that you access through port 5601. All you need to do is point your web browser at the
 machine where Kibana is running and specify the port number. For example, `localhost:5601` or `http://YOURDOMAIN.com:5601`.
@@ -13,7 +13,7 @@ If you still don't see any results, it's possible that you don't *have* any docu
 
 [float]
 [[status]]
-=== Checking Kibana Status
+=== Check {kib} status
 
 You can reach the Kibana server's status page by navigating to the status endpoint, for example, `localhost:5601/status`. The status page displays
 information about the server's resource usage and lists the installed plugins.

docs/setup/connect-to-elasticsearch.asciidoc

@@ -1,5 +1,5 @@
 [[connect-to-elasticsearch]]
-== Adding data
+== Add data to {kib}
 
 To start working with your data in {kib}, you can: