Merge branch 'master' into fix/monitor-list-expaned-row-should-follow…

…-filters

.eslintrc.js

@@ -189,13 +189,6 @@ module.exports = {
         'react-hooks/exhaustive-deps': 'off',
       },
     },
-    {
-      files: ['x-pack/legacy/plugins/uptime/**/*.{js,ts,tsx}'],
-      rules: {
-        'react-hooks/exhaustive-deps': 'off',
-        'react-hooks/rules-of-hooks': 'off',
-      },
-    },
 
     /**
      * Files that require Apache 2.0 headers, settings

.github/CODEOWNERS

@@ -8,6 +8,16 @@
 /src/plugins/share/ @elastic/kibana-app
 /src/legacy/server/url_shortening/ @elastic/kibana-app
 /src/legacy/server/sample_data/ @elastic/kibana-app
+/src/legacy/core_plugins/kibana/public/dashboard/ @elastic/kibana-app
+/src/legacy/core_plugins/kibana/public/discover/ @elastic/kibana-app
+/src/legacy/core_plugins/kibana/public/visualize/ @elastic/kibana-app
+/src/legacy/core_plugins/kibana/public/local_application_service/ @elastic/kibana-app
+/src/legacy/core_plugins/kibana/public/home/ @elastic/kibana-app
+/src/legacy/core_plugins/kibana/public/dev_tools/ @elastic/kibana-app
+/src/plugins/home/ @elastic/kibana-app
+/src/plugins/kibana_legacy/ @elastic/kibana-app
+/src/plugins/timelion/ @elastic/kibana-app
+/src/plugins/dev_tools/ @elastic/kibana-app
 
 # App Architecture
 /src/plugins/data/ @elastic/kibana-app-arch
@@ -57,6 +67,13 @@
 /x-pack/test/functional/services/transform_ui/ @elastic/ml-ui
 /x-pack/test/functional/services/transform.ts @elastic/ml-ui
 
+# Maps
+/x-pack/legacy/plugins/maps/ @elastic/kibana-gis
+/x-pack/test/api_integration/apis/maps/ @elastic/kibana-gis
+/x-pack/test/functional/apps/maps/ @elastic/kibana-gis
+/x-pack/test/functional/es_archives/maps/ @elastic/kibana-gis
+/x-pack/test/visual_regression/tests/maps/index.js @elastic/kibana-gis
+
 # Operations
 /src/dev/ @elastic/kibana-operations
 /src/setup_node_env/ @elastic/kibana-operations

.github/workflows/pr-project-assigner.yml

@@ -11,5 +11,11 @@ jobs:
         uses: elastic/github-actions/[email protected]
         id: project_assigner
         with:
-          issue-mappings: '[{"label": "Team:AppAch", "projectName": "kibana-app-arch", "columnId": 6173897}]'
-          ghToken: ${{ secrets.GITHUB_TOKEN }}
+          issue-mappings: |
+            [
+              { "label": "Team:AppArch", "projectName": "kibana-app-arch", "columnId": 6173897 },
+              { "label": "Feature:Lens", "projectName": "Lens", "columnId": 6219362 },
+              { "label": "Team:Platform", "projectName": "kibana-platform", "columnId": 5514360 },
+              {"label": "Team:Canvas", "projectName": "canvas", "columnId": 6187580}
+            ]
+          ghToken: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/project-assigner.yml

@@ -11,7 +11,7 @@ jobs:
         uses: elastic/github-actions/[email protected]
         id: project_assigner
         with:
-          issue-mappings: '[{"label": "Team:AppArch", "projectName": "kibana-app-arch", "columnId": 6173895}]'
+          issue-mappings: '[{"label": "Team:AppArch", "projectName": "kibana-app-arch", "columnId": 6173895}, {"label": "Feature:Lens", "projectName": "Lens", "columnId": 6219363}, {"label": "Team:Canvas", "projectName": "canvas", "columnId": 6187593}]'
           ghToken: ${{ secrets.GITHUB_TOKEN }}
-      
+
 

.gitignore

@@ -29,7 +29,6 @@ disabledPlugins
 webpackstats.json
 /config/*
 !/config/kibana.yml
-!/config/apm.js
 coverage
 selenium
 .babel_register_cache.json

.i18nrc.json

@@ -11,6 +11,7 @@
     "embeddableApi": "src/plugins/embeddable",
     "embeddableExamples": "examples/embeddable_examples",
     "share": "src/plugins/share",
+    "home": "src/plugins/home",
     "esUi": "src/plugins/es_ui_shared",
     "devTools": "src/plugins/dev_tools",
     "expressions": "src/plugins/expressions",

.node-version

@@ -1 +1 @@
-10.15.2
+10.18.0

.nvmrc

@@ -1 +1 @@
-10.15.2
+10.18.0

NOTICE.txt

@@ -1,5 +1,5 @@
 Kibana source code with Kibana X-Pack source code
-Copyright 2012-2019 Elasticsearch B.V.
+Copyright 2012-2020 Elasticsearch B.V.
 
 ---
 Pretty handling of logarithmic axes.

docs/apm/advanced-queries.asciidoc

@@ -1,9 +1,7 @@
 [[advanced-queries]]
 === Advanced queries
 
-When querying, you're simply searching and selecting data from fields in Elasticsearch documents.
-It may be helpful to view some of your documents in {kibana-ref}/discover.html[Discover] to better understand how APM data is stored in Elasticsearch. 
-
+When querying in the APM app, you're simply searching and selecting data from fields in Elasticsearch documents.
 Queries entered into the query bar are also added as parameters to the URL,
 so it's easy to share a specific query or view with others.
 
@@ -13,11 +11,48 @@ In the screenshot below, you can begin to see some of the transaction fields ava
 image::apm/images/apm-query-bar.png[Example of the Kibana Query bar in APM app in Kibana]
 
 [float]
-==== Example queries
+==== Example APM app queries
 
 * Exclude response times slower than 2000 ms: `transaction.duration.us > 2000000`
 * Filter by response status code: `context.response.status_code >= 400`
 * Filter by single user ID: `context.user.id : 12`
-* View _all_ transactions for an endpoint, instead of just a sample - `processor.event: "transaction" AND transaction.name: "<TRANSACTION_NAME_HERE>"`
 
 TIP: Read the {kibana-ref}/kuery-query.html[Kibana Query Language Enhancements] documentation to learn more about the capabilities of the {kib} query language.
+
+[float]
+[[discover-advanced-queries]]
+=== Querying in the Discover app
+
+It may also be helpful to view your APM data in the {kibana-ref}/discover.html[Discover app].
+Querying documents in Discover works the same way as querying in the APM app,
+and all of the example queries listed above can also be used in the Discover app.
+
+[float]
+==== Example Discover app query
+
+One example where you may want to make use of the Discover app,
+is for viewing  _all_ transactions for an endpoint, instead of just a sample.
+
+TIP: Starting in v7.6, you can view 10 samples per bucket in the APM app, instead of just one.
+
+Use the APM app to find a transaction name and time bucket that you're interested in learning more about.
+Then, switch to the Discover app and make a search:
+
+["source","sh"]
+-----
+processor.event: "transaction" AND transaction.name: "<TRANSACTION_NAME_HERE>" and transaction.duration.us > 13000 and transaction.duration.us < 14000`
+-----
+
+In this example, we're interested in viewing all of the `APIRestController#customers` transactions
+that took between 13 and 14 milliseconds. Here's what Discover returns:
+
+[role="screenshot"]
+image::apm/images/advanced-discover.png[View all transactions in bucket]
+
+You can now explore the data until you find a specific transaction that you're interested in.
+Copy that transaction's `transaction.id`, and paste it into the APM app to view the data in the context of the APM app:
+
+[role="screenshot"]
+image::apm/images/specific-transaction-search.png[View specific transaction in apm app]
+[role="screenshot"]
+image::apm/images/specific-transaction.png[View specific transaction in apm app]

docs/canvas/canvas-elements.asciidoc

@@ -20,80 +20,76 @@ When you add elements to your workpad, you can:
 [[add-canvas-element]]
 === Add elements to your workpad
 
-Choose the elements to display on your workpad, then familiarize yourself with the element using the preconfigured demo data.
+Choose the elements to display on your workpad, then familiarize yourself with the element using the preconfigured demo data. By default, every element you add to a workpad uses demo data until you change the data source. The demo data includes a small sample data set that you can use to experiment with your element.
 
 . Click *Add element*.
 
-. In the *Elements* window, select the element you want to use. 
+. In the *Elements* window, select the element you want to use.
 +
 [role="screenshot"]
 image::images/canvas-element-select.gif[Canvas elements]
 
-. Play around with the default settings and see what the element can do. 
+. Play around with the default settings and see what the element can do.
 
-TIP: Want to use a different element? You can delete the element by selecting it, clicking the *Element options* icon in the top right corner, then selecting *Delete*.
+TIP: Want to use a different element? You can delete the element by selecting it, clicking the *Element options* icon in the top right, then selecting *Delete*.
 
 [float]
 [[connect-element-data]]
 === Connect the element to your data
 
-When you are ready to move on from the demo data, connect the element to your own data.
+When you have finished using the demo data, connect the element to a data source.
 
 . Make sure that the element is selected, then select *Data*.
 
 . Click *Change your data source*.
 
 [float]
 [[elasticsearch-sql-data-source]]
-==== Connect to Elasticsearch SQL
+==== Connect to {es} SQL
 
-Access your data in Elasticsearch using the Elasticsearch SQL syntax.
+Access your data in {es} using SQL syntax. For information about SQL syntax, refer to {ref}/sql-spec.html[SQL language].
 
-Unfamiliar with writing Elasticsearch SQL queries? For more information, refer to {ref}/sql-spec.html[SQL language].
+. Click *{es} SQL*.
 
-. Click *Elasticsearch SQL*.
+. In the *{es} SQL query* box, enter your query, then *Preview* it.
 
-. In the *Elasticearch SQL query* box, enter your query, then *Preview* it.
-
-. If everything looks correct, *Save* it. 
+. If everything looks correct, *Save* it.
 
 [float]
 [[elasticsearch-raw-doc-data-source]]
-==== Connect to Elasticsearch raw data
+==== Connect to {es} raw data
 
-Use the Lucene query syntax to use your raw data in Elasticsearch.
+Access your raw data in {es} without the use of aggregations. Use {es} raw data when you have low volume datasets, or to plot exact, non-aggregated values.
 
-For for more information about the Lucene query string sytax, refer to <<lucene-query,Lucene Query Syntax>>.
+To use targeted queries, you can enter a query using the <<lucene-query,Lucene Query Syntax>>.
 
-. Click *Elasticsearch raw documents*.
+. Click *{es} raw documents*.
 
-. In the *Index* field, enter the index pattern that you want to display. 
+. In the *Index* field, enter the index pattern that you want to display.
 
 . From the *Fields* dropdown, select the associated fields you want to display.
 
 . To sort the data, select an option from the *Sort Field* and *Sort Order* dropdowns.
 
-. For more targeted queries, enter a *Query* using the Lucene query string syntax. 
+. For more targeted queries, enter a *Query* using the Lucene query string syntax.
 
-. *Preview* the query. 
+. *Preview* the query.
 
-. If your query looks correct, *Save* it. 
+. If your query looks correct, *Save* it.
 
 [float]
 [[timelion-data-source]]
 ==== Connect to Timelion
 
-Use <<timelion,Timelion>> queries to use your time series data. 
+Access your time series data using <<timelion,Timelion>> queries. To use Timelion queries, you can enter a query using the <<lucene-query,Lucene Query Syntax>>.
 
 . Click *Timelion*.
 
-. Enter a *Query* using the Lucene query string syntax. 
-+
-For for more information about the Lucene query string syntax, refer to <<lucene-query,Lucene Query Syntax>>.
+. Enter a *Query* using the Lucene query string syntax.
 
 . Enter the *Interval*, then *Preview* the query.
 
-. If your query looks correct, *Save* it. 
+. If your query looks correct, *Save* it.
 
 [float]
 [[configure-display-options]]
@@ -109,7 +105,7 @@ When you connect your element to a data source, the element often appears as a w
 
 . Click *Display*
 
-. Change the display options for the element. 
+. Change the display options for the element.
 
 [float]
 [[element-display-container]]
@@ -122,7 +118,7 @@ Further define the appearance of the element container and border.
 . Expand *Container style*.
 
 . Change the *Appearance* and *Border* options.
- 
+
 [float]
 [[apply-element-styles]]
 ==== Apply a set of styles
@@ -155,7 +151,7 @@ Increase or decrease how often your data refreshes on your workpad.
 [role="screenshot"]
 image::images/canvas-refresh-interval.png[Element data refresh interval]
 
-TIP: To manually refresh the data, click the *Refresh data* icon. 
+TIP: To manually refresh the data, click the *Refresh data* icon.
 
 [float]
 [[organize-element]]
@@ -223,7 +219,7 @@ Change the order of how the elements are displayed on your workpad.
 
 . Select an element.
 
-. In the top right corder, click the *Element options* icon. 
+. In the top right corder, click the *Element options* icon.
 
 . Select *Order*, then select the order that you want the element to appear.
 
@@ -262,7 +258,7 @@ When you have run out of room on your workpad page, add more pages.
 
 . Click *Page 1*, then click *+*.
 
-. On the *Page* editor panel on the right, select the page transition from the *Transition* dropdown. 
+. On the *Page* editor panel on the right, select the page transition from the *Transition* dropdown.
 +
 [role="screenshot"]
 image::images/canvas-add-pages.gif[Add pages]