Merge branch '7.14' into backport/7.14/pr-106331

docs/CHANGELOG.asciidoc

@@ -2694,7 +2694,7 @@ image::images/timelion-vis-paste-expression.png[Timelion advanced editor UI]
 The Timelion visualization panel appears on the dashboard.
 +
 [role="screenshot"]
-image::images/timelion-dashboard.png[Final dashboard with saved Timelion app worksheet]
+image::user/dashboard/images/timelion-dashboard.png[Final dashboard with saved Timelion app worksheet]
 
 [float]
 [[breaking-v7.10.0]]

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

@@ -317,6 +317,7 @@ The plugin integrates with the core system via lifecycle events: `setup`<!-- -->
 |  [SavedObjectsImportHook](./kibana-plugin-core-server.savedobjectsimporthook.md) | A hook associated with a specific saved object type, that will be invoked during the import process. The hook will have access to the objects of the registered type.<!-- -->Currently, the only supported feature for import hooks is to return warnings to be displayed in the UI when the import succeeds. The only interactions the hook can have with the import process is via the hook's response. Mutating the objects inside the hook's code will have no effect. |
 |  [SavedObjectsImportWarning](./kibana-plugin-core-server.savedobjectsimportwarning.md) | Composite type of all the possible types of import warnings.<!-- -->See [SavedObjectsImportSimpleWarning](./kibana-plugin-core-server.savedobjectsimportsimplewarning.md) and [SavedObjectsImportActionRequiredWarning](./kibana-plugin-core-server.savedobjectsimportactionrequiredwarning.md) for more details. |
 |  [SavedObjectsNamespaceType](./kibana-plugin-core-server.savedobjectsnamespacetype.md) | The namespace type dictates how a saved object can be interacted in relation to namespaces. Each type is mutually exclusive: \* single (default): This type of saved object is namespace-isolated, e.g., it exists in only one namespace. \* multiple: This type of saved object is shareable, e.g., it can exist in one or more namespaces. \* multiple-isolated: This type of saved object is namespace-isolated, e.g., it exists in only one namespace, but object IDs must be unique across all namespaces. This is intended to be an intermediate step when objects with a "single" namespace type are being converted to a "multiple" namespace type. In other words, objects with a "multiple-isolated" namespace type will be \*share-capable\*, but will not actually be shareable until the namespace type is changed to "multiple". \* agnostic: This type of saved object is global. |
+|  [SavedObjectTypeExcludeFromUpgradeFilterHook](./kibana-plugin-core-server.savedobjecttypeexcludefromupgradefilterhook.md) | If defined, allows a type to run a search query and return a query filter that may match any documents which may be excluded from the next migration upgrade process. Useful for cleaning up large numbers of old documents which are no longer needed and may slow the migration process.<!-- -->If this hook fails, the migration will proceed without these documents having been filtered out, so this should not be used as a guarantee that these documents have been deleted.<!-- -->Experimental and subject to change |
 |  [SavedObjectUnsanitizedDoc](./kibana-plugin-core-server.savedobjectunsanitizeddoc.md) | Describes Saved Object documents from Kibana &lt; 7.0.0 which don't have a <code>references</code> root property defined. This type should only be used in migrations. |
 |  [ScopeableRequest](./kibana-plugin-core-server.scopeablerequest.md) | A user credentials container. It accommodates the necessary auth credentials to impersonate the current user.<!-- -->See [KibanaRequest](./kibana-plugin-core-server.kibanarequest.md)<!-- -->. |
 |  [ServiceStatusLevel](./kibana-plugin-core-server.servicestatuslevel.md) | A convenience type that represents the union of each value in [ServiceStatusLevels](./kibana-plugin-core-server.servicestatuslevels.md)<!-- -->. |

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

@@ -0,0 +1,13 @@
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [kibana-plugin-core-server](./kibana-plugin-core-server.md) &gt; [SavedObjectsType](./kibana-plugin-core-server.savedobjectstype.md) &gt; [excludeOnUpgrade](./kibana-plugin-core-server.savedobjectstype.excludeonupgrade.md)
+
+## SavedObjectsType.excludeOnUpgrade property
+
+If defined, allows a type to exclude unneeded documents from the migration process and effectively be deleted. See [SavedObjectTypeExcludeFromUpgradeFilterHook](./kibana-plugin-core-server.savedobjecttypeexcludefromupgradefilterhook.md) for more details.
+
+<b>Signature:</b>
+
+```typescript
+excludeOnUpgrade?: SavedObjectTypeExcludeFromUpgradeFilterHook;
+```

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

@@ -52,6 +52,7 @@ Example after converting to a multi-namespace (shareable) type in 8.1:
 
 ```
 Note: migration function(s) can be optionally specified for any of these versions and will not interfere with the conversion process. |
+|  [excludeOnUpgrade](./kibana-plugin-core-server.savedobjectstype.excludeonupgrade.md) | <code>SavedObjectTypeExcludeFromUpgradeFilterHook</code> | If defined, allows a type to exclude unneeded documents from the migration process and effectively be deleted. See [SavedObjectTypeExcludeFromUpgradeFilterHook](./kibana-plugin-core-server.savedobjecttypeexcludefromupgradefilterhook.md) for more details. |
 |  [hidden](./kibana-plugin-core-server.savedobjectstype.hidden.md) | <code>boolean</code> | Is the type hidden by default. If true, repositories will not have access to this type unless explicitly declared as an <code>extraType</code> when creating the repository.<!-- -->See [createInternalRepository](./kibana-plugin-core-server.savedobjectsservicestart.createinternalrepository.md)<!-- -->. |
 |  [indexPattern](./kibana-plugin-core-server.savedobjectstype.indexpattern.md) | <code>string</code> | If defined, the type instances will be stored in the given index instead of the default one. |
 |  [management](./kibana-plugin-core-server.savedobjectstype.management.md) | <code>SavedObjectsTypeManagementDefinition&lt;Attributes&gt;</code> | An optional [saved objects management section](./kibana-plugin-core-server.savedobjectstypemanagementdefinition.md) definition for the type. |

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

@@ -0,0 +1,19 @@
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [kibana-plugin-core-server](./kibana-plugin-core-server.md) &gt; [SavedObjectTypeExcludeFromUpgradeFilterHook](./kibana-plugin-core-server.savedobjecttypeexcludefromupgradefilterhook.md)
+
+## SavedObjectTypeExcludeFromUpgradeFilterHook type
+
+If defined, allows a type to run a search query and return a query filter that may match any documents which may be excluded from the next migration upgrade process. Useful for cleaning up large numbers of old documents which are no longer needed and may slow the migration process.
+
+If this hook fails, the migration will proceed without these documents having been filtered out, so this should not be used as a guarantee that these documents have been deleted.
+
+Experimental and subject to change
+
+<b>Signature:</b>
+
+```typescript
+export declare type SavedObjectTypeExcludeFromUpgradeFilterHook = (toolkit: {
+    readonlyEsClient: Pick<ElasticsearchClient, 'search'>;
+}) => estypes.QueryDslQueryContainer | Promise<estypes.QueryDslQueryContainer>;
+```

docs/management/manage-index-patterns.asciidoc

@@ -48,7 +48,7 @@ The script must match the field *Type*, or the script fails.
 +
 For information on how to create runtime fields in *Discover*, refer to <<add-field-in-discover,Add a field>>.
 +
-For information on how to create runtime fields in *Lens*, refer to <<add-fields-in-lens,Add fields>>.
+For information on how to create runtime fields in *Lens*, refer to <<change-the-fields,Change the fields list>>.
 
 [float]
 [[runtime-field-examples]]

docs/redirects.asciidoc

@@ -7,6 +7,22 @@
 The following pages have moved or been deleted.
 
 --
+[role="exclude",id="configuring-tls"]
+== Encrypt TLS communications in {kib}
+See {ref}/security-basic-setup-https.html#encrypt-kibana-http[Encrypt HTTP client communications for {kib}].
+
+[float]
+[role="exclude",id="configuring-tls-browser-kib"]
+=== Encrypt traffic between the browser and {kib}
+
+See {ref}/security-basic-setup-https.html#encrypt-kibana-browser[Encrypt traffic between your browser and {kib}].
+
+[float]
+[role="exclude",id="configuring-tls-kib-es"]
+=== Encrypt traffic between {kib} and {es}
+
+See {ref}/security-basic-setup-https.html#encrypt-kibana-elasticsearch[Encrypt traffic between {kib} and {es}].
+
 [role="exclude",id="monitoring-xpack-kibana"]
 == Configuring monitoring in {kib}
 

docs/user/dashboard/aggregation-based.asciidoc

@@ -1,8 +1,22 @@
 [[add-aggregation-based-visualization-panels]]
 === Aggregation-based
 
-Aggregation-based visualizations are the core {kib} panels, and are not optimized
-for a specific use case.
+Aggregation-based visualizations are the core {kib} panels, and are not optimized for a specific use case.
+
+With aggregation-based visualizations, you can:
+
+* Split charts up to three aggregation levels, which is more than *Lens* and *TSVB*
+* Create visualization with non-time series data
+* Use a <<save-open-search,saved search>> as an input
+* Sort data tables and use the summary row and percentage column features
+* Assign colors to data series
+* Extend features with plugins
+
+Aggregation-based visualizations include the following limitations:
+
+* Limited styling options
+* Math is unsupported
+* Multiple indices is unsupported
 
 [float]
 [[types-of-visualizations]]
@@ -135,7 +149,7 @@ Add the sample web logs data that you'll use to create the bar chart, then creat
 [float]
 ===== Open and set up the aggregation-based bar chart
 
-Open the bar chart visualization builder and change the time range. 
+Open the *Aggregation based* editor and change the time range. 
 
 . On the dashboard, click *All types > Aggregation based*, select *Vertical bar*, then select *kibana_sample_data_logs*.