Merge branch 'master' of github.com:elastic/kibana into fix/doc_value…

…s_autocomplete

* 'master' of github.com:elastic/kibana: (189 commits)
  [TSVB] Shim new platform (elastic#39169)
  [Metric Vis] Shim new platform (elastic#42240)
  [Tag Cloud] Shim new platform (elastic#42348)
  Disable flaky request lib tests. Add es_ui_shared plugin to CODEOWNERS.
  Add disk space percentage to node listing (elastic#42145)
  [SIEM] Add chart interactions - update date picker after brush selection on charts (elastic#42440)
  Document HTTP service (elastic#42331)
  [Reporting] Sanitize 409 error log message (elastic#42495)
  [docs][skip ci] Maps read only access (elastic#35561)
  [x-pack/ftr] refactor types to be more accurate/consistent wit… (elastic#42407)
  [DOCS] Updates images and content in Dashboard docs (elastic#42500)
  Allow sorting on multiple columns in Discover (elastic#41918)
  [Infra UI][Logs UI] Fix autocomplete to use proper derived index pattern (elastic#42287)
  [ftr/cheerio] improve cheerio types to include test subject me… (elastic#42534)
  Upgraded EUI 13.0.0 -> 13.1.1 (elastic#42298)
  Increase max-old-space-size for builds (elastic#42218)
  [Infra UI] Add cloud metrics and cloud/host info to metadata endpoint (elastic#41836)
  [Logs UI][a11y] Announce name of column on remove column button (elastic#41695)
  Inspector 👉 New Platform (elastic#42164)
  Make alerting properly space aware (elastic#42081)
  ...

.eslintrc.js

@@ -186,8 +186,10 @@ module.exports = {
         'x-pack/legacy/plugins/apm/**/*.js',
         'test/*/config.ts',
         'test/visual_regression/tests/**/*',
-        'x-pack/test/visual_regression/tests/**/*',
-        'x-pack/test/*/config.ts',
+        'x-pack/test/*/{tests,test_suites,apis,apps}/**/*',
+        'x-pack/test/*/*config.*ts',
+        'x-pack/test/saved_object_api_integration/*/apis/**/*',
+        'x-pack/test/ui_capabilities/*/tests/**/*',
       ],
       rules: {
         'import/no-default-export': 'off',
@@ -396,6 +398,14 @@ module.exports = {
         'no-console': ['warn', { allow: ['error'] }],
       },
     },
+    {
+      plugins: ['react-hooks'],
+      files: ['x-pack/legacy/plugins/apm/**/*.{ts,tsx}'],
+      rules: {
+        'react-hooks/rules-of-hooks': 'error', // Checks rules of Hooks
+        'react-hooks/exhaustive-deps': ['error', { additionalHooks: '^useFetcher$' }],
+      },
+    },
 
     /**
      * GIS overrides

.github/CODEOWNERS

@@ -36,6 +36,7 @@
 /src/core/  @elastic/kibana-platform
 /src/legacy/server/saved_objects/  @elastic/kibana-platform
 /src/legacy/ui/public/saved_objects  @elastic/kibana-platform
+/config/kibana.yml @elastic/kibana-platform
 
 # Security
 /x-pack/legacy/plugins/security/  @elastic/kibana-security
@@ -57,6 +58,7 @@
 
 # Elasticsearch UI
 /src/legacy/core_plugins/console/  @elastic/es-ui
+/src/plugins/es_ui_shared/  @elastic/es-ui
 /x-pack/legacy/plugins/console_extensions/  @elastic/es-ui
 /x-pack/legacy/plugins/cross_cluster_replication/  @elastic/es-ui
 /x-pack/legacy/plugins/index_lifecycle_management/  @elastic/es-ui

.i18nrc.json

@@ -17,14 +17,15 @@
     "visTypeMarkdown": "src/legacy/core_plugins/vis_type_markdown",
     "metricVis": "src/legacy/core_plugins/metric_vis",
     "visTypeVega": "src/legacy/core_plugins/vis_type_vega",
-    "tableVis": "src/legacy/core_plugins/table_vis",
+    "visTypeTable": "src/legacy/core_plugins/vis_type_table",
     "regionMap": "src/legacy/core_plugins/region_map",
     "statusPage": "src/legacy/core_plugins/status_page",
     "tileMap": "src/legacy/core_plugins/tile_map",
     "timelion": "src/legacy/core_plugins/timelion",
     "tagCloud": "src/legacy/core_plugins/tagcloud",
     "tsvb": "src/legacy/core_plugins/metrics",
-    "kbnESQuery": "packages/kbn-es-query"
+    "kbnESQuery": "packages/kbn-es-query",
+    "inspector": "src/plugins/inspector"
   },
   "exclude": ["src/legacy/ui/ui_render/ui_render_mixin.js"],
   "translations": []

docs/canvas/canvas-getting-started.asciidoc

@@ -7,7 +7,7 @@ To get up and running with Canvas, use the following tutorial where you'll creat
 [float]
 === Before you begin
 
-For this tutorial, you'll need to add the {kibana-ref}/add-sample-data.html[Sample eCommerce orders data].
+For this tutorial, you'll need to add the <<add-sample-data, Sample eCommerce orders data>>.
 
 [float]
 === Create and personalize your workpad

docs/canvas/canvas-workpad.asciidoc

@@ -14,7 +14,7 @@ When you create a workpad, you'll start with a blank page, or you can choose a w
 
 * To import an existing workpad, click and drag a workpad JSON file to the *Import workpad JSON file* field.
 
-For advanced workpad examples, add a {kibana-ref}/add-sample-data.html[sample Kibana data set], then select *Canvas* from the *View Data* dropdown list.
+For advanced workpad examples, add a <<add-sample-data, sample Kibana data set>>, then select *Canvas* from the *View Data* dropdown list.
 
 For more workpad inspiration, go to the link:https://www.elastic.co/blog/[Elastic Blog]. 
 

docs/code/code-basic-nav.asciidoc

@@ -17,4 +17,9 @@ Clicking *Blame* shows the most recent commit per line.
 [role="screenshot"]
 image::images/code-blame.png[]
 
+[float]
+==== Branch selector
+You can use the Branch selector to view different branches of a repo. Note that code intelligence and search index are not available for any branch other than master branch.
+
+
 include::code-semantic-nav.asciidoc[]

docs/code/code-install-lang-server.asciidoc

@@ -16,6 +16,10 @@ You can check the status of the language servers and get installation instructio
 [role="screenshot"]
 image::images/code-lang-server-status.png[]
 
+[float]
+=== Ctag language server
+*Code* also uses a Ctag language server to generate symbol information and code intelligence when a dedicated language server is not available. The code intelligence information generated by the Ctag language server is less accurate but covers more languages.
+
 
 
 include::code-basic-nav.asciidoc[]

docs/code/code-repo-management.asciidoc

@@ -15,12 +15,7 @@ Deleting a repo removes it from local storage and the Elasticsearch index.
 
 [float]
 ==== Reindex a repo
-You can set *Code* to automatically reindex imported repos at set intervals by set the following config in `kibana.yaml`.
-
-[source,yaml]
-----
-xpack.code.disableIndexScheduler: false
-----
+*Code* automatically reindexes an imported repo at set intervals, but in some cases you might need to manually refresh the index. For example, you might refresh an index  after a new language server is installed. Or, you might want to immediately update the index to the HEAD revision. Click *Reindex* to initiate a reindex.
 
 In some cases you might need to manually refresh the index besides automatic indexing. For example, you might refresh an index  after a new language server is installed. Or, you might want to immediately update the index to the HEAD revision. Click *Reindex* to initiate a reindex.
 

docs/dashboard.asciidoc

@@ -3,66 +3,84 @@
 
 [partintro]
 --
-A Kibana _dashboard_ displays a collection of visualizations, searches, and {kibana-ref}/maps.html[maps].
-You can arrange, resize, and edit the dashboard content and then save the dashboard
-so you can share it.
 
-[role="screenshot"]
-image:images/Dashboard_example.png[Example dashboard]
+A {kib} _dashboard_ is a collection of visualizations, searches, and 
+maps, typically in real-time. Dashboards provide 
+at-a-glance insights into your data and enable you to drill down into details. 
 
---
+To start working with dashboards, click *Dashboard* in the side navigation. 
+With *Dashboard*, you can:
 
-[[dashboard-getting-started]]
-== Building a Dashboard
+* <<dashboard-create-new-dashboard, Create a dashboard>>
+* <<customizing-your-dashboard, Arrange dashboard elements>>
+* <<sharing-dashboards, Share a dashboard>>
+* <<import-dashboards, Import and export dashboards>>
+* <<viewing-detailed-information, Inspect and edit dashboard elements>>
+
+
+[role="screenshot"]
+image:images/Dashboard_example.png[Example dashboard]
 
-If you haven't yet indexed data into {es} or created an index pattern,
-you'll be prompted to do so as you follow the steps for creating a dashboard.
-Or, you can use one of the prebuilt sample data sets, available from the
-Kibana home page.
 
 [float]
 [[dashboard-read-only-access]]
 === [xpack]#Read only access#
-When you have insufficient privileges to create or save dashboards, the following 
-indicator in Kibana will be displayed. The buttons to create new dashboards or edit
-existing dashboard won't be visible. For more information on granting access to
-Kibana see <<xpack-security-authorization>>.
+If you see
+the read-only icon in the application header,
+then you don't have sufficient privileges to create and save dashboards. The buttons to create and edit
+dashboards are not visible. For more information, see <<xpack-security-authorization>>.
 
 [role="screenshot"]
 image::images/dashboard-read-only-badge.png[Example of Dashboard's read only access indicator in Kibana's header]
 
 [float]
+[[dashboard-getting-started]]
+=== Interact with dashboards
+
+When you open *Dashhboard*, you're presented an overview of your dashboards. 
+If you don't have any dashboards, you can add 
+<<add-sample-data, sample data sets>>,
+which include pre-built dashboards. 
+
+Once you open a dashboard, you can filter the data
+by entering a search query, changing the time filter, or clicking 
+in the visualizations, searches, and maps. If a dashboard element has a stored query, 
+both queries are applied.
+
+--
+
 [[dashboard-create-new-dashboard]]
-=== Creating a new Dashboard
+== Create a dashboard
+
+To create a dashboard, you must have data indexed into {es}, an index pattern 
+to retrieve the data from {es}, and 
+visualizations, saved searches, or maps. If these don't exist, you're prompted to 
+add them as you create the dashboard.
 
-. In the side navigation, click *Dashboard*.
+For an end-to-end example, see <<tutorial-build-dashboard, Building your own dashboard>>.
+
+. Open *Dashboard.*
 . Click *Create new dashboard.*
 . Click *Add*.
-. [[adding-visualizations-to-a-dashboard]]Use *Add Panels* to add visualizations
-and saved searches to the dashboard. If you have a large number of
-visualizations, you can filter the lists.
+. Use *Add panels* to add elements to the dashboard.
++
+The visualizations, saved searches, and maps
+are stored in panels that you can move and resize. A
+menu in the upper right of the panel has options for customizing
+the panel. You can add elements from 
+multiple indices, and the same element can appear in multiple dashboards.
 +
 [role="screenshot"]
 image:images/Dashboard_add_visualization.png[Example add visualization to dashboard]
 
-. [[saving-dashboards]]When you're finished adding and arranging the panels,
-go to the menu bar and click *Save*.
-
-. In *Save Dashboard*, enter a dashboard title and optionally a description.
-
-. To store the time period specified in the time filter, enable *Store time
-with dashboard*.
-
-. Click *Save*.
-
-[[loading-a-saved-dashboard]]
-To import, export, and delete dashboards, see <<managing-saved-objects>>.
+. When you're finished adding and arranging the panels,
+*Save* the dashboard.
 
+[float]
 [[customizing-your-dashboard]]
-== Arranging Dashboard Elements
+=== Arrange dashboard elements
 
-The visualizations and searches in a dashboard are stored in panels that you can move,
-resize, edit, and delete.  To start editing, click *Edit* in the menu bar.
+In *Edit* mode, you can move, resize, customize, and delete panels to suit your needs. 
 
 [[moving-containers]]
 * To move a panel, click and hold the panel header and drag to the new location.
@@ -71,53 +89,58 @@ resize, edit, and delete.  To start editing, click *Edit* in the menu bar.
 * To resize a panel, click the resize control on the lower right and drag
 to the new dimensions.
 
-[[removing-containers]]
-Additional commands for managing the panel and its contents
-are in the gear menu in the upper right.
-
-[role="screenshot"]
-image:images/Dashboard_Resize_Menu.png[Example dashboard]
+* To toggle the use of margins and panel titles, use the *Options* menu in the upper left.
 
-NOTE: Deleting a panel from a
+* To delete a panel, open the panel menu and select *Delete from dashboard.* Deleting a panel from a
 dashboard does *not* delete the saved visualization or search.
 
-[[viewing-detailed-information]]
-== Inspecting a Visualization from the Dashboard
 
-Many visualizations allow you to inspect the data and requests behind the
-visualization.
+[float]
+[[sharing-dashboards]]
+=== Share a dashboard
+
+[[embedding-dashboards]]
+When you've finished your dashboard, you can share it with your teammates. 
+From the *Share* menu, you can:
+
+* Embed the code in a web page. Users must have Kibana access
+to view an embedded dashboard.
+* Share a direct link to a {kib} dashboard
+* Generate a PDF report
+* Generate a PNG report
+
+TIP: You can create a link to a dashboard by title by doing this: +
+`${domain}/${basepath?}/app/kibana#/dashboards?title=${yourdashboardtitle}`
+
+TIP: When sharing a link to a dashboard snapshot, use the *Short URL*. Snapshot
+URLs are long and can be problematic for Internet Explorer and other
+tools. To create a short URL, you must have write access to {kib}.
+
+[float]
+[[import-dashboards]]
+=== Import and export dashboards
 
-In the dashboard, expand the visualization's panel menu (or gear menu if in
-*Edit* mode) and select *Inspect*.
+To import and export dashboards, go to *Management > Saved Objects*. For details,
+see <<managing-saved-objects, Managing saved objects>>. 
 
-The initial view shows the underlying data for the visualization. To view the
-requests that were made for the visualization, choose *Requests* from the *View*
-menu.
+[float]
+[[viewing-detailed-information]]
+=== Inspect and edit elements
 
-The views you'll see depend on the element that you inspect.
+Many dashboard elements allow you to drill down into the data and requests 
+behind the element. Open the menu in the upper right of the panel and select *Inspect*. 
+The views you see depend on the element that you inspect. 
 
 [role="screenshot"]
-image:images/Dashboard_visualization_data.png[Example of visualization data]
+image:images/Dashboard_inspect.png[Inspect in dashboard]
 
+To open an element for editing, put the dashboard in *Edit* mode, 
+and then select *Edit* from the panel menu. The changes you make appear in
+every dashboard that uses the element. 
 
 
-[[sharing-dashboards]]
-== Sharing a Dashboard
 
-You can either share a direct link to a Kibana dashboard,
-or embed the dashboard in a web page. Users must have Kibana access
-to view an embedded dashboard.
 
-[[embedding-dashboards]]
 
-. Open the dashboard you want to share.
-. In the menu bar, click *Share*.
-. Copy the link you want to share or the iframe you want to embed. You can
-share the live dashboard or a static snapshot of the current point in time.
 
-TIP: You can create a link to a dashboard by title by doing this: +
-`${domain}/${basepath?}/app/kibana#/dashboards?title=${yourdashboardtitle}`
 
-TIP: When sharing a link to a dashboard snapshot, use the *Short URL*. Snapshot
-URLs are long and can be problematic for Internet Explorer and other
-tools.  To create a short URL, you must have write access to {kib}.

docs/development/core/development-basepath.asciidoc

@@ -66,6 +66,15 @@ To accomplish this the `serve` task does a few things:
   - redirects from `/{any}/app/{appName}` to `/{randomBasePath}/app/{appName}` so that refreshes should work
   - proxies all requests starting with `/{randomBasePath}/` to the Kibana server
 
+If you're writing scripts that interact with the Kibana API, the base path proxy will likely
+make this difficult. To bypass the base path proxy for a single request, prefix urls with
+`__UNSAFE_bypassBasePath` and the request will be routed to the development Kibana server.
+
+["source","shell"]
+-----------
+curl "http://elastic:changeme@localhost:5601/__UNSAFE_bypassBasePath/api/status"
+-----------
+
 This proxy can sometimes have unintended side effects in development, so when
 needed you can opt out by passing the `--no-base-path` flag to the `serve` task
 or `yarn start`.