Merge branch 'master' into retry-flaky-tests

.github/CODEOWNERS

@@ -129,6 +129,7 @@
 # Kibana Alerting Services
 /x-pack/legacy/plugins/alerting/ @elastic/kibana-alerting-services
 /x-pack/legacy/plugins/actions/ @elastic/kibana-alerting-services
+/x-pack/plugins/event_log/ @elastic/kibana-alerting-services
 /x-pack/plugins/task_manager/ @elastic/kibana-alerting-services
 /x-pack/test/alerting_api_integration/ @elastic/kibana-alerting-services
 /x-pack/test/plugin_api_integration/plugins/task_manager/ @elastic/kibana-alerting-services
@@ -150,6 +151,6 @@
 /x-pack/legacy/plugins/license_management/ @elastic/es-ui
 /x-pack/legacy/plugins/remote_clusters/ @elastic/es-ui
 /x-pack/legacy/plugins/rollup/ @elastic/es-ui
-/x-pack/legacy/plugins/searchprofiler/ @elastic/es-ui
+/x-pack/plugins/searchprofiler/ @elastic/es-ui
 /x-pack/legacy/plugins/snapshot_restore/ @elastic/es-ui
 /x-pack/legacy/plugins/watcher/ @elastic/es-ui

docs/developer/visualize/development-create-visualization.asciidoc

@@ -62,7 +62,7 @@ The list of common parameters:
 - *visualization*: A constructor function for a Visualization.
 - *requestHandler*: <string> one of the available request handlers or a <function> for a custom request handler
 - *responseHandler*: <string> one of the available response handlers or a <function> for a custom response handler
-- *editor*: <string> one of the available editors or Editor class for custom one
+- *editor*: Editor class for custom one
 - *editorConfig*: object holding editor parameters
 - *options.showTimePicker*: <bool> show or hide time filter (defaults to true)
 - *options.showQueryBar*: <bool> show or hide query bar (defaults to true)
@@ -218,7 +218,6 @@ These tabs should be React components.
  title: 'My New Vis',
  icon: 'my_icon',
  description: 'Cool new chart',
- editor: 'default',
  editorConfig: {
  optionsTemplate: MyReactComponent // or if multiple tabs are required:
  optionTabs: [

docs/development/core/server/kibana-plugin-server.kibanarequest.events.md

@@ -0,0 +1,13 @@
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [kibana-plugin-server](./kibana-plugin-server.md) &gt; [KibanaRequest](./kibana-plugin-server.kibanarequest.md) &gt; [events](./kibana-plugin-server.kibanarequest.events.md)
+
+## KibanaRequest.events property
+
+Request events [KibanaRequestEvents](./kibana-plugin-server.kibanarequestevents.md)
+
+<b>Signature:</b>
+
+```typescript
+readonly events: KibanaRequestEvents;
+```

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

@@ -23,10 +23,11 @@ export declare class KibanaRequest<Params = unknown, Query = unknown, Body = unk
 | Property | Modifiers | Type | Description |
 | --- | --- | --- | --- |
 | [body](./kibana-plugin-server.kibanarequest.body.md) | | <code>Body</code> | |
+| [events](./kibana-plugin-server.kibanarequest.events.md) | | <code>KibanaRequestEvents</code> | Request events [KibanaRequestEvents](./kibana-plugin-server.kibanarequestevents.md) |
 | [headers](./kibana-plugin-server.kibanarequest.headers.md) | | <code>Headers</code> | Readonly copy of incoming request headers. |
 | [params](./kibana-plugin-server.kibanarequest.params.md) | | <code>Params</code> | |
 | [query](./kibana-plugin-server.kibanarequest.query.md) | | <code>Query</code> | |
 | [route](./kibana-plugin-server.kibanarequest.route.md) | | <code>RecursiveReadonly&lt;KibanaRequestRoute&lt;Method&gt;&gt;</code> | matched route details |
-| [socket](./kibana-plugin-server.kibanarequest.socket.md) | | <code>IKibanaSocket</code> | |
+| [socket](./kibana-plugin-server.kibanarequest.socket.md) | | <code>IKibanaSocket</code> | [IKibanaSocket](./kibana-plugin-server.ikibanasocket.md) |
 | [url](./kibana-plugin-server.kibanarequest.url.md) | | <code>Url</code> | a WHATWG URL standard object. |
 

docs/development/core/server/kibana-plugin-server.kibanarequest.socket.md

@@ -4,6 +4,8 @@
 
 ## KibanaRequest.socket property
 
+[IKibanaSocket](./kibana-plugin-server.ikibanasocket.md)
+
 <b>Signature:</b>
 
 ```typescript

docs/development/core/server/kibana-plugin-server.kibanarequestevents.aborted_.md

@@ -0,0 +1,13 @@
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [kibana-plugin-server](./kibana-plugin-server.md) &gt; [KibanaRequestEvents](./kibana-plugin-server.kibanarequestevents.md) &gt; [aborted$](./kibana-plugin-server.kibanarequestevents.aborted_.md)
+
+## KibanaRequestEvents.aborted$ property
+
+Observable that emits once if and when the request has been aborted.
+
+<b>Signature:</b>
+
+```typescript
+aborted$: Observable<void>;
+```

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

@@ -0,0 +1,20 @@
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [kibana-plugin-server](./kibana-plugin-server.md) &gt; [KibanaRequestEvents](./kibana-plugin-server.kibanarequestevents.md)
+
+## KibanaRequestEvents interface
+
+Request events.
+
+<b>Signature:</b>
+
+```typescript
+export interface KibanaRequestEvents 
+```
+
+## Properties
+
+| Property | Type | Description |
+| --- | --- | --- |
+| [aborted$](./kibana-plugin-server.kibanarequestevents.aborted_.md) | <code>Observable&lt;void&gt;</code> | Observable that emits once if and when the request has been aborted. |
+

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

@@ -76,6 +76,7 @@ The plugin integrates with the core system via lifecycle events: `setup`<!-- -->
 | [IRouter](./kibana-plugin-server.irouter.md) | Registers route handlers for specified resource path and method. See [RouteConfig](./kibana-plugin-server.routeconfig.md) and [RequestHandler](./kibana-plugin-server.requesthandler.md) for more information about arguments to route registrations. |
 | [IScopedRenderingClient](./kibana-plugin-server.iscopedrenderingclient.md) | |
 | [IUiSettingsClient](./kibana-plugin-server.iuisettingsclient.md) | Server-side client that provides access to the advanced settings stored in elasticsearch. The settings provide control over the behavior of the Kibana application. For example, a user can specify how to display numeric or date fields. Users can adjust the settings via Management UI. |
+| [KibanaRequestEvents](./kibana-plugin-server.kibanarequestevents.md) | Request events. |
 | [KibanaRequestRoute](./kibana-plugin-server.kibanarequestroute.md) | Request specific route information exposed to a handler. |
 | [LegacyRequest](./kibana-plugin-server.legacyrequest.md) | |
 | [LegacyServiceSetupDeps](./kibana-plugin-server.legacyservicesetupdeps.md) | |

docs/setup/settings.asciidoc

@@ -229,23 +229,25 @@ Kibana, the server needs to be CORS-enabled so Kibana can download the file.
 The following example shows a valid regionmap configuration.
 +
 --
- map.regionmap:
+ map
  includeElasticMapsService: false
- layers:
- - name: "Departments of France"
- url: "http://my.cors.enabled.server.org/france_departements.geojson"
- attribution: "INRAP"
- fields:
- - name: "department"
+ regionmap:
+ layers:
+ - name: "Departments of France"
+ url: "http://my.cors.enabled.server.org/france_departements.geojson"
+ attribution: "INRAP"
+ fields:
+ - name: "department"
  description: "Full department name"
- - name: "INSEE"
+  - name: "INSEE"
  description: "INSEE numeric identifier"
 --
 
-[[regionmap-ES-map]]`map.regionmap.includeElasticMapsService:`:: Turns on or off
+[[regionmap-ES-map]]`map.includeElasticMapsService:`:: Turns on or off
 whether layers from the Elastic Maps Service should be included in the vector
 layer option list. Supported on Elastic Cloud Enterprise. By turning this off,
-only the layers that are configured here will be included. The default is `true`.
+only the layers that are configured here will be included. The default is `true`. 
+This also affects whether tile-service from the Elastic Maps Service will be available.
 
 [[regionmap-attribution]]`map.regionmap.layers[].attribution:`:: Optional.
 References the originating source of the geojson file. Supported on {ece}.

docs/user/security/securing-communications/index.asciidoc

@@ -4,8 +4,9 @@
 <titleabbrev>Encrypting communications</titleabbrev>
 ++++
 
-{kib} supports Transport Layer Security (TLS/SSL) encryption for all forms of data-in-transit. Browsers send traffic to {kib} and {kib}
-sends traffic to {es}. These communications are configured separately.
+{kib} supports Transport Layer Security (TLS/SSL) encryption for all forms of
+data-in-transit. Browsers send traffic to {kib} and {kib} sends traffic to {es}.
+These communications are configured separately.
 
 [[configuring-tls-browser-kib]]
 ==== Encrypting traffic between the browser and {kib}
@@ -78,15 +79,18 @@ NOTE: To perform this step, you must
 {ref}/configuring-security.html[enable the {es} {security-features}] or you 
 must have a proxy that provides an HTTPS endpoint for {es}. 
 
-. Specify the HTTPS URL in the `elasticsearch.hosts` setting in the {kib} configuration file, `kibana.yml`:
+. Specify the HTTPS URL in the `elasticsearch.hosts` setting in the {kib}
+configuration file, `kibana.yml`:
 +
 --
 [source,yaml]
 --------------------------------------------------------------------------------
 elasticsearch.hosts: ["https://<your_elasticsearch_host>.com:9200"]
 --------------------------------------------------------------------------------
 
-Using the HTTPS protocol results in a default `elasticsearch.ssl.verificationMode` option of `full`, which utilizes hostname verification.
+Using the HTTPS protocol results in a default
+`elasticsearch.ssl.verificationMode` option of `full`, which utilizes hostname
+verification.
 
 For more information, see <<settings,{kib} configuration settings>>. 
 --
@@ -95,24 +99,32 @@ For more information, see <<settings,{kib} configuration settings>>.
 +
 --
 
-If you are using your own CA to sign certificates for {es}, then you need to specify the CA certificate chain in {kib} to properly establish
-trust in TLS connections. If your CA certificate chain is contained in a PKCS #12 trust store, specify it like so:
+If you are using your own CA to sign certificates for {es}, then you need to
+specify the CA certificate chain in {kib} to properly establish trust in TLS
+connections. If your CA certificate chain is contained in a PKCS #12 trust store,
+specify it like so:
 
 [source,yaml]
 --------------------------------------------------------------------------------
 elasticsearch.ssl.truststore.path: "/path/to/your/truststore.p12"
 elasticsearch.ssl.truststore.password: "optional decryption password"
 --------------------------------------------------------------------------------
 
-Otherwise, if your CA certificate chain is in PEM format, specify each certificate like so:
+Otherwise, if your CA certificate chain is in PEM format, specify each
+certificate like so:
 
 [source,yaml]
 --------------------------------------------------------------------------------
 elasticsearch.ssl.certificateAuthorities: ["/path/to/your/cacert1.pem", "/path/to/your/cacert2.pem"]
 --------------------------------------------------------------------------------
 
+TIP: You can use the {ref}/certutil.html[`elasticsearch-certutil http` command]
+to generate a PEM format x.509 certificate for the {es} CA. It also provides
+detailed configuration details in readme files.
+
 --
 
-. (Optional) If the Elastic {monitor-features} are enabled, configure {kib} to connect to the {es} monitoring cluster via HTTPS. The steps
-are the same as above, but each setting is prefixed by `xpack.monitoring.`. For example, `xpack.monitoring.elasticsearch.hosts`,
+. (Optional) If the Elastic {monitor-features} are enabled, configure {kib} to
+connect to the {es} monitoring cluster via HTTPS. The steps are the same as
+above, but each setting is prefixed by `xpack.monitoring.`. For example, `xpack.monitoring.elasticsearch.hosts`,
 `xpack.monitoring.elasticsearch.ssl.truststore.path`, etc.

docs/user/visualize.asciidoc

@@ -3,9 +3,9 @@
 
 [partintro]
 --
-_Visualize_ enables you to create visualizations of the data from your Elasticsearch indices, which you can then add to dashboards for analysis.
+_Visualize_ enables you to create visualizations of the data from your {es} indices, which you can then add to dashboards for analysis.
 
-{kib} visualizations are based on Elasticsearch queries. By using a series of {es} {ref}/search-aggregations.html[aggregations] to extract and process your data, you can create charts that show you the trends, spikes, and dips you need to know about.
+{kib} visualizations are based on {es} queries. By using a series of {es} {ref}/search-aggregations.html[aggregations] to extract and process your data, you can create charts that show you the trends, spikes, and dips you need to know about.
 
 [float]
 [[create-a-visualization]]
@@ -15,52 +15,72 @@ _Visualize_ enables you to create visualizations of the data from your Elasticse
 . Click *Create new visualization*.
 . Choose the visualization type:
 +
-* *Basic charts*
-<<lens,Lens>>:: Quickly build several types of basic visualizations by simply dragging and dropping the data fields you want to display.
+* Basic charts
+[horizontal]
+<<lens,Lens>>::
+Quickly build several types of basic visualizations by simply dragging and dropping the data fields you want to display.
+
 * *<<most-frequent,Most frequently used visualizations>>*
 [horizontal]
 Line&comma; area, and bar charts:: Compare different series in X/Y charts.
+
 Pie chart:: Display each source contribution to a total.
+
 Data table:: Flattens aggregations into table format.
+
 Metric:: Display a single number.
+
 Goal and gauge:: Display a number with progress indicators.
-Heat maps:: Display shaded cells within a matrix.
+
 Tag cloud:: Display words in a cloud, where the size of the word corresponds to its importance.
+
 * *Time series optimized*
 [horizontal]
 <<TSVB,TSVB>>:: Visualize time series data using pipeline aggregations.
+
 <<timelion,Timelion>>:: Compute and combine data from multiple time series
 data sets.
+
 * *Maps*
 [horizontal]
-<<maps, Elastic maps>>:: The most powerful way of visualizing map data in {kib}.
-<<tilemap,_Coordinate map_>>:: Displays points on a map using a geohash aggregation.
-<<regionmap,_Region map_>>:: Merge any structured map data onto a shape.
-* *<<for-dashboard, For use in dashboards>>*
+<<maps,Elastic Maps>>:: The most powerful way of visualizing map data in {kib}.
+
+<<tilemap,Coordinate map>>:: Displays points on a map using a geohash aggregation.
+
+<<regionmap,Region map>>:: Merge any structured map data onto a shape.
+
+<<heatmap,Heat map>>:: Display shaded cells within a matrix.
+
+* *<<for-dashboard,Dashboard tools>>*
 [horizontal]
 <<for-dashboard,Controls>>:: Provides the ability to add interactive inputs to a Dashboard.
+
 <<for-dashboard,Markdown widget>>:: Display free-form information or instructions.
+
 * *For developers*
 [horizontal]
 <<vega-graph,Vega>>:: Complete control over query and display.
 
 . Specify a search query to retrieve the data for your visualization:
 ** To enter new search criteria, select the <<index-patterns, index pattern>> for the indices that
-contain the data you want to visualize. This opens the visualization builder
+contain the data you want to visualize. The visualization builder opens
 with a wildcard query that matches all of the documents in the selected
 indices.
 ** To build a visualization from a saved search, click the name of the saved
-search you want to use. This opens the visualization builder and loads the
+search you want to use. The visualization builder opens and loads the
 selected query.
 +
 NOTE: When you build a visualization from a saved search, any subsequent
 modifications to the saved search are automatically reflected in the
 visualization. To disable automatic updates, you can disconnect a visualization
 from the saved search.
 
+
 --
 include::{kib-repo-dir}/visualize/visualize_rollup_data.asciidoc[]
 
+include::{kib-repo-dir}/visualize/aggregations.asciidoc[]
+
 include::{kib-repo-dir}/visualize/lens.asciidoc[]
 
 include::{kib-repo-dir}/visualize/most-frequent.asciidoc[]
@@ -70,6 +90,7 @@ include::{kib-repo-dir}/visualize/timelion.asciidoc[]
 
 include::{kib-repo-dir}/visualize/tilemap.asciidoc[]
 include::{kib-repo-dir}/visualize/regionmap.asciidoc[]
+include::{kib-repo-dir}/visualize/heatmap.asciidoc[]
 
 include::{kib-repo-dir}/visualize/for-dashboard.asciidoc[]