Merge remote-tracking branch 'elastic/main' into reporting/reporting-…

…deprecation-wording-iii

docs/concepts/data-views.asciidoc

@@ -12,10 +12,10 @@ or all indices that contain your data.
 [[data-views-read-only-access]]
 === Required permissions
 
-* Access to *Data Views* requires the <<xpack-kibana-role-management, {kib} privilege>>
+* Access to *Data Views* requires the <<kibana-role-management, {kib} privilege>>
 `Data View Management`.
 
-* To create a data view, you must have the <<xpack-kibana-role-management,{es} privilege>>
+* To create a data view, you must have the <<kibana-role-management,{es} privilege>>
 `view_index_metadata`.
 
 * If a read-only indicator appears in {kib}, you have insufficient privileges

docs/management/connectors/action-types/index.asciidoc

@@ -74,7 +74,7 @@ Example of the index document for Index Threshold rule:
     "rule_name": "{{ruleName}}",
     "alert_id": "{{alertId}}",
     "context_message": "{{context.message}}"
-} 
+}
 --------------------------------------------------
 
 Example of creating a test index using the API.
@@ -108,7 +108,7 @@ experimental[] {kib} offers a preconfigured index connector to facilitate indexi
 This functionality is experimental and may be changed or removed completely in a future release.
 ==================================================
 
-To use this connector, set the <<action-settings, `xpack.actions.preconfiguredAlertHistoryEsIndex`>> configuration to `true`. 
+To use this connector, set the <<action-settings, `xpack.actions.preconfiguredAlertHistoryEsIndex`>> configuration to `true`.
 
 ```js
   xpack.actions.preconfiguredAlertHistoryEsIndex: true
@@ -123,11 +123,11 @@ Documents are indexed using a preconfigured schema that captures the <<defining-
 
 [IMPORTANT]
 ==============================================
-To write documents to the preconfigured index, you must have `all` or `write` privileges to the `kibana-alert-history-*` indices. Refer to <<xpack-kibana-role-management>> for more information.
+To write documents to the preconfigured index, you must have `all` or `write` privileges to the `kibana-alert-history-*` indices. Refer to <<kibana-role-management>> for more information.
 ==============================================
 
 [NOTE]
 ==================================================
 The `kibana-alert-history-*` indices are not configured to use ILM so they must be maintained manually. If the index size grows large,
 consider using the {ref}/docs-delete-by-query.html[delete by query] API to clean up older documents in the index.
-==================================================
+==================================================

docs/maps/import-geospatial-data.asciidoc

@@ -17,7 +17,7 @@ The {stack-security-features} provide roles and privileges that control which us
 You can manage your roles, privileges, and
 spaces in **{stack-manage-app}** in {kib}. For more information, see
 {ref}/security-privileges.html[Security privileges],
-<<kibana-privileges, {kib} privileges>>, and <<xpack-kibana-role-management, {kib} role management>>.
+<<kibana-privileges, {kib} privileges>>, and <<kibana-role-management, {kib} role management>>.
 
 To upload GeoJSON files in {kib} with *Maps*, you must have:
 

docs/redirects.asciidoc

@@ -416,27 +416,32 @@ This content has moved. Refer to <<data-views-api-get>>.
 
 This content has moved. Refer to <<data-views-runtime-field-api-create>>.
 
-[role="exclude",id="index-patterns-runtime-field-api-delete]
+[role="exclude",id="index-patterns-runtime-field-api-delete"]
 == Index patterns has been renamed to data views.
 
 This content has moved. Refer to <<data-views-runtime-field-api-delete>>.
 
-[role="exclude",id="index-patterns-runtime-field-api-get]
+[role="exclude",id="index-patterns-runtime-field-api-get"]
 == Index patterns has been renamed to data views.
 
 This content has moved. Refer to <<data-views-runtime-field-api-get>>.
 
-[role="exclude",id="index-patterns-runtime-field-api-update]
+[role="exclude",id="index-patterns-runtime-field-api-update"]
 == Index patterns has been renamed to data views.
 
 This content has moved. Refer to <<data-views-runtime-field-api-update>>.
 
-[role="exclude",id="index-patterns-runtime-field-api-upsert]
+[role="exclude",id="index-patterns-runtime-field-api-upsert"]
 == Index patterns has been renamed to data views.
 
 This content has moved. Refer to <<data-views-runtime-field-api-upsert>>.
 
-[role="exclude",id="index-patterns-api-update]
+[role="exclude",id="index-patterns-api-update"]
 == Index patterns has been renamed to data views.
 
 This content has moved. Refer to <<data-views-api-update>>.
+
+[role="exclude",id="xpack-kibana-role-management"]
+== Kibana role management.
+
+This content has moved. Refer to <<kibana-role-management>>.

docs/user/dashboard/aggregation-based.asciidoc

@@ -114,7 +114,7 @@ Choose the type of visualization you want to create, then use the editor to conf
 
 . Add the <<aggregation-reference,aggregations>> you want to visualize using the editor, then click *Update*. 
 +
-NOTE: For the *Date Histogram* to use an *auto interval*, the date field must match the primary time field of the index pattern.
+NOTE: For the *Date Histogram* to use an *auto interval*, the date field must match the primary time field of the {data-source}.
 
 . To change the order, drag and drop the aggregations in the editor. 
 + 

docs/user/dashboard/lens-advanced.asciidoc

@@ -34,7 +34,7 @@ Open the visualization editor, then make sure the correct fields appear.
 
 . On the dashboard, click *Create visualization*.
 
-. Make sure the *kibana_sample_data_ecommerce* index appears, then set the <<set-time-filter,time filter>> to *Last 30 days*.
+. Make sure the *kibana_sample_data_ecommerce* {data-source} appears, then set the <<set-time-filter,time filter>> to *Last 30 days*.
 
 [discrete]
 [[custom-time-interval]]

docs/user/dashboard/lens.asciidoc

@@ -48,7 +48,7 @@ Choose the data you want to visualize.
 
 . If you want to learn more about the data a field contains, click the field.
 
-. To visualize more than one index pattern, click *Add layer > Add visualization layer*, then select the index pattern.
+. To visualize more than one {data-source}, click *Add layer > Add visualization layer*, then select the {data-source}.
 
 Edit and delete.
 
@@ -60,18 +60,18 @@ Edit and delete.
 [[change-the-fields]]
 ==== Change the fields list
 
-Change the fields list to display a different index pattern, different time range, or add your own fields.
+Change the fields list to display a different {data-source}, different time range, or add your own fields.
 
-* To create a visualization with fields in a different index pattern, open the *Index pattern* dropdown, then select the index pattern. 
+* To create a visualization with fields in a different {data-source}, open the *Data view* dropdown, then select the {data-source}. 
 
 * If the fields list is empty, change the <<set-time-filter,time filter>>.
 
-* To add fields, open the action menu (*...*) next to the *Index pattern* dropdown, then select *Add field to index pattern*.
+* To add fields, open the action menu (*...*) next to the *Data view* dropdown, then select *Add field to {data-source}*.
 +
 [role="screenshot"]
-image:images/runtime-field-menu.png[Dropdown menu located next to index pattern field with items for adding and managing fields, width=50%]
+image:images/runtime-field-menu.png[Dropdown menu located next to {data-source} field with items for adding and managing fields, width=50%]
 +
-For more information about adding fields to index patterns and examples, refer to <<runtime-fields>>.
+For more information about adding fields to {data-sources} and examples, refer to <<runtime-fields>>.
 
 [float]
 [[create-custom-tables]]
@@ -453,7 +453,7 @@ To configure the bounds, use the menus in the editor toolbar. Bar and area chart
 .*Is it possible to display icons in data tables?*
 [%collapsible]
 ====
-You can display icons with <<managing-index-patterns, field formatters>> in data tables.
+You can display icons with <<managing-data-views, field formatters>> in data tables.
 ====
 
 [discrete]

docs/user/dashboard/timelion.asciidoc

@@ -34,7 +34,7 @@ The fist parameter of the .es function is the parameter q (for query), which is
 .es(*)
 .es(q=*)
 
-Multiple parameters are separated by comma. The .es function has another parameter called index, that can be used to specify an index pattern for this series, so the query won't be executed again all indexes (or whatever you changed the above mentioned setting to).
+Multiple parameters are separated by a comma. The .es function has another parameter called index, that can be used to specify {a-data-source} for this series, so the query won't be executed against all indexes (or whatever you changed the setting to).
 
 .es(q=*, index=logstash-*)
 

docs/user/dashboard/tsvb.asciidoc

@@ -16,7 +16,7 @@ With *TSVB*, you can:
 image::images/tsvb-screenshot.png[TSVB overview]
 
 [float]
-[[tsvb-index-pattern-mode]]
+[[tsvb-data-view-mode]]
 ==== Open and set up TSVB
 
 Open *TSVB*, then configure the required settings. You can create *TSVB* visualizations with only {data-sources}, or {es} index strings. 
@@ -31,17 +31,19 @@ When you use only {data-sources}, you are able to:
 
 * Improve performance
 
+[[tsvb-index-pattern-mode]]
+
 IMPORTANT: Creating *TSVB* visualizations with an {es} index string is deprecated and will be removed in a future release. By default, you create *TSVB* visualizations with only {data-sources}. To use an {es} index string, contact your administrator, or go to <<advanced-options, Advanced Settings>> and set `metrics:allowStringIndices` to `true`.
 
 . On the dashboard, click *All types*, then select *TSVB*.
 
 . In *TSVB*, click *Panel options*, then specify the *Data* settings.
 
-. Open the *Index pattern selection mode* options next to the *Index pattern* dropdown.
+. Open the *Data view mode* options next to the *Data view* dropdown.
 
 . Select *Use only {kib} {data-sources}*.
 
-. From the *Index pattern* drodpown, select the {data-source}, then select the *Time field* and *Interval*.
+. From the *Data view* drodpown, select the {data-source}, then select the *Time field* and *Interval*.
 
 . Select a *Drop last bucket* option. 
 +
@@ -258,9 +260,9 @@ Calculating the duration between the start and end of an event is unsupported in
 [%collapsible]
 ====
 
-To group with multiple fields, create runtime fields in the index pattern you are visualizing.
+To group with multiple fields, create runtime fields in the {data-source} you are visualizing.
 
-. Create a runtime field. Refer to <<managing-index-patterns, *Manage index patterns data fields*>> for more information.
+. Create a runtime field. Refer to <<managing-data-views, Manage data views>> for more information.
 +
 [role="screenshot"]
 image::images/tsvb_group_by_multiple_fields.png[Group by multiple fields]

docs/user/dashboard/tutorial-create-a-dashboard-of-lens-panels.asciidoc

@@ -41,7 +41,7 @@ Open the visualization editor, then make sure the correct fields appear.
 . Make sure the *kibana_sample_data_logs* index appears.
 +
 [role="screenshot"]
-image::images/lens_indexPatternDropDown_7.16.png[Index pattern dropdown]
+image::images/lens_dataViewDropDown_8.0.png[Data view dropdown]
 
 To create the visualizations in this tutorial, you'll use the following fields:
 
@@ -96,7 +96,7 @@ image::images/lens_metricUniqueVisitors_7.16.png[Metric visualization that displ
 
 There are two shortcuts you can use to view metrics over time. 
 When you drag a numeric field to the workspace, the visualization editor adds the default
-time field from the index pattern. When you use the *Date histogram* function, you can
+time field from the {data-source}. When you use the *Date histogram* function, you can
 replace the time field by dragging the field to the workspace.
 
 To visualize the *bytes* field over time:

docs/user/dashboard/url-drilldown.asciidoc

@@ -202,7 +202,7 @@ Tip: Use in combination with <<helpers, date>> helper to format date.
 |
 | context.panel.indexPatternId +
 context.panel.indexPatternIds
-|Index pattern ids used by a panel.
+|The {data-source} IDs used by a panel.
 
 |
 | context.panel.savedObjectId

docs/user/dashboard/vega.asciidoc

@@ -10,7 +10,7 @@ URL, or static data, and support <<reference-for-kibana-extensions,{kib} extensi
 Use *Vega* or *Vega-Lite* when you want to create visualizations with:
 
 * Aggregations that use `nested` or `parent/child` mapping
-* Aggregations without an index pattern
+* Aggregations without {a-data-source}
 * Queries that use custom time filters
 * Complex calculations
 * Extracted data from _source instead of aggregations
@@ -73,7 +73,7 @@ index: kibana_sample_data_ecommerce
 
 A flat line appears with zero results.
 
-To add the data fields from the *kibana_sample_data_ecommerce* index, replace the following, then click *Update*:
+To add the data fields from the *kibana_sample_data_ecommerce* {data-source}, replace the following, then click *Update*:
 
 * `%timefield%: @timestamp` with `%timefield%: order_date`
 

docs/user/management.asciidoc

@@ -106,7 +106,7 @@ a| <<xpack-security, Users>>
 Add or delete users and assign roles that give users
 specific privileges.
 
-| <<xpack-kibana-role-management, Roles>>
+| <<kibana-role-management, Roles>>
 |View the roles that exist on your cluster. Customize
 the actions that a user with the role can perform, on a cluster, index, and space level.
 

docs/user/security/authorization/index.asciidoc

@@ -23,7 +23,7 @@ Whichever approach you use, be careful when granting cluster privileges and inde
 cluster, and {kib} spaces do not prevent you from granting users of two different tenants access to the same index.
 
 [role="xpack"]
-[[xpack-kibana-role-management]]
+[[kibana-role-management]]
 === {kib} role management
 
 Roles are a collection of privileges that allow you to perform actions in {kib} and {es}. Users are not directly granted privileges, but are instead assigned one or more roles that describe the desired level of access. When you assign a user multiple roles, the user receives a union of the roles’ privileges. This means that you cannot reduce the privileges of a user by assigning them an additional role. You must instead remove or edit one of their existing roles.

docs/user/security/tutorials/how-to-secure-access-to-kibana.asciidoc

@@ -131,6 +131,6 @@ This guide is an introduction to {kib}'s security features. Check out these addi
 
 * View the <<kibana-authentication, authentication guide>> to learn more about single-sign on and other login features.
 
-* View the <<xpack-kibana-role-management, authorization guide>> to learn more about authorizing access to {kib}'s features.
+* View the <<kibana-role-management, authorization guide>> to learn more about authorizing access to {kib}'s features.
 
 Still have questions? Ask  on our https://discuss.elastic.co/c/kibana[Kibana discuss forum] and a fellow community member or Elastic engineer will help out.

src/core/public/core_app/status/components/metric_tiles.test.tsx

@@ -35,6 +35,18 @@ const timeMetric: Metric = {
   value: 1234,
 };
 
+const metricWithMeta: Metric = {
+  name: 'Delay',
+  type: 'time',
+  value: 1,
+  meta: {
+    description: 'Percentiles',
+    title: '',
+    value: [1, 5, 10],
+    type: 'time',
+  },
+};
+
 describe('MetricTile', () => {
   it('correct displays an untyped metric', () => {
     const component = shallow(<MetricTile metric={untypedMetric} />);
@@ -55,4 +67,9 @@ describe('MetricTile', () => {
     const component = shallow(<MetricTile metric={timeMetric} />);
     expect(component).toMatchSnapshot();
   });
+
+  it('correctly displays a metric with metadata', () => {
+    const component = shallow(<MetricTile metric={metricWithMeta} />);
+    expect(component).toMatchSnapshot();
+  });
 });