Merge branch 'master' into fix/saved-query-overlay

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

@@ -8,6 +8,9 @@
 
 ```typescript
 readonly links: {
+        readonly dashboard: {
+            readonly drilldowns: string;
+        };
         readonly filebeat: {
             readonly base: string;
             readonly installation: string;

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

@@ -17,5 +17,5 @@ export interface DocLinksSetup
 |  --- | --- | --- |
 |  [DOC\_LINK\_VERSION](./kibana-plugin-core-public.doclinkssetup.doc_link_version.md) | <code>string</code> |  |
 |  [ELASTIC\_WEBSITE\_URL](./kibana-plugin-core-public.doclinkssetup.elastic_website_url.md) | <code>string</code> |  |
-|  [links](./kibana-plugin-core-public.doclinkssetup.links.md) | <code>{</code><br/><code>        readonly filebeat: {</code><br/><code>            readonly base: string;</code><br/><code>            readonly installation: string;</code><br/><code>            readonly configuration: string;</code><br/><code>            readonly elasticsearchOutput: string;</code><br/><code>            readonly startup: string;</code><br/><code>            readonly exportedFields: string;</code><br/><code>        };</code><br/><code>        readonly auditbeat: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly metricbeat: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly heartbeat: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly logstash: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly functionbeat: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly winlogbeat: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly aggs: {</code><br/><code>            readonly date_histogram: string;</code><br/><code>            readonly date_range: string;</code><br/><code>            readonly filter: string;</code><br/><code>            readonly filters: string;</code><br/><code>            readonly geohash_grid: string;</code><br/><code>            readonly histogram: string;</code><br/><code>            readonly ip_range: string;</code><br/><code>            readonly range: string;</code><br/><code>            readonly significant_terms: string;</code><br/><code>            readonly terms: string;</code><br/><code>            readonly avg: string;</code><br/><code>            readonly avg_bucket: string;</code><br/><code>            readonly max_bucket: string;</code><br/><code>            readonly min_bucket: string;</code><br/><code>            readonly sum_bucket: string;</code><br/><code>            readonly cardinality: string;</code><br/><code>            readonly count: string;</code><br/><code>            readonly cumulative_sum: string;</code><br/><code>            readonly derivative: string;</code><br/><code>            readonly geo_bounds: string;</code><br/><code>            readonly geo_centroid: string;</code><br/><code>            readonly max: string;</code><br/><code>            readonly median: string;</code><br/><code>            readonly min: string;</code><br/><code>            readonly moving_avg: string;</code><br/><code>            readonly percentile_ranks: string;</code><br/><code>            readonly serial_diff: string;</code><br/><code>            readonly std_dev: string;</code><br/><code>            readonly sum: string;</code><br/><code>            readonly top_hits: string;</code><br/><code>        };</code><br/><code>        readonly scriptedFields: {</code><br/><code>            readonly scriptFields: string;</code><br/><code>            readonly scriptAggs: string;</code><br/><code>            readonly painless: string;</code><br/><code>            readonly painlessApi: string;</code><br/><code>            readonly painlessSyntax: string;</code><br/><code>            readonly luceneExpressions: string;</code><br/><code>        };</code><br/><code>        readonly indexPatterns: {</code><br/><code>            readonly loadingData: string;</code><br/><code>            readonly introduction: string;</code><br/><code>        };</code><br/><code>        readonly kibana: string;</code><br/><code>        readonly siem: {</code><br/><code>            readonly guide: string;</code><br/><code>            readonly gettingStarted: string;</code><br/><code>        };</code><br/><code>        readonly query: {</code><br/><code>            readonly luceneQuerySyntax: string;</code><br/><code>            readonly queryDsl: string;</code><br/><code>            readonly kueryQuerySyntax: string;</code><br/><code>        };</code><br/><code>        readonly date: {</code><br/><code>            readonly dateMath: string;</code><br/><code>        };</code><br/><code>        readonly management: Record&lt;string, string&gt;;</code><br/><code>    }</code> |  |
+|  [links](./kibana-plugin-core-public.doclinkssetup.links.md) | <code>{</code><br/><code>        readonly dashboard: {</code><br/><code>            readonly drilldowns: string;</code><br/><code>        };</code><br/><code>        readonly filebeat: {</code><br/><code>            readonly base: string;</code><br/><code>            readonly installation: string;</code><br/><code>            readonly configuration: string;</code><br/><code>            readonly elasticsearchOutput: string;</code><br/><code>            readonly startup: string;</code><br/><code>            readonly exportedFields: string;</code><br/><code>        };</code><br/><code>        readonly auditbeat: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly metricbeat: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly heartbeat: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly logstash: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly functionbeat: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly winlogbeat: {</code><br/><code>            readonly base: string;</code><br/><code>        };</code><br/><code>        readonly aggs: {</code><br/><code>            readonly date_histogram: string;</code><br/><code>            readonly date_range: string;</code><br/><code>            readonly filter: string;</code><br/><code>            readonly filters: string;</code><br/><code>            readonly geohash_grid: string;</code><br/><code>            readonly histogram: string;</code><br/><code>            readonly ip_range: string;</code><br/><code>            readonly range: string;</code><br/><code>            readonly significant_terms: string;</code><br/><code>            readonly terms: string;</code><br/><code>            readonly avg: string;</code><br/><code>            readonly avg_bucket: string;</code><br/><code>            readonly max_bucket: string;</code><br/><code>            readonly min_bucket: string;</code><br/><code>            readonly sum_bucket: string;</code><br/><code>            readonly cardinality: string;</code><br/><code>            readonly count: string;</code><br/><code>            readonly cumulative_sum: string;</code><br/><code>            readonly derivative: string;</code><br/><code>            readonly geo_bounds: string;</code><br/><code>            readonly geo_centroid: string;</code><br/><code>            readonly max: string;</code><br/><code>            readonly median: string;</code><br/><code>            readonly min: string;</code><br/><code>            readonly moving_avg: string;</code><br/><code>            readonly percentile_ranks: string;</code><br/><code>            readonly serial_diff: string;</code><br/><code>            readonly std_dev: string;</code><br/><code>            readonly sum: string;</code><br/><code>            readonly top_hits: string;</code><br/><code>        };</code><br/><code>        readonly scriptedFields: {</code><br/><code>            readonly scriptFields: string;</code><br/><code>            readonly scriptAggs: string;</code><br/><code>            readonly painless: string;</code><br/><code>            readonly painlessApi: string;</code><br/><code>            readonly painlessSyntax: string;</code><br/><code>            readonly luceneExpressions: string;</code><br/><code>        };</code><br/><code>        readonly indexPatterns: {</code><br/><code>            readonly loadingData: string;</code><br/><code>            readonly introduction: string;</code><br/><code>        };</code><br/><code>        readonly kibana: string;</code><br/><code>        readonly siem: {</code><br/><code>            readonly guide: string;</code><br/><code>            readonly gettingStarted: string;</code><br/><code>        };</code><br/><code>        readonly query: {</code><br/><code>            readonly luceneQuerySyntax: string;</code><br/><code>            readonly queryDsl: string;</code><br/><code>            readonly kueryQuerySyntax: string;</code><br/><code>        };</code><br/><code>        readonly date: {</code><br/><code>            readonly dateMath: string;</code><br/><code>        };</code><br/><code>        readonly management: Record&lt;string, string&gt;;</code><br/><code>    }</code> |  |
 

docs/maps/connect-to-ems.asciidoc

@@ -1,17 +1,17 @@
 [role="xpack"]
 [[maps-connect-to-ems]]
-== Connecting to Elastic Maps Service
+== Connect to Elastic Maps Service
 
 https://www.elastic.co/elastic-maps-service[Elastic Maps Service (EMS)] is a service that hosts
 tile layers and vector shapes of administrative boundaries.
-If you are using Kibana's out-of-the-box settings, **Elastic Maps** is already configured to use EMS.
+If you are using Kibana's out-of-the-box settings, Maps is already configured to use EMS.
 
 EMS requests are made to the following domains:
 
 * tiles.maps.elastic.co
 * vector.maps.elastic.co
 
-**Elastic Maps** makes requests directly from the browser to EMS.
+Maps makes requests directly from the browser to EMS.
 
 [float]
 === Connect to Elastic Maps Service from an internal network
@@ -33,5 +33,5 @@ behind a firewall. If this happens, you can disable the EMS connection to avoid
 To disable EMS, change your <<settings, kibana.yml>> file.
 
 . Set `map.includeElasticMapsService` to `false` to turn off the EMS connection.
-. Set `map.tilemap.url` to the URL of your tile server. This configures the default tile layer of **Elastic Maps**.
+. Set `map.tilemap.url` to the URL of your tile server. This configures the default tile layer of Maps.
 . (Optional) Set `map.regionmap` to the vector shapes of the administrative boundaries that you want to use.

docs/maps/geojson-upload.asciidoc

@@ -1,11 +1,13 @@
 [role="xpack"]
 [[geojson-upload]]
 == Upload GeoJSON data
-*Elastic Maps* makes it easy to import geospatial data into the Elastic Stack.
-Using the *GeoJSON Upload* feature, you can drag and drop your point and shape
+
+Maps makes it easy to import geospatial data into the Elastic Stack.
+Using the GeoJSON Upload feature, you can drag and drop your point and shape
 data files directly into {es}, and then use them as layers
 in the map.  You can also use the GeoJSON data in the broader Kibana ecosystem,
 for example, in visualizations and Canvas workpads.
+
 [float]
 === Why GeoJSON?
 GeoJSON is an open-standard file format for storing geospatial vector data.
@@ -17,7 +19,7 @@ GeoJSON is the most commonly used and flexible option.
 Follow these instructions to upload a GeoJSON data file, or try the
 <<indexing-geojson-data-tutorial, end-to-end integrated example>>.
 
-. Open the menu, go to *Elastic Maps*, and then click *Add layer*.
+. Open the menu, go to *Maps*, and then click *Add layer*.
 . Click *Uploaded GeoJSON*.
 +
 [role="screenshot"]

docs/maps/index.asciidoc

@@ -1,21 +1,21 @@
 [role="xpack"]
 [[maps]]
-= Elastic Maps
+= Maps
 
 [partintro]
 --
 
-*Elastic Maps* enables you to parse through your geographical data at scale, with speed, and in real time. With features like multiple layers and indices in a map, plotting of raw documents, dynamic client-side styling, and global search across multiple layers, you can understand and monitor your data with ease.
+Maps enables you to parse through your geographical data at scale, with speed, and in real time. With features like multiple layers and indices in a map, plotting of raw documents, dynamic client-side styling, and global search across multiple layers, you can understand and monitor your data with ease.
 
-With *Elastic Maps*, you can:
+With Maps, you can:
 
 * Create maps with multiple layers and indices.
 * Upload GeoJSON files into Elasticsearch.
 * Embed your map in dashboards.
 * Symbolize features using data values.
 * Focus in on just the data you want.
 
-*Ready to get started?* Start your tour of *Elastic Maps* with the <<maps-getting-started, getting started tutorial>>.
+*Ready to get started?* Start your tour of Maps with the <<maps-getting-started, getting started tutorial>>.
 
 [float]
 === Create maps with multiple layers and indices
@@ -26,7 +26,7 @@ image::maps/images/sample_data_ecommerce.png[]
 
 [float]
 === Upload GeoJSON files into Elasticsearch
-Elastic Maps makes it easy to import geospatial data into the Elastic Stack. Using the GeoJSON Upload feature, you can drag and drop your point and shape data files directly into Elasticsearch, and then use them as layers in the map.
+Maps makes it easy to import geospatial data into the Elastic Stack. Using the GeoJSON Upload feature, you can drag and drop your point and shape data files directly into Elasticsearch, and then use them as layers in the map.
 
 [float]
 === Embed your map in dashboards

docs/maps/indexing-geojson-data-tutorial.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[indexing-geojson-data-tutorial]]
-== Indexing GeoJSON data tutorial
+=== Tutorial: Index GeoJSON data
 
 In this tutorial, you'll build a customized map that shows the flight path between
 two airports, and the lightning hot spots on that route. You'll learn to:
@@ -15,7 +15,7 @@ two airports, and the lightning hot spots on that route. You'll learn to:
 This tutorial requires you to download the following GeoJSON sample data files.
 These files are good examples of the types
 of vector data that you can upload to Kibana and index in
-Elasticsearch for display in *Elastic Maps*.
+Elasticsearch for display in  Maps.
 
 * https://raw.githubusercontent.com/elastic/examples/master/Maps/Getting%20Started%20Examples/geojson_upload_and_styling/logan_international_airport.geojson[Logan International Airport]
 * https://raw.githubusercontent.com/elastic/examples/master/Maps/Getting%20Started%20Examples/geojson_upload_and_styling/bangor_international_airport.geojson[Bangor International Airport]

docs/maps/map-settings.asciidoc

@@ -1,8 +1,8 @@
 [role="xpack"]
 [[maps-settings]]
-== Map settings
+== Configure map settings
 
-Elastic Maps offers settings that let you configure how a map is displayed.
+Maps offers settings that let you configure how a map is displayed.
 To access these settings, click *Map settings* in the application toolbar.
 
 [float]

docs/maps/maps-aggregations.asciidoc

@@ -2,6 +2,11 @@
 [[maps-aggregations]]
 == Plot big data without plotting too much data
 
+++++
+<titleabbrev>Plot big data</titleabbrev>
+++++
+
+
 Use {ref}/search-aggregations.html[aggregations] to plot large data sets without overwhelming your network or your browser.
 When using aggregations, the documents stay in Elasticsearch and only the calculated values for each group are returned to your computer.
 
@@ -37,7 +42,7 @@ image::maps/images/grid_to_docs.gif[]
 [[maps-grid-aggregation]]
 === Grid aggregation
 
-*Grid aggregation* layers use {ref}/search-aggregations-bucket-geotilegrid-aggregation.html[GeoTile grid aggregation] to group your documents into grids. You can calculate metrics for each gridded cell.
+Grid aggregation layers use {ref}/search-aggregations-bucket-geotilegrid-aggregation.html[GeoTile grid aggregation] to group your documents into grids. You can calculate metrics for each gridded cell.
 
 Symbolize grid aggregation metrics as:
 
@@ -213,7 +218,7 @@ The following shows an example terms aggregation response. Note the *key* proper
 }
 --------------------------------------------------
 
-==== Augmenting the left source with metrics from the right source
+==== Augment the left source with metrics from the right source
 
 The join adds metrics for each terms aggregation bucket to the world country feature with the corresponding ISO 3166-1 alpha-2 code. Features that do not have a corresponding terms aggregation bucket are not visible on the map.
 

docs/maps/maps-getting-started.asciidoc

@@ -1,8 +1,14 @@
 [role="xpack"]
 [[maps-getting-started]]
-== Getting started with Elastic Maps
+== Get started with Maps
 
-You work with *Elastic Maps* by adding layers. The data for a layer can come from
+++++
+<titleabbrev>Get started</titleabbrev>
+++++
+
+
+
+You work with Maps by adding layers. The data for a layer can come from
 sources such as {es} documents, vector sources, tile map services, web map
 services, and more. You can symbolize the data in different ways.
 For example, you might show which airports have the longest flight
@@ -25,7 +31,7 @@ image::maps/images/read-only-badge.png[Example of Maps' read only access indicat
 [float]
 === Prerequisites
 Before you start this tutorial, <<add-sample-data, add the web logs sample data set>>. Each
-sample data set includes a map to go along with the data. Once you've added the data, open *Elastic Maps* and
+sample data set includes a map to go along with the data. Once you've added the data, open Maps and
 explore the different layers of the *[Logs] Total Requests and Bytes* map.
 You'll re-create this map in this tutorial.
 
@@ -40,7 +46,7 @@ In this tutorial, you'll learn to:
 
 [role="xpack"]
 [[maps-create]]
-=== Creating a new map
+=== Create a map
 
 The first thing to do is to create a new map.
 
@@ -55,7 +61,7 @@ image::maps/images/gs_create_new_map.png[]
 
 [role="xpack"]
 [[maps-add-choropleth-layer]]
-=== Adding a choropleth layer
+=== Add a choropleth layer
 
 Now that you have a map, you'll want to add layers to it.
 The first layer you'll add is a choropleth layer to shade world countries
@@ -106,7 +112,7 @@ image::maps/images/gs_add_cloropeth_layer.png[]
 
 [role="xpack"]
 [[maps-add-elasticsearch-layer]]
-=== Adding layers for {es} data
+=== Add layers for the {es} data
 
 To avoid overwhelming the user with too much data at once, you'll add two layers for {es} data.
 
@@ -183,7 +189,7 @@ image::maps/images/sample_data_web_logs.png[]
 
 [role="xpack"]
 [[maps-save]]
-=== Saving the map
+=== Save the map
 Now that your map is complete, you'll want to save it so others can use it.
 
 . In the application toolbar, click *Save*.
@@ -202,7 +208,7 @@ You have completed the steps for re-creating the sample data map.
 
 [role="xpack"]
 [[maps-embedding]]
-=== Adding the map to a dashboard
+=== Add the map to a dashboard
 You can add your saved map to a {kibana-ref}/dashboard.html[dashboard] and view your geospatial data alongside bar charts, pie charts, and other visualizations.
 
 . Open the menu, then go to *Dashboard*.
@@ -224,7 +230,7 @@ Your dashboard should look like this:
 [role="screenshot"]
 image::maps/images/gs_dashboard_with_map.png[]
 
-==== Exploring your data using filters
+==== Explore your data using filters
 
 You can apply filters to your dashboard to hone in on the data that you are most interested in.
 The dashboard is interactive--you can quickly create filters by clicking on the desired data in the map and visualizations.