Merge branch 'main' into close-doc-expand-sidebar-onindex-pattern-change

.github/CODEOWNERS

@@ -34,10 +34,12 @@
 /src/plugins/vis_types/vislib/ @elastic/kibana-vis-editors
 /src/plugins/vis_types/xy/ @elastic/kibana-vis-editors
 /src/plugins/vis_types/pie/ @elastic/kibana-vis-editors
+/src/plugins/vis_types/heatmap/ @elastic/kibana-vis-editors
 /src/plugins/visualize/ @elastic/kibana-vis-editors
 /src/plugins/visualizations/ @elastic/kibana-vis-editors
 /src/plugins/chart_expressions/expression_tagcloud/ @elastic/kibana-vis-editors
 /src/plugins/chart_expressions/expression_metric/ @elastic/kibana-vis-editors
+/src/plugins/chart_expressions/expression_heatmap/ @elastic/kibana-vis-editors
 /src/plugins/url_forwarding/ @elastic/kibana-vis-editors
 /packages/kbn-tinymath/ @elastic/kibana-vis-editors
 /x-pack/test/functional/apps/lens @elastic/kibana-vis-editors

.i18nrc.json

@@ -28,6 +28,7 @@
     "expressionRepeatImage": "src/plugins/expression_repeat_image",
     "expressionRevealImage": "src/plugins/expression_reveal_image",
     "expressionShape": "src/plugins/expression_shape",
+    "expressionHeatmap": "src/plugins/chart_expressions/expression_heatmap",
     "expressionTagcloud": "src/plugins/chart_expressions/expression_tagcloud",
     "expressionMetricVis": "src/plugins/chart_expressions/expression_metric",
     "inputControl": "src/plugins/input_control_vis",
@@ -69,6 +70,7 @@
     "visTypeVislib": "src/plugins/vis_types/vislib",
     "visTypeXy": "src/plugins/vis_types/xy",
     "visTypePie": "src/plugins/vis_types/pie",
+    "visTypeHeatmap": "src/plugins/vis_types/heatmap",
     "visualizations": "src/plugins/visualizations",
     "visualize": "src/plugins/visualize",
     "apmOss": "src/plugins/apm_oss",

config/kibana.yml

@@ -99,7 +99,7 @@
 
 # Logs queries sent to Elasticsearch.
 #logging.loggers:
-#  - name: elasticsearch.queries
+#  - name: elasticsearch.query
 #    level: debug
 
 # Logs http responses.

dev_docs/tutorials/data/search.mdx

@@ -129,6 +129,12 @@ setTimeout(() => {
 }, 1000);
 ```
 
+<DocCallOut color="danger" title="Cancel your searches if results are no longer needed">
+  Users might no longer be interested in search results. For example, they might start a new search
+  or leave your app without waiting for the results. You should handle such cases by using
+  `AbortController` with search API.
+</DocCallOut>
+
 #### Search strategies
 
 By default, the search service uses the DSL query and aggregation syntax and returns the response from Elasticsearch as is. It also provides several additional basic strategies, such as Async DSL (`x-pack` default) and EQL.

docs/api/alerting.asciidoc

@@ -1,7 +1,7 @@
 [[alerting-apis]]
 == Alerting APIs
 
-The following APIs are available for {kib} alerting.
+The following APIs are available for Alerting.
 
 * <<create-rule-api, Create rule API>> to create a rule
 

docs/api/alerting/list_rule_types.asciidoc

@@ -4,7 +4,7 @@
 <titleabbrev>List rule types</titleabbrev>
 ++++
 
-Retrieve a list of alerting rule types that the user is authorized to access.
+Retrieve a list of rule types that the user is authorized to access.
 
 Each rule type includes a list of consumer features. Within these features, users are authorized to perform either `read` or `all` operations on rules of that type. This helps determine which rule types users can read, but not create or modify.
 

docs/apm/api.asciidoc

@@ -10,7 +10,6 @@ Some APM app features are provided via a REST API:
 
 * <<agent-config-api>>
 * <<apm-annotation-api>>
-* <<kibana-api,Kibana API>>
 * <<rum-sourcemap-api>>
 
 [float]
@@ -71,6 +70,13 @@ curl -X POST \
     }'
 ----
 
+[float]
+[[kibana-api]]
+=== Kibana API
+
+In addition to the APM specific API endpoints, Kibana provides its own <<api,REST API>>
+which you can use to automate certain aspects of configuring and deploying Kibana.
+
 ////
 *******************************************************
 *******************************************************
@@ -474,90 +480,6 @@ curl -X POST \
 *******************************************************
 ////
 
-[[kibana-api]]
-=== Kibana API
-
-In addition to the APM specific API endpoints, Kibana provides its own <<api,REST API>>
-which you can use to automate certain aspects of configuring and deploying Kibana.
-An example is below.
-
-[[api-create-apm-index-pattern]]
-==== Customize the APM index pattern
-
-Use Kibana's <<saved-objects-api-update,update object API>> to update the default APM index pattern on the fly.
-
-The following example sets the default APM app index pattern to `some-other-pattern-*`:
-
-[source,sh]
-----
-curl -X PUT "localhost:5601/api/saved_objects/index-pattern/apm_static_index_pattern_id" \ <1>
--H 'Content-Type: application/json' \
--H 'kbn-xsrf: true' \
--H 'Authorization: Basic ${YOUR_AUTH_TOKEN}' \
--d' {
-      "attributes": {
-        "title": "some-other-pattern-*", <2>
-      }
-    }'
-----
-<1> `apm_static_index_pattern_id` is the internal, hard-coded ID of the APM index pattern.
-This value should not be changed
-<2> Your custom index pattern matcher.
-
-The API returns the following:
-
-[source,json]
-----
-{
-   "id":"apm_static_index_pattern_id",
-   "type":"index-pattern",
-   "updated_at":"2020-07-06T22:55:59.555Z",
-   "version":"WzYsMV0=",
-   "attributes":{
-      "title":"some-other-pattern-*"
-   }
-}
-----
-
-To view the new APM app index pattern, use the <<saved-objects-api-get,GET object API>>:
-
-[source,sh]
-----
-curl -X GET "localhost:5601/api/saved_objects/index-pattern/apm_static_index_pattern_id" \ <1>
--H 'kbn-xsrf: true' \
--H 'Authorization: Basic ${YOUR_AUTH_TOKEN}'
-----
-<1> `apm_static_index_pattern_id` is the internal, hard-coded ID of the APM index pattern.
-
-The API returns the following:
-
-[source,json]
-----
-{
-  "id":"apm_static_index_pattern_id",
-  "type":"index-pattern",
-  "updated_at":"2020-07-06T22:55:59.555Z",
-  "version":"WzYsMV0=",
-  "attributes":{...}
-    "fieldFormatMap":"{...}
-    "fields":"[{...},{...},...]
-    "sourceFilters":"[{\"value\":\"sourcemap.sourcemap\"}]",
-    "timeFieldName":"@timestamp",
-    "title":"some-other-pattern-*"
-   },
-   ...
-}
-----
-
-// More examples will go here
-
-More information on Kibana's API is available in <<api,REST API>>.
-
-////
-*******************************************************
-*******************************************************
-////
-
 [role="xpack"]
 [[rum-sourcemap-api]]
 === RUM source map API

docs/apm/apm-alerts.asciidoc

@@ -107,7 +107,7 @@ From this page, you can disable, mute, and delete APM alerts.
 [[apm-alert-more-info]]
 === More information
 
-See {kibana-ref}/alerting-getting-started.html[alerting and actions] for more information.
+See {kibana-ref}/alerting-getting-started.html[Alerting] for more information.
 
 NOTE: If you are using an **on-premise** Elastic Stack deployment with security,
 communication between Elasticsearch and Kibana must have TLS configured.

docs/apm/set-up.asciidoc

@@ -8,28 +8,13 @@
 
 APM is available via the navigation sidebar in {Kib}.
 If you have not already installed and configured Elastic APM,
-the *Add data* page will get you started.
+follow the three steps on the *Add data* page to get started:
 
-[role="screenshot"]
-image::apm/images/apm-setup.png[Installation instructions on the APM page in Kibana]
-
-[float]
-[[apm-configure-index-pattern]]
-=== Load the index pattern
-
-Index patterns tell {kib} which {es} indices you want to explore.
-An APM index pattern is necessary for certain features in the APM app, like the query bar.
-To set up the correct index pattern, on the *Add data* page, click *Load Kibana objects*.
+. Start APM Server
+. Add APM agents
+. Load Kibana objects
 
 [role="screenshot"]
-image::apm/images/apm-index-pattern.png[Setup index pattern for APM in Kibana]
-
-TIP: To use a custom index pattern,
-adjust Kibana's <<apm-settings-in-kibana,settings>> or use the <<api-create-apm-index-pattern,Kibana API>>.
-
-[float]
-[[apm-getting-started-next]]
-=== Next steps
+image::apm/images/apm-setup.png[Installation instructions on the APM page in Kibana]
 
-No further configuration in the APM app is required.
-Install an APM Agent library in your service to begin visualizing and analyzing your data!
+That's it! You're now ready to explore your data.

docs/concepts/data-views.asciidoc

@@ -87,11 +87,12 @@ For an example, refer to <<rollup-data-tutorial,Create and visualize rolled up d
 ==== Create a data view that searches across clusters
 
 If your {es} clusters are configured for {ref}/modules-cross-cluster-search.html[{ccs}],
-you can create a {data-source} to search across the clusters of your choosing. Use the
-same syntax that you use in a raw {ccs} request in {es}:
+you can create a {data-source} to search across the clusters of your choosing.
+You specify data streams, indices, and aliases in a remote cluster using the
+following syntax:
 
 ```ts
-<cluster-names>:<data-view>
+<remote_cluster_name>:<target>
 ```
 
 To query {ls} indices across two {es} clusters

docs/developer/contributing/development-accessibility-tests.asciidoc

@@ -90,7 +90,7 @@ Failures can seem confusing if you've never seen one before. Here is a breakdown
    [aria-hidden-focus]: Ensures aria-hidden elements do not contain focusable elements
      Help: https://dequeuniversity.com/rules/axe/3.5/aria-hidden-focus?application=axeAPI
      Elements:
-       - #example
+       - <span aria-hidden="true"><button type="button">Submit</button></span>
        at Accessibility.testAxeReport (test/accessibility/services/a11y/a11y.ts:90:15)
        at Accessibility.testAppSnapshot (test/accessibility/services/a11y/a11y.ts:58:18)
        at process._tickCallback (internal/process/next_tick.js:68:7)
@@ -100,5 +100,5 @@ Failures can seem confusing if you've never seen one before. Here is a breakdown
 * "Dashboard" and "create dashboard button" are the names of the test suite and specific test that failed.
 * Always in brackets, "[aria-hidden-focus]" is the name of the axe rule that failed, followed by a short description.
 * "Help: <url>" links to the axe documentation for that rule, including severity, remediation tips, and good and bad code examples.
-* "Elements:"  points to where in the DOM the failure originated (using CSS selector syntax). In this example, the problem came from an element with the ID `example`. If the selector is too complicated to find the source of the problem, use the browser plugins mentioned earlier to locate it. If you have a general idea where the issue is coming from, you can also try adding unique IDs to the page to narrow down the location.
+* "Elements:"  points to where in the DOM the failure originated (using HTML syntax). In this example, the problem came from a span with the `aria-hidden="true"` attribute and a nested `<button>` tag. If the selector is too complicated to find the source of the problem, use the browser plugins mentioned earlier to locate it. If you have a general idea where the issue is coming from, you can also try adding unique IDs to the page to narrow down the location.
 * The stack trace points to the internals of axe. The stack trace is there in case the test failure is a bug in axe and not in your code, although this is unlikely.

docs/developer/plugin-list.asciidoc

@@ -94,6 +94,10 @@ This API doesn't support angular, for registering angular dev tools, bootstrap a
 |Expression Error plugin adds an error renderer to the expression plugin. The renderer will display the error image.
 
 
+|{kib-repo}blob/{branch}/src/plugins/chart_expressions/expression_heatmap[expressionHeatmap]
+|WARNING: Missing README.
+
+
 |{kib-repo}blob/{branch}/src/plugins/expression_image/README.md[expressionImage]
 |Expression Image plugin adds an image renderer to the expression plugin. The renderer will display the given image.
 
@@ -274,6 +278,10 @@ It acts as a container for a particular visualization and options tabs. Contains
 The plugin exposes the static DefaultEditorController class to consume.
 
 
+|{kib-repo}blob/{branch}/src/plugins/vis_types/heatmap[visTypeHeatmap]
+|WARNING: Missing README.
+
+
 |{kib-repo}blob/{branch}/src/plugins/vis_type_markdown/README.md[visTypeMarkdown]
 |The markdown visualization that can be used to place text panels on dashboards.
 

docs/index-extra-title-page.html

@@ -63,7 +63,7 @@
               >
             </li>
             <li class="listitem">
-              <a href="https://www.elastic.co/guide/en/kibana/current/index-patterns.html"
+              <a href="https://www.elastic.co/guide/en/kibana/8.0/data-views.html"
                 >Create a data view</a
               >
             </li>

docs/management/advanced-options.asciidoc

@@ -521,7 +521,10 @@ Enables the legacy time axis for charts in Lens, Discover, Visualize and TSVB
 The maximum number of buckets a datasource can return. High numbers can have a negative impact on your browser rendering performance.
 
 [[visualization-visualize-pieChartslibrary]]`visualization:visualize:legacyPieChartsLibrary`::
-The visualize editor uses new pie charts with improved performance, color palettes, label positioning, and more. Enable this option if you prefer to use to the legacy charts library.
+The visualize editor uses new pie charts with improved performance, color palettes, label positioning, and more. Enable this option if you prefer to use the legacy charts library.
+
+[[visualization-visualize-heatmapChartslibrary]]`visualization:visualize:legacyHeatmapChartsLibrary`::
+Disable this option if you prefer to use the new heatmap charts with improved performance, legend settings, and more..
 
 [[visualize-enablelabs]]`visualize:enableLabs`::
 Enables users to create, view, and edit experimental visualizations. When disabled,

docs/redirects.asciidoc

@@ -15,6 +15,10 @@ Refer to {ref}/snapshot-restore.html[Snapshot and Restore].
 == Tutorial: Snapshot and Restore
 Refer to {ref}/snapshot-restore.html[Snapshot and Restore].
 
+[role="exclude",id="configuring-tls-communication"]
+== Encrypt communications in {kib}
+Refer to <<using-kibana-with-security,Configure security in {kib}>>.
+
 [role="exclude",id="configuring-tls"]
 == Encrypt TLS communications in {kib}
 Refer to {ref}/security-basic-setup-https.html#encrypt-kibana-http[Encrypt HTTP client communications for {kib}].

docs/settings/alert-action-settings.asciidoc

@@ -5,7 +5,7 @@
 <titleabbrev>Alerting and action settings</titleabbrev>
 ++++
 
-Alerts and actions are enabled by default in {kib}, but require you configure the following in order to use them:
+Alerting and actions are enabled by default in {kib}, but require you to configure the following:
 
 . <<using-kibana-with-security,Set up {kib} to work with {stack} {security-features}>>.
 . <<configuring-tls-kib-es,Set up TLS encryption between {kib} and {es}>>.

docs/settings/apm-settings.asciidoc

@@ -101,6 +101,8 @@ Changing these settings may disable features of the APM App.
 | `xpack.apm.indices.sourcemap` {ess-icon}
   | Matcher for all source map indices. Defaults to `apm-*`.
 
+| `xpack.apm.autocreateApmIndexPattern` {ess-icon}
+  | Set to `false` to disable the automatic creation of the APM index pattern when the APM app is opened. Defaults to `true`.
 |===
 
 // end::general-apm-settings[]

docs/setup/settings.asciidoc

@@ -21,7 +21,7 @@ configuration using `${MY_ENV_VAR}` syntax.
 |===
 
 | `console.ui.enabled:`
-Toggling this causes the server to regenerate assets on the next startup,
+| Toggling this causes the server to regenerate assets on the next startup,
 which may cause a delay before pages start being served.
 Set to `false` to disable Console. *Default: `true`*
 

docs/user/alerting/alerting-getting-started.asciidoc

@@ -125,18 +125,18 @@ image::images/rule-concepts-summary.svg[Rules, connectors, alerts and actions wo
 [[alerting-concepts-differences]]
 == Differences from Watcher
 
-{kib} alerting and <<watcher-ui,Watcher>> are both used to detect conditions and can trigger actions in response, but they are completely independent alerting systems.
+Alerting and <<watcher-ui,Watcher>> are both used to detect conditions and can trigger actions in response, but they are completely independent alerting systems.
 
 This section will clarify some of the important differences in the function and intent of the two systems.
 
-Functionally, {kib} alerting differs in that: 
+Functionally, Alerting differs in that: 
 
 * Scheduled checks are run on {kib} instead of {es}
 * {kib} <<alerting-concepts-conditions, rules hide the details of detecting conditions>> through *rule types*, whereas watches provide low-level control over inputs, conditions, and transformations.
 * {kib} rules track and persist the state of each detected condition through *alerts*. This makes it possible to mute and throttle individual alerts, and detect changes in state such as resolution.
-* Actions are linked to *alerts* in {kib} alerting. Actions are fired for each occurrence of a detected condition, rather than for the entire rule.
+* Actions are linked to *alerts* in Alerting. Actions are fired for each occurrence of a detected condition, rather than for the entire rule.
 
-At a higher level, {kib} alerting allows rich integrations across use cases like <<xpack-apm,*APM*>>, <<metrics-app,*Metrics*>>, <<xpack-siem,*Security*>>, and <<uptime-app,*Uptime*>>.
+At a higher level, Alerting allows rich integrations across use cases like <<xpack-apm,*APM*>>, <<metrics-app,*Metrics*>>, <<xpack-siem,*Security*>>, and <<uptime-app,*Uptime*>>.
 Pre-packaged *rule types* simplify setup and hide the details of complex, domain-specific detections, while providing a consistent interface across {kib}.
 
 --

docs/user/alerting/alerting-setup.asciidoc

@@ -5,7 +5,7 @@
 <titleabbrev>Set up</titleabbrev>
 ++++
 
-The Alerting feature is automatically enabled in {kib}, but might require some additional configuration.
+Alerting is automatically enabled in {kib}, but might require some additional configuration.
 
 [float]
 [[alerting-prerequisites]]
@@ -17,17 +17,17 @@ If you are using an *on-premises* Elastic Stack deployment:
 
 If you are using an *on-premises* Elastic Stack deployment with <<using-kibana-with-security, *security*>>:
 
-* If you are unable to access Alerting, ensure that you have not {ref}/security-settings.html#api-key-service-settings[explicitly disabled API keys].
+* If you are unable to access {kib} Alerting, ensure that you have not {ref}/security-settings.html#api-key-service-settings[explicitly disabled API keys].
 
-The Alerting framework uses queries that require the `search.allow_expensive_queries` setting to be `true`. See the scripts {ref}/query-dsl-script-query.html#_allow_expensive_queries_4[documentation]. 
+The alerting framework uses queries that require the `search.allow_expensive_queries` setting to be `true`. See the scripts {ref}/query-dsl-script-query.html#_allow_expensive_queries_4[documentation]. 
 
 [float]
 [[alerting-setup-production]]
 === Production considerations and scaling guidance
 
 When relying on alerting and actions as mission critical services, make sure you follow the <<alerting-production-considerations,Alerting production considerations>>.
 
-See <<alerting-scaling-guidance>> for more information on the scalability of {kib} alerting.
+See <<alerting-scaling-guidance>> for more information on the scalability of Alerting.
 
 [float]
 [[alerting-security]]